Loading current status…
SigmaX is being 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.
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.
The core record path exists: Capital Twin context, CapitalMandate result, ActionIntent identity, Preflight, authorization state, route status, impact record, and audit record.
Mandate rules define what is allowed, blocked, or proof-required before an ActionIntent can become an authorization candidate.
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 published OpenAPI 3.1 contract and a compiling typed TypeScript SDK are shipped, with a CI guard asserting the spec matches the running routes. The API/SDK path creates and reads governed ActionIntent records — never an order, custody, or capital-routing API.