Receipts & Value Ledger
Proof is generated as work runs.
SupraOS Receipts are workflow-level proof objects. They are not ordinary logs. A log says something happened in one system. A Receipt binds the why, who, what, where, approval, policy, evidence, action, outcome, and value context across systems.
Receipt anatomy
| Field | Meaning |
|---|---|
| Receipt ID | Unique identifier. |
| Work Object ID | The execution unit the Receipt belongs to. |
| Charter ID | The mandate authorizing the work. |
| Intent | What the work was meant to accomplish. |
| Human owner | Accountable owner. |
| Agent identities | Agents involved and execution context. |
| Source scope | Sources used or referenced. |
| Policy version | Policy rules evaluated. |
| Approval events | Who approved what and when. |
| Executed actions | Actions taken, prepared, or blocked. |
| Systems touched | Connected systems involved. |
| Evidence references | Artifacts, records, logs, links, hashes, or confirmations. |
| External signals | Public or external context used, if applicable. |
| Redaction profile | What can be shown to each audience. |
| Outcome | Completed, blocked, pending, exception, or verified. |
| Value Ledger link | Related value/risk record. |
| Verification status | Whether the proof chain validates. |
Value Ledger
- Baseline
- Value at risk
- Value under recovery
- Verified value captured
- Risk prevented
- Work Objects launched
- Receipts generated
- Evidence gaps
- Confidence and attribution
Controlled disclosure
- Executive view: outcome, value, owner, open decisions.
- Security view: identities, systems touched, action classes, policy decisions.
- Auditor view: evidence references, approvals, Receipt verification.
- Legal view: disclosure scope, chain of custody, privilege boundaries.
- Vendor/customer view: only scoped facts and permitted evidence.
Need deeper diligence?
Qualified evaluators can request security review materials or start with a read-only Company Scan.