Target, payload, recipients and expiry bound
READYTHE CONSEQUENCE GATEWAY
Any agent can propose the move. Every consequential action passes through SupraOS.
The Consequence Gateway applies one execution standard to SupraOS specialists, customer-designed agents, external agents, automations and people. It binds every proposed move to live state, customer rules, authority and required proof.
Agents can change. The authority and proof standard do not.
HOW EVERY ACTION RUNS
From proposal to durable proof through one boundary.
ProposePredictDecideAuthorizePrepareExecuteVerifyObserveConfirm
The agent never turns model confidence into authority. SupraOS refreshes mutable state, checks VTWM consequences, applies customer rules, binds the exact permission, executes or delegates the step, and verifies the actual destination.
SUPRAOS / ACTION / AUTHORITY / PROOF LIVE
CONSEQUENCE GATEWAYThe execution boundary for every agent
Live state, consequences, customer rules and exact authority
ProposePredictAuthorizePrepareExecuteObserve
Expected, forbidden, hidden and delayed effects
PASSEDScope and limit valid for current state
BOUNDDestination state + non-reversal watch
REQUIREDGateway decisionExecute through ServiceNowPermission bound to current state
THE EXACT ACTION CONTRACT
No vague approval. No stale permission. No self-reported completion.
Business result
The exact outcome this action advances and the exposure attached to it.
Current source state
The facts, versions, evidence and contradictions valid at decision time.
Permitted + forbidden
What may change, what must not change and the point of no return.
Owner + expiry
Who can authorize the consequence, under which rule, limit and time window.
Required final state
Destination read-back, supporting evidence and delayed observations required.
Failure path
How SupraOS pauses, retries, compensates, escalates or fails without inventing success.
If the target, state, evidence, recipients, policy or action changes, the authority no longer matches. SupraOS rebuilds the move before it runs.
EVERY EXECUTOR
Use the best worker for each approved step.
Native connector
SupraOS executes the approved action and reads the destination back.
Responsible employee
A named owner receives the exact work, evidence and completion standard.
Agent or automation
A customer or partner executor performs the approved step; SupraOS checks the resulting destination state.
Execution can be delegated. Commercial accountability cannot.
DESTINATION VERIFICATION
The executor’s “done” response never closes the outcome.
SupraOS checks the state where the change landed. It compares the observed result with the authorized change, records mismatches, keeps required delayed watches open and advances the Outcome Graph only when the proof standard is met.
Actual destination state
Connector result, object version, before-and-after state and linked evidence.
Expected versus observed
Required changes, forbidden changes, partial completion and ambiguity.
What must continue to hold
Acceptance, signature, payment, non-reversal and other outcome conditions.
EARNED AUTONOMY
Verified performance earns a wider operating boundary.
SupraOS tracks each company, agent, action family and consequence class separately. Verified history shows where the customer can expand authority. Drift, policy change, mismatch, reversal or failed proof automatically holds the affected action family inside its current boundary.
Autonomy is not a product-wide switch. It is earned action by action.