Object, fields, limits and expected effect
BOUNDTRANSITION RECEIPTS & COMMERCIAL PROOF
An agent’s answer is not proof. The company state is.
A Transition Receipt proves one move. A Recovery Record carries the complete commercial outcome. The Value Ledger keeps the final value attached to the work that produced it.
Effective and last reviewed: 23 July 2026
Every consequential move leaves a complete Transition Receipt.
SupraOS binds the starting state, evidence, VTWM forecast, customer rules, exact authority, executor, payload, destination response, immediate read-back and delayed observations into one inspectable record.
SUPRAOS / EXECUTION / DESTINATION READ-BACKPRODUCT VIEW
TRANSITION RECEIPTApproved action matched to observed reality
Authority, executor, destination change and delayed state remain bound
ApproveExecuteRead backCompareObserveClose
Executor identity and response recorded
DONEObject version and before/after state checked
VERIFIEDCommercial condition remains under observation
OPENReceipt stateImmediate proof completeFinal value awaits customer confirmation
Three proof layers. No leap from task to value.
Transition Receipt
What was authorized, what executed, what changed and which states must still be observed.
Recovery Record
Every action, human completion, deliberate no-action decision and final confirmation behind one commercial outcome.
Value Ledger
Qualified value, completed work, verified state, customer confirmation and final value remain separate.
Done is not changed. Changed is not value. SupraOS proves each state separately.
What a Transition Receipt captures.
| Field | What it proves |
|---|---|
| Outcome Room + transition ID | The commercial outcome and exact state change this record belongs to. |
| Current state + evidence | What the company knew, when it knew it and which sources supported the move. |
| VTWM forecast | Expected, forbidden, hidden and delayed effects predicted before release. |
| Rules + exact authority | The customer’s operating rules, eligible role, decision, limits and expiry applied. |
| Executor + payload | The SupraOS agent, employee or external agent and the exact operation performed. |
| Immediate destination state | The response and resulting state SupraOS read back from the destination after execution. |
| Delayed observations | Whether downstream obligations, reversals, persistence and commercial conditions held. |
| Repair + final status | Any retry, compensation, rollback, escalation and the final verified state. |
TRANSITION RECEIPT OBJECT
The complete record of one consequential company move.
transition_receipt {
decision_state_hash: "st_8f2…",
candidate_futures: [A, B, C, D],
selected_future: "B_fix_validate_renew",
intent_lock: "il_41d…",
named_authority: "CRO / renewal",
executor: "approved connector",
expected_state: "jira.priority=P1",
first_observation: "jira.priority=P2",
divergence: "destination mismatch",
correction: "write rebuilt",
second_observation: "jira.priority=P1",
delayed_condition: "customer accepted",
final_value_state: "$420K protected"
}
decision_state_hash: "st_8f2…",
candidate_futures: [A, B, C, D],
selected_future: "B_fix_validate_renew",
intent_lock: "il_41d…",
named_authority: "CRO / renewal",
executor: "approved connector",
expected_state: "jira.priority=P1",
first_observation: "jira.priority=P2",
divergence: "destination mismatch",
correction: "write rebuilt",
second_observation: "jira.priority=P1",
delayed_condition: "customer accepted",
final_value_state: "$420K protected"
}
What the receipt makes inspectable
- The state that existed when the decision was made.
- The futures considered and why the selected future survived.
- The exact authority, limits, expiry and forbidden effects.
- The executor response and independent destination readback.
- Every mismatch, repair, delayed observation and final value state.
Share the proof without copying the source systems.
Each reviewer can inspect the authority, execution and resulting state they need. Customer systems remain authoritative; the Recovery Record keeps the chain intact.