One proposed action, fully labeled.
The packet names the Capital Twin, the signal, the proposed action, the mandate result, missing proof, and required approver.
- AIX-WM-DRIFT-1047
- Mandate: conditional
- Proof gap: tax note stale
Site under construction, formerly SigmaX has begun the process of transitioning to AIgentXS.
An agent proposes an action. Rules define its permitted scope. Evidence supports or challenges it. The appropriate person reviews the decision, and the record preserves what was checked, who was responsible, and what happened next.
Intent infrastructure, not money movement. Human authorization required. No live execution or capital movement.
An evaluation is a rule-checking result. Authorization is a decision by the appropriate principal. Execution is a separate controlled action. Observed effect is evidence of what happened. One stage never proves the next.
An architecture description does not establish a working connector or customer deployment.
The modules below show the existing Capital Action OS: mandate checks, Preflight, human authorization, route status, impact records, and audit trails. Illustrations explain the record structure; they do not establish a live customer workflow.
Follow a sample proposed action, called an ActionIntent, through eight stations. Select a station to inspect what it adds to the decision record.
The account becomes a Capital Twin: positions, objectives, mandate, constraints, notes, and evidence context.
SigmaX does not approve on behalf of the human. Route status is recorded; SigmaX does not execute or move capital. Later evidence feeds the next Capital Twin without upgrading sample or paper evidence into live proof.
The platform does not end at a dashboard. It produces a packet a team can inspect before deciding what is allowed.
Model drift, tax note, mandate constraint, and proposed rebalance
Mandate check, proof gap, counter-evidence, cost, and route eligibility
Human authorization required before any outside action
Paper-ready for committee review; no execution inside SigmaX
The packet names the Capital Twin, the signal, the proposed action, the mandate result, missing proof, and required approver.
SigmaX identifies the principal or reviewer who must authorize, hold, or block. The system does not approve for them.
Impact Ledger and AuditWriter preserve what changed, what was checked, who reviewed it, and what route state existed.
The artifact shows the proposed action, missing proof, required approver, and route state before anyone acts outside SigmaX.
Evidence layer for Capital Twins and ActionIntents.
Signal source. Drift can become an ActionIntent only through mandate and Preflight checks.
Preflight and counterfactual context, not a standalone product or execution engine.
System of record for route, authorization, impact, and audit state.
Choose a sample condition to inspect how a missing, duplicated, or truncated event is represented in the record.
none
Every event's hash recomputes from stored content.
Complete — v01 → v12, consecutively versioned.
verified means both: provenance recomputes and the sequence is complete — never one without the other · recompute-on-read ships in the public API and SDK, operator-enabled per deployment
SigmaX is built on an architecture designed to govern consequential actions from initial proposal through authorization, execution status, observed effect, reconciliation, and audit proof.
Multiple United States patent applications have been filed relating to aspects of this architecture, including fail-closed candidate promotion, evidence-governed authorization, independent effect verification, recovery and supervision, and audit-completeness verification.
Patent pending. No patent has been granted, and no statement on this website represents the scope, validity, enforceability, ownership, or eventual disposition of any patent claim.
Multiple U.S. applications pending
Patent pending
Fail-closed promotion gate + audit-completeness (anti-omission) verification + evidence governance
Status and scope in /disclosures
Start with Builder Sandbox, move into Authority Team or Institutional OS, or connect your own platform through the ActionIntent API and private deployment path.