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. This page is the canonical definition of each state.
Live
Available today in the Lagos pilot. You can fund a task of this type right now and get a verified outcome back.
Pilot scale: one zone (Yaba, Lagos), ~100 verified Operators. Throughput grows as the pilot proves out.
Pilot
Running with selected design partners under concierge supervision. Ask us to be included.
Not self-serve yet; templates and pricing may still move. No SLA.
Gated
Built or planned, and deliberately locked behind a metric gate. It unlocks when the numbers hold — not when a date arrives.
The gate is always stated (e.g. “fill ≥95% and auto-pass ≥90%, per zone”). We never sell into a gate.
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 one of the six reasons teams trust the work; this page is that discipline, written down. When a gate opens, the change lands in the changelog.