Audit & receipts
Every gate decision the Warden makes — allow or deny, including when it routes the call to review — produces a signed receipt. Receipts are not an optional logging feature you opt into; they are the mechanism that makes the Enforced Boundary's claims checkable after the fact, not just trusted at the moment of the call.
Inside the platform-native sandbox, the individual frames of an invocation are evidenced too, but not each one separately signed. Routine allowed frames are leaves in a signed Merkle checkpoint, taken at a fixed interval and on any significant decision. The significant ones carry their own signed receipt: the invocation's gate decision, every attestation requirement, the first policy denial for each target, every credentialed send, every governed or privileged operation, and the first egress to each new destination. If a checkpoint cannot be written, the invocation is stopped.
1. What a receipt is
A receipt is the artifact attached to every Warden gate decision:
{ "ledgerId": "ldg_a1b2c3", "signature": "..." }
ledgerIdcorrelates to the decision's entry in the project's audit stream, so an investigation can move from a receipt to the audit record of the same decision. A Warden receipt is a standalone signed commitment: it is not an entry in Kibo's hash-chained audit ledger, which covers custody-lifecycle key operations.signatureis the platform's signature over the decision payload — the principal, the tool, the input, the verdict, and thegovernedOpClassthat was billed. Anyone holding the platform's public signing key can verify a receipt without trusting the platform's live API.
2. What a receipt proves
A receipt is the answer to "did Warden actually decide this, and did the decision it recorded match what happened." A verified receipt attests to three things:
- The exact call was adjudicated — the receipt binds the specific principal, tool, and input, not "some approval from Warden at some point." A receipt for one call cannot be presented as authorization for a different one.
- The decision has not been altered since — the receipt's signature covers the decision, so any change to a receipt breaks its signature and is detectable on verification. Warden receipts are standalone signed commitments, not links in a hash chain.
- The
governedOpClassthat was billed is the class that was decided — because the class is bound into the receipt at decide-time, the billing weight applied to an action is provably the class Warden actually assigned, not a value that could drift between decision and invoice.
A receipt is tamper-evident, not "un-tamperable" — the guarantee is that tampering is detectable, via signature verification, not that tampering is physically impossible. This is the same precise framing Kibo's audit ledger uses, and Keep holds to it for the same reason: an overclaimed guarantee is a worse security posture than an accurately-scoped one.
3. Receipts are single-use
An approved (allow) decision's receipt authorizes exactly one call and cannot be replayed against a second one — the platform never hands the agent a copy of its own receipt to hold or resubmit. The guarantee comes from the agent never possessing the receipt in the first place, not from an expiry window or a usage counter layered on top after the fact.
4. Two receipts, two jobs — do not conflate them
Keep has two kinds of receipt, and they authorize different things:
| Receipt | Where it comes from | What it's for |
|---|---|---|
| Decision receipt | Warden gate | The record of an enforced decision, and the sole credential the platform's execution machinery uses to perform an approved action. This is the receipt §1–§3 describe. |
| Classification receipt | /rampart/classify | A signed, time-bound attestation of a classification result — see API reference §1. Advisory input a tool's manifest can opt in to having Warden weigh, never an authorization on its own. |
A classification receipt cannot substitute for a decision receipt, and Warden never treats one as if it were the other — the two carry distinct, non-interchangeable signing scopes precisely so they can't be confused for each other even by accident.
5. Retrieving and verifying a receipt
Every Warden gate decision returns a signed receipt — a standard JWS, signed by the platform ledger key (EdDSA or RS256), committing to the full decision (verdict, reason, tool, waypoint class, org/project/subject, decision time, and any policy/approval/classification fields that applied). Any change to a receipt is detectable by verifying its signature with a standard JWS verifier. A receipt is a standalone per-decision object — it is not an entry in Kibo's hash chain, which covers custody-lifecycle operations only.
Verify a receipt offline with any standard JWS/JOSE verifier: fetch the platform's public keys once from /.well-known/ledger-jwks, then verify the receipt's signature against the key named by its kid, pinning the issuer (/warden) and the receipt type. The feed carries more than one signing key, each tagged with its k9o_signer_role; a receipt verifier accepts the key the receipt names. The ledgerId field cross-references the decision's row in your audit export. This is a per-receipt signature check — the Kibo ledger chain-walk verifier does not apply to gate receipts.
6. See also
- API reference — the
/rampart/classifyresponse shape. - Architecture — how a decision is made.
- Billing & the GOPS model — how the receipt-bound
governedOpClassdetermines cost. - Kibo — Audit Ledger — Kibo's hash-chained ledger of custody-lifecycle operations, a separate system from Warden receipts.