The verification workbench

Trust starts with a check you can repeat.

Sign a receipt. Change one field. Challenge a signer. Follow a policy version. Six small experiments make the evidence mechanisms visible and inspectable.

The verification code runs locally on synthetic inputs. These demonstrations establish bounded properties under their verifiers; they do not provide production runtime enforcement or certify an agent. See what runs today and what is only proposed.

  • 01 · Signature integrity — Flip one byte and it voids.
  • 02 · Batch inclusion — Eight receipts. One signature. Each provable alone.
  • 03 · Policy history — Yesterday's decision, judged by yesterday's policy.
  • 04 · Configuration binding — Change the configuration. Re-check the evidence.
  • 05 · Delegated authority — Widen one edge. Watch the root's blast radius move.
  • 06 · Authority analysis — Inspect the authority that goes unused. Full page: the over-grant analyzer.

05 · Delegated authority

Widen one edge. Watch the root's blast radius move.

A correct capability token can only narrow as it is delegated, so an ancestor reaches exactly its own grant. Break that on any edge and authority flows back up the tree.

Delegation treeSix synthetic identities. A widened child grant adds its scope to every ancestor's effective authority.platformopsfinancepayroll-botpii-botledger-botDelegation treeSix synthetic identities. A widened child grant adds its scope to every ancestor's effective authority.platformopspayroll-botpii-botfinanceledger-bot
  • passattenuation holds — Every child narrows. The root reaches exactly its own grant: 5 of 9 sensitive resources.
  • noteblast radius at the root — 5 / 9 sensitive resources reachable — BRI 55.6%