ARCHITECTURE

From permission to decision

A person defines the scope. The agent proves its identity. Each receiving service makes the final decision.

Grants consent within a fictional session.

Two signatures, two keys

The issuer signs the delegation using ES256. The agent uses its own P-256 key to bind the proof to the request content, the receiving URL, and the credential. The service verifies both signatures and records the proof identifier in a SQLite database.

View issuer public key

Two local policies

Aero Demo accepts booking drafts up to USD 1,500. Bank Demo permits transfer drafts up to USD 500 and rejects confirmation. Each limit applies in addition to the delegated amount.

Revocation and traceability

The process checks the delegation's current status and consumes the proof in a database transaction. Session history shows which checks passed, failed, or were skipped.

Try the verification flow