Action Spine status.
SigmaX is aligned around the Capital Action OS: a system-of-record layer for Capital Twins, mandates, ActionIntents, Preflight, human authorization, route status, impact records, and audit trails.
Built for proof before motion. Not live execution. Not customer-capital routing.
The Public Evidence And Authority Ledger.
A public-safe view of what SigmaX is actually producing: evidence records, review checks, source coverage, and authority boundaries. No identities, no client data, no raw strategies, no customer capital routing, and no execution authority.
What exists in the current product direction.
Every posture below is a build-and-gate statement: what the code does, and what has to pass before a release ships — typecheck, API tests, and the web and portal builds. None of them says a capability is operating on a schedule for a customer. That would need a registered scheduled task, an advancing heartbeat, and a dated runtime record, and this page does not have one.
The Public Evidence And Authority Ledger above is the only section on this page that reads runtime state, and it reports itself unavailable when no dated record is observed. Per-capability status — the claim, the demonstration that proves it, and where it actually stands — is stated once, on the authorization flow page. This page does not restate it, so nothing written here can move a capability up that ladder.
The source record path covers Capital Twin context, CapitalMandate result, ActionIntent identity, Preflight, authorization state, route status, impact record, and audit record. CI checks typecheck, API tests, and web/portal builds; each service release needs its own deployment evidence.
Mandate rules define what is allowed, blocked, or proof-required before an ActionIntent can become an authorization candidate. That describes the code path this release gates — not a claim that the registry is running on a schedule for a customer today.
Approval records are bound to an accountable principal. SigmaX does not approve, sign, route, or execute on behalf of the human.
Authority state is stored as durable records rather than page-only UI state or sample-only claims.
Impact and audit records preserve the evidence, mandate result, approval state, route state, actor, and timestamp.
The public OpenAPI 3.1 contract is checked against source registrations in CI. A TypeScript client exists in the repository and is not published to a public package registry. Confirm SDK distribution, workspace access, and enabled routes during onboarding. A source contract is not proof of current customer availability. This is never an order, custody, or capital-routing API.
The current boundary is decision support and draft/paper routing.
The pilot activation path is concrete.
- Pilot workspace provisioning: workspace, roles, access scope, and sample-to-real data boundary
- Embedded Approval Inbox activation: approved partner origin, API base URL, and scoped session issuance
- Production smoke: access inquiry, checkout/intake fallback, portal login, approval queue, API keys, and audit export
- Pilot proof packet: first workflow, route states, impact records, and audit trail
- Counsel/operator review before any execution, custody, or customer-capital pathway