01
Trust
Start from an anchor you chose.
The verifier receives trusted roots explicitly. The protocol does not phone home, discover an identity provider, or silently expand the trust set.
- root
- engineering
- key
- ed25519:8f31…
- scope
- deploy
The authority path
From trust
to action.
Auths makes permission a portable object. Authority begins from trust the verifier chose, narrows through delegation, binds to an exact action, and resolves where that action would execute.
Read the protocol01—05One continuous chain
02
Delegate
Pass authority by narrowing it.
A grant can reduce capability, resource, audience, validity, and depth. It cannot manufacture authority its parent never held.
- capability
- release
- target
- prod-eu
- expires
- 14:32 UTC
03
Bind
Attach authority to exact bytes.
A profile canonicalizes the security-relevant action. The proof covers its digest and audience, so later mutation produces a different action.
- artifact
- sha256:a91e…
- strategy
- canary
- audience
- gateway
04
Verify
Resolve permission at the boundary.
The receiving service checks signatures, delegation, constraints, time, audience, and limits locally against its own trusted context.
- signatures
- valid
- authority
- complete
- network
- 0 calls
05
Execute
Run only the verified command.
The application decodes the command from the verified action. It never verifies one set of bytes and executes another supplied by the caller.
- result
- authorized
- command
- sealed
- decision
- deterministic
06The invariant
At every boundary
Authority may narrow. It never grows.
Trusted rootBounded grantExact action