What our capability states mean.
Every capability on this site carries one of three states, rendered from the same governed configuration that gates the product — so the site can only claim what is actually true.
Live today: 10 task types · Pilot: 0 · Gated: 3 — from GET /v1/content
| State | What you can do | What can change | What opens the next state |
|---|---|---|---|
| Live | Self-serve in the Lagos pilot: fund a task and a verified Operator is dispatched. | Pricing and templates are stable; changes land in the changelog first. | Already open. Scale grows zone by zone as fill and auto-pass hold. |
| Pilot | Running with selected design partners under concierge supervision. Ask to be included. | Templates and pricing may still move. No SLA yet. | Goes Live when its pilot cohort holds the stated quality bar. |
| Gated | Not orderable. Built or planned, and deliberately locked. | Anything may change before release. | A stated metric gate — e.g. fill ≥95% and auto-pass ≥90%, per zone. Never a date. |
Why gates? Composed workflows fail exponentially on an unproven single-task fill rate — so capabilities open per zone only when fill and auto-pass thresholds hold. Metric-gated release is that discipline, written down. When a gate opens, the change lands in the changelog, and the badge you followed to this page updates in the same moment — both render from the same configuration.