Example Presence Record
Who, what, when, why, device, challenge, signature — the sealed answers, plus where to fetch the key and the verifier that check them.
The anatomy, field by field
Who — the actor the action context names, and, when a human reviewer decided, the officer sealed into the override record.
What — the intent, target and amount that were actually approved: the action digest commits to all of them, so a later change is detectable.
When — the evaluation timestamp, sealed at decision time rather than reconstructed afterwards.
Why — the verdict policy actually reached, the policy evaluation with any failed rules, and the rollout stage in force.
Device — the outcome of the server-verified passkey assertion and capture provenance that Gate 1 evaluated.
Challenge — the session nonce the ceremony answered, which commits to a SHA-256 digest of the action context.
Signature — Ed25519 over the canonical payload and its chain hash, naming the key id, with the keys and the verifier published.
In shadow mode the sealed verdict is the true one even though the caller was told to proceed — which is precisely what makes a watch-only period a measurement rather than a gap.
Check it yourself
The artifacts behind this page
- Produce a real one in the browser./demo →
- What gets sealed, and when./how-it-works/signed-records →