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
A company starts with a changed signal, model, constraint, or client requirement. SigmaX turns it into a non-executing decision packet, checks the mandate and proof requirements, identifies the required human authorization, records the route status, and preserves the impact and audit state.
Intent infrastructure, not money movement. Human authorization required. No live execution or capital movement.
Watch an ActionIntent pass eight stations. Every station adds a field to the record the customer keeps.
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.
Every lifecycle event is consecutively versioned and independently anchored. Break the sequence — recompute-on-read names exactly what is wrong.
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
The way SigmaX gates a proposed action — its fail-closed candidate-promotion gate, its audit-completeness (anti-omission) verification, and the related evidence-governance architecture — is the subject of seven U.S. provisional patent applications filed with the United States Patent and Trademark Office, covering six distinct inventions. Patent pending; not a representation that any patent has been granted.
Read the intellectual-property disclosures ->7 U.S. provisional applications
Patent pending
Fail-closed promotion gate + audit-completeness (anti-omission) verification + evidence governance
Named filings in /disclosures