# Status

The platform is extracted from bodies that already run, so its parts are at different stages of maturity, and this page states each stage plainly. Four words are used, and they mean specific things. **Running** means the capability operates inside the first body today. **Rails** means the provider interfaces underneath the capability exist and are proven programmable one at a time, so wiring them into the platform is provisioning work rather than invention. **Extracting** means the capability is proven as a convention inside the first body and is being pulled into the platform layer now. **Open** means no shipping product implements the capability anywhere, including this one.

Each capability below carries the weakest of the four words that is still true of it today.

| capability | state | detail |
|---|---|---|
| event log | running | The append-only log runs in the first body. Every table the body uses is a view over it, and the log doubles as the audit trail. |
| funnel instrumentation | running | Signed tokens and per-stage events exist in the first body. The first outbound waves are the calibration run for the stage rates. |
| approval queue | running | Approve-each is the standing law in the first body: nothing is sent in the owner's name without approval of the exact text. Batch approval and standing rules are the graduation path. |
| presence | running | Domain purchase, DNS, and site deployment are proven end to end through provider APIs. |
| mind-swappability | running | The craft lives in the body's machinery. In a blind screening, a cheaper model matched a stronger model's graded output once the machinery carried the craft. |
| body-side memory | running | Events, worklogs, skills, and verdict registries persist inside the body and survive a change of mind. |
| legal wrapper | running | One umbrella entity with a trade name per venture. The entity is the contracting party, and a named human owns it. |
| composed spawn | rails | Each provisioned part is proven against its provider individually. The one-call composition is the platform work now. |
| payments | rails | The payment provider's interfaces are mature, and the first body's payment links are being wired in. |
| banking | rails | Balance, transactions, and virtual cards are readable and manageable through the bank's API. |
| mail | rails | Sending and receiving are proven. Cold outbound runs on a separate warmed domain, so a deliverability problem cannot touch the primary domain. |
| voice | rails | Phone providers are proven programmable. Voice is sequenced last, after outbound earns it. |
| managed organs | extracting | The first body hand-rolled its pipeline tables. The shared pipeline, contact, and finance tables are extracted only as a second body proves the same schema recurs. |
| multi-tenant events | extracting | Venture-scoped rows on one database are the virtualization path for the shared event store. |
| spend gradients | open | Card issuers enforce caps and category rules, and those rails are mature. The graduated authorization layer on top, from approve-each to standing rules on money, is not shipped by any product, including this one. |
| agent KYC | open | Beneficial ownership of an entity must be a human, so every body is legally a human-owned company operated by agents. One vendor precedent for an agent-operated entity exists, and it is months old. |