Skip to main content
Delegrity

Product

Every action stops at a checkpoint.

Pick a case and watch where Delegrity can say no.

One request, five stopsIllustrative sequence · not a live record

The account changes after approval. The recheck catches it.

Agent request
  1. BindWho, for whom, and the exact action. Exact action fixed
  2. DecideMandate, your policy, a person. Allowed and approved
  3. GrantRecheck, then single-use authority. Account ····4821 → ····9930
  4. ConfirmRead the system back. Nothing to read back
  5. ProveA signed, hash-chained receipt. No execution receipt
Execution boundary
Target systemNot reached

Decision BLOCKED

Execution NOT_DISPATCHED

Outcome –

How one action is decided

  • The request becomes one action, fixed by a fingerprint, with the agent, who it acts for and the mandate in force.
  • Your policy engine is consulted, and any approval is bound to that exact fingerprint.
  • Revoking the mandate means an earlier decision no longer covers the action.
  • Just before it runs, authority is checked again, and what was approved is compared, field by field, with what is about to run.
  • Only if nothing material changed is a single-use grant issued, bound to that action and the bridge presenting it, valid for at most 300 seconds.

What each action leaves

  • Every record carries the fingerprint of the one before it, so changing any record breaks the chain from that point.
  • The receipt carries an Ed25519 signature.
  • A separate verifier checks the signature and the chain without trusting the rest of Delegrity.
  • Sending is not doing: until the business system's result is read back, the outcome stays unknown.
  • A development system may run without a signing key, and its receipts then say unsigned.

Bring one action your agent must not get wrong.

We map it with you in a 45-minute session, at no platform commitment.