Five labels. Plain BUILT is the only one that means you could use it.
State of the world as at 29 August 2026, re-read after the 1 September sitting. Sixteen migrations that were written and applied to nothing are now cloud-applied; what separates the platform from working is a build, the run driver, not a window at a database.
Five words, and they are not interchangeable.
- BuiltIn the main line, its tests run, and a person or a job actually reaches it.
- Built, not switched onIn the product with its tests running, and nothing turns it on: a flag with no setting row behind it, or a caller that hasn't adopted it. Real, and unusable.
- Written, not appliedMerged as a database migration and applied to no database. Needs a person at a keyboard with a database open. Since 1 September this label is mostly spent.
- Not builtNo code. Some are gaps. Some are recorded decisions, and those say so.
- Ruled out for nowA decision, not backlog. Named so nobody counts it as coming.
Thirty capabilities, one label each.
| Capability | State | Note |
|---|---|---|
| Agent-facing API, workflow definitions, run control loop, skill contract | Built | |
| Scheduled workflow dispatcher; inbound signal intake (form, webhook) | Built | |
| Draft-before-operate enforcement: a workflow must be promoted before it can act | Built | |
| Landing-zone data fence; sync metering and freshness; proven sync workers | Built | |
| Credential custody; session grants (scoped, short-TTL) and tripwire | Built | |
| Row-level security and client data isolation | Built | |
| Approvals permission floor: agents mint, humans decide, enforced in the database | Built | |
| Scoped agent identities replacing the master key (19 of them) | Built | |
| BYOK model-credential resolver with four named refusals | Built | |
| Client portal on real records through row-level security | Built | |
| Credential broker, the sole door to client platforms | Built, not switched on | No live client credential activated |
| Ten-check gate chain | Built, not switched on | Master flag off by default |
| Run and job ledger: tables, claim, settle, cost columns | Built | Cloud-applied 1 September; nothing drives it yet |
| A job running start to finish | Not built | The run driver. A four-to-seven day build, and the highest-weighted open risk on the board |
| Cheap planning pass and Gate 1 on the plan | Built, not switched on | Waits on the run driver |
| Memory step: a run recap the next run reads | Built, not switched on | Routes landed; no run has produced one |
| Per-client budget caps | Built, not switched on | Spend ceilings in cents set nowhere yet |
| Per-client fairness in the scheduler | Built, not switched on | |
| Fleet and per-client roll-ups | Built, not switched on | Seeded shut: an open flag over an empty ledger would present zeroes as fact |
| Starting work from a page or doc comment | Built, not switched on | |
| Chat panel | Built, not switched on | Needs a metered key |
| Handlers for 36 client-platform actions | Built, not switched on | 17 read, 4 stage, 15 never. Unregistered |
| Worker sandbox boundary | Built, not switched on | Refuses to arm until the host half exists |
| Skill release control | Built, not switched on | Installed service, four refusals hold it shut |
| Automations registry, library, silence alarm | Built, not switched on | Registry live; first automation awaiting approval |
| Alerting that reaches a human | Not built | The watchers fire. No device is subscribed |
| Portability and self-hosting tooling | Not built | Five design papers, no code. The one thing that hasn't moved |
| Scheduled sessions on the provider's cloud | Not built | |
| A warehouse layer | Ruled out for now | |
| Skills catalogue and studio surfaces | Ruled out for now | A ready plan, deliberately not started |
The single best question to ask isn't "is it built". The answer is mostly yes and it's the less informative half. Ask: has a job ever run from start to finish, and can I see the receipt? As at 1 September the answer is no, and the board carries that as its highest-weighted open risk in those words. Everything on this page is downstream of it.
More docs
Architecture
The topology: four zones wired around one record, where agents run, and the four ways a worker is started.
Security
Row-level security as the whole authorisation story, the credential broker, the ten-check gate chain, and what has actually been made to fire.
The stack
Next.js, TypeScript, Supabase, Nango, Airbyte, n8n and Vercel: what each does, what's being rebuilt, and what a stranger needs to run it.
Data plane
How client data reaches Hub: Airbyte into a fenced landing zone, thin transforms, a freshness stamp on every number.
Automations & skills
The split: one repo per organisation, a birth certificate for every automation, skills whose home is git.
Status
The capability matrix, five labels, no hedging. What you could use this afternoon versus what needs a switch or a sitting.
Self-hosting
The clone manifest and the transfer sequence: what you stand up, what moves, what never leaves our custody.