strix-verify

Public receipt inspector. Every field below is either read from the receipt's own signed bytes or marked absent. The verdict is computed in your browser, not served by Strix.

Fetching the receipt and verifying it in your browser…

1 Human view · what this receipt says happened

2 Cryptographic view · the bytes the signature covers

3 Verify independently · don't take this page's word for it

? What a verified receipt does and does not prove

It does prove

  • These exact bytes were signed by the key the receipt names, and have not changed since.
  • The action, actor, capability, environment and timestamp inside the signed payload are the ones that were bound at signing time — not a label added afterwards.
  • The record occupies its own link in an append-only proof chain.

It does not prove

  • Completeness. A receipt proves what it records. It cannot prove that everything else which happened was also recorded — that is a property of the execution boundary, not of a signature.
  • That the decision was correct. Verification establishes provenance and integrity, never that the policy behind the outcome was the right policy.
  • Anything about fields marked absent below. Where a fact is not in the signed bytes, this page says so instead of supplying one.