Skip to main content
The current protocol revision is 2.0.0-draft.3. Requests select that exact revision and the versions of every required profile. Unsupported selections are errors. Implementations must not silently downgrade them. A request binds the tenant, producer, operator-resolved requester, route revision, purpose, profiles, material digests, captured limits and absolute deadlines. Execution requests add the proposed action, context, policy and occurrence commitments. Producer metadata is retained in the commitment but does not acquire authorising meaning. Decision, audit, grant and execution states are separate. A signed answer can remain useful history after private content is deleted or authority expires. A signature alone proves neither human understanding nor successful execution. Accepted requests keep their original revisions and signed records. Upgrades must support that meaning or cancel unused authority and require fresh review. Historical verification, retries and restored data cannot renew an expired or consumed grant. Continue with the review lifecycle, execution extension, HTTP transport and machine-readable contract.