A receipt you can check.
The envelope, its place in the ledger, and the signed root. Verification runs in this browser from the same code as the offline CLI.
Loading the published development receipt…
Source claimed-at is the sender’s event date. Recorded-at is when Recourse recorded it; Sealed-at is when its proof was committed. The minute bucket is not the seal time. Imported history does not backdate sealing.
Received → Durable → Sealed. Acknowledged is not durable. Searchable-through: Not available in this preview.
Received, Durable and Sealed dates are covered by the receipt proof. Received and Durable sit inside the hashed chain entry, Sealed sits inside the signed root, so the verifier detects a change made to any of them after sealing. They are still times this service asserts from its own clock, and the development signer supplies no independently trusted time. Recorded-at is inside the hashed envelope. Seal lag is calculated from the Sealed-at inside the signed root, which is the value these pages render.
Decision record
- Record ID
- Loading…
- Decision
- Loading…
- Tenant sequence
- Loading…
- Source claimed-at
- Loading…
- Recorded-at
- Loading…
- Sealed-at
- Loading…
- Seal lag from recorded-at
- Loading…
- Envelope SHA-256
- Loading…
- Previous chain commitment
- Loading…
- Hold state
- Loading…
The hold state is read when this page loads. It is not part of the sealed bytes, so it can change after the seal.
Minute seal
- Tree size
- Loading…
- Leaf index
- Loading…
- Minute
- Loading…
- Merkle root
- Loading…
- Timestamp trust
- Loading…
- Development public-key pin
- Loading…
- Global development public-key pin
- Loading…
- Global root
- Loading…
- Global log period
- Loading…
Where this record has reached
- Received
- Loading…
- Durable
- Loading…
- Sealed
- Loading…
- Searchable-through
- Loading…
Received is an acknowledgement, not durability. Searchable-through is a retrieval index position reported by the index, never inferred from ledger state.
From leaf to root
Each sibling is the actual hash supplied in this receipt. The verifier reconstructs the path and compares it with the signed root.
What this proves
A valid receipt binds the exact public fields, ciphertext and key reference to a specific chain entry and signed Merkle root.
Development signer means integrity under a published dev key and no independently trusted time. Decision quality, the truth of inputs and retention need their own evidence.
Inspect the receipt JSON
Loading…