Expand description
Agent Delegation Protocol 1.0 types and validation helpers.
Delegation events are ordinary Agent Identity envelopes whose actor is a controller key for an HTTPS principal document.
Structs§
- Controller
- Same type for active and retired bindings. Missing delegation means signing-only.
- Delegation
Acceptance - Delegation
Credential - Delegation
Events Response - Delegation
Grant Payload - Delegation
Policy - Delegation
Query Request - Delegation
Query Response - Delegation
Revoke Payload - Delegation
Service Discovery - Delegation
Service Endpoints - Delegation
Status Document - Delegation
Summary - Principal
Descriptor - Principal
Document - Principal
Link
Enums§
Constants§
Functions§
- delegation_
grant_ event - delegation_
revoke_ event - is_
principal_ alias - Reports whether
urlis an alias the principal itself acknowledges. Any origin can redirect to any principal, so an alias must not be shown as a name for the principal unless it is listed here. - materialize_
delegation_ credential - Materializes an already accepted event with trusted previous state and the service’s actual acceptance time. This helper does not authorize the event.
- validate_
controller - validate_
controller_ enumeration - Per-result check; caller authenticates the actor and resolves the document.
- validate_
delegation_ acceptance - Caller also enforces fresh HTTPS, live Identity replay rules, and atomic persistence.
- validate_
delegation_ envelope - validate_
delegation_ event_ authority - Pre-signing policy check over trusted document/state. No signature, HTTP, cache-age, live timestamp-window, or nonce verification is performed.
- validate_
delegation_ grant_ payload - validate_
delegation_ id - validate_
delegation_ query_ request - A public delegation query is an existence check and must include both
subjectandprincipal_id. Omitting either side makes it an enumeration query, which services must authorize before answering; passallow_enumerationwhen building such an authorized request.limitdefaults to 20; services SHOULD cap it at 100. - validate_
delegation_ revoke_ payload - validate_
delegation_ use - Audience/status/time only, after signature/history checks. Caller still authenticates the subject and enforces scopes and constraints.
- validate_
historical_ delegation - Caller authenticates acceptance evidence and previous state. This checks the evidence’s hash binding and historical policy, not current status or application constraints.
- validate_
principal_ document - validate_
principal_ resolution - Checks the authoritative-read rule of Agent Delegation Section 3: a
principal document binds controller keys only when it is read at its own
id. A document served anywhere else is a copy; itscontrollersmust be discarded anddocument.idresolved instead.