SuperLoops
Every project SuperLoops runs for a client lives across four surfaces joined by one immutable identifier. The surfaces share identity, never content. And the human gate sits between every proposal and every send.
Agent context — brain, rules, runbooks, SOPs, governance
Every workflow's source of intent. Why the agent does what it does.
Code, repos, scripts, infra, build output
Where the system actually runs. Versioned, deployable, owned.
Structured client ops · task tracking · client interfaces
The client-facing surface. What you see, what you approve.
Strategy · registry · navigation · human reading
Where the operator's brain lives. Where decisions get explained.
The slug is the join key — identical on all four surfaces, immutable after creation. If you change the slug, you have a new project, not a new version of the old one.
The same four-beat loop SuperLoops has been running for thirteen years — across LCX, Bitay, Tezos India, and now three of its own products — serving over 70,000 users. The structure is what shipped them. It's what SuperLoops installs for clients.
Form, webhook, or schedule. The agent knows about it before you do.
sub-second
Pulls enrichment, drafts the routing, packages the proposal for review.
12 min manual → 8s
One card. Approve, edit, or kill. The system waits on the human gate.
by you, every time
API calls fan out — atomic, idempotent, fully logged.
single source of truth
Want to see how SuperLoops would install this?
Twenty minutes. SuperLoops walks the team through the four surfaces and where each workflow would sit.