Policy and authority

V5 policy evaluation is bound to the committed policy root. Signed authority envelopes, bounded delegation, key rotation, and keyring-root selection are part of the same foundation (KIP-0008 through KIP-0011).

The host still owns credentials, the decision to invoke a mutation, and every external effect. Core does not ship a credential store or an implicit Studio write route.

Rust produces matching authorization roots for policy evaluation and canonical authority-envelope roots. Cryptographic algorithms and external identity resolution stay host responsibilities on that crate. Optional key ids are included in canonical envelope payloads so rotation fixtures match.

An attestation that names keyringRoot must match authorityKeyringRootV1 of the supplied keyring, and the key must sit inside notBefore, notAfter, and revokedAt. See Attestations.

executeKnowledgeAuthorizedOperationV5 is the host-owned gate for commit, merge, policy, authority, and sync. It validates the envelope, records allow or deny, and invokes the supplied mutation only after approval. Policy and authority administration handlers remain host-owned. See Coordination.

Namespace filters on a V4 query are not this policy system. Authorize first. See Namespace boundaries.