Skip to content

Site under construction, formerly SigmaX has begun the process of transitioning to AIgentXS.

AIgentXS · How it works

Keep the proposal, the rules, and the decision together.

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.

Shared design
Proposal identity, versioned rules, linked evidence, decision responsibility, and record history.
Sector-specific
Buyers, inputs, rules, qualified reviewers, jurisdiction, failure modes, integration, and legal pathway.

An architecture description does not establish a working connector or customer deployment.

Capital implementation — SigmaX

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.

Lifecycle

One signal becomes one record.

Follow a sample proposed action, called an ActionIntent, through eight stations. Select a station to inspect what it adds to the decision record.

Paused while inspecting or outside view
Signal + Capital Twin01 / 08
Understand

The account becomes a Capital Twin: positions, objectives, mandate, constraints, notes, and evidence context.

Decision record · sample household1 / 8 FIELDS
Capital Twin
Household · positions, mandate, constraints, notes
ActionIntent
Preflight
Authorization
Route status
Impact Ledger
AuditWriter
Drift & replay
select a station to pause · Play animation resumesno live execution or capital movement · human authorization required

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.

Inspectable product output

The company receives a governed decision packet, not another dashboard.

The platform does not end at a dashboard. It produces a packet a team can inspect before deciding what is allowed.

Company input

Model drift, tax note, mandate constraint, and proposed rebalance

SigmaX analysis

Mandate check, proof gap, counter-evidence, cost, and route eligibility

Approval state

Human authorization required before any outside action

Route status

Paper-ready for committee review; no execution inside SigmaX

Sample ActionIntent packet
Committee review packet: AIX-WM-DRIFT-1047
Sample only
ActionIntent packet

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
Approval state

Authority stays human-bound.

SigmaX identifies the principal or reviewer who must authorize, hold, or block. The system does not approve for them.

Approver: investment principal
Human authorization required
State: approval required
AI authority: none
Audit output

The record is ready before the meeting.

Impact Ledger and AuditWriter preserve what changed, what was checked, who reviewed it, and what route state existed.

Impact Ledger: opened
AuditWriter: draft record
External action: none
Decision handoff

The artifact shows the proposed action, missing proof, required approver, and route state before anyone acts outside SigmaX.

Buyer handoff
One packet for committee review
Open issue
Tax note must be refreshed
Route state
Paper-ready; no execution
Capital authority
none
Customer capital
not routed
External execution
disabled
Audit completeness

See what happens when a record is missing.

Choose a sample condition to inspect how a missing, duplicated, or truncated event is represented in the record.

v01
9f2a
v02
c41d
v03
07be
v04
e5a3
v05
3b90
v06
d6c2
v07
71f4
v08
a8e0
v09
5c17
v10
f03d
v11
2e6b
v12
b94c
HEAD · v01ANCHOR · v12 · recompute-on-read: verified
VERIFIED
Finding

none

Provenance

Every event's hash recomputes from stored content.

Sequence

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

How the records are secured ->
Intellectual property

Patent-pending governed-action architecture.

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.

Filings

Multiple U.S. applications pending

Status

Patent pending

Covers

Fail-closed promotion gate + audit-completeness (anti-omission) verification + evidence governance

Detail

Status and scope in /disclosures

Build the decision record before the action path.

Start with Builder Sandbox, move into Authority Team or Institutional OS, or connect your own platform through the ActionIntent API and private deployment path.