Shared receipts
The public-safe decision artifact produced from a completed analysis.
A receipt contains the selected relationship, side, essential economics, material limitation, freshness and a path back to the relevant market.
Receipt storage accepts structured public-safe fields only. It excludes the owner's raw sentence, private notes, model prompts, internal traces and unsupported execution claims.
A persisted receipt uses an opaque public identifier. Revocation makes it unavailable to public readers.
Lifecycle
The create request carries a fixed receipt version, receipt type, series and market tickers, selected side, market timestamps, selected-side price, amount at risk, upfront cost, possible gross payout and remaining exposure. Arbitrary narrative fields are rejected.
The service validates that the market belongs to the stated series and that the snapshot precedes market close when a close time is present. It reconstructs the binary-contract ledger and rejects inconsistent cost, payout or remaining exposure.
Creation is idempotent. Repeating the same request with the same idempotency key returns the existing receipt. Reusing that key for different economics returns a conflict rather than changing the stored decision.
Public reads use an opaque identifier. Missing receipts are unavailable. Expired or revoked receipts return the same bounded unavailable state, which limits what a caller can learn about prior records. Revocation changes public access without changing the original private analysis.