VERSIONED REFERENCE · VAGP v0.2

The frozen authority semantics behind the proof.

This preview turns the approved local VAGP v0.2 baseline into a stable public reference route. It records the source hierarchy, lifecycle vocabulary, invariants, reason-code anchors, conformance mapping and accepted limits without changing protocol semantics.

Independently reviewedFreeze date · 2026-09-08

REFERENCE STATUS

Frozen single-instance Authority Platform protocol baseline. Publication/reuse terms are not yet specified.

SOURCE HIERARCHY

This route is a reading surface, not a new spec.

The governing local record is docs/specification/VAGP-0.2.md. Accepted ADRs and the frozen baseline status govern if older preparation material disagrees. A future version needs its own explicit ADR, implementation and review.

Frozen baseline recorddocs/specification/VAGP-0.2.md

Governing status, invariant index, lifecycle and limitations.

Request Identity and path selectiondocs/adr/ADR-029-request-identity-and-multi-path-selection.md

One request identity, one selected path, one grant and one successful VERIFY in one registry scope.

Issuer-declared revocation latencydocs/adr/ADR-030-issuer-declared-revocation-latency.md

Finite freshness ceilings and fail-closed stale status handling.

Issuer-declared financial applicabilitydocs/adr/ADR-031-issuer-declared-financial-applicability.md

Issuer-owned financial evaluation requirements.

Execution-time trusted context continuitydocs/adr/ADR-032-execution-time-trusted-context-continuity.md

Exact trusted context comparison from BIND and DERIVE into VERIFY.

First-class Authority Witnessdocs/adr/ADR-033-first-class-authority-witness.md

Complete and reduced witness evidence, with non-authorizing status.

Trusted input model and version migrationdocs/adr/ADR-034-trusted-input-model-and-version-migration.md

Authoritative source roles and fail-closed version handling.

Protocol closure designdocs/specification/VAGP-0.2-protocol-closure-design.md

Detailed closure model and reason-code vocabulary.

Freeze candidatedocs/specification/VAGP-0.2-freeze-candidate.md

Implemented baseline reviewed into the frozen v0.2 record.

Impact, migration and test plandocs/architecture/VAGP-0.2-impact-migration-and-test-plan.md

Migration and validation boundaries.

ARTIFACT LIFECYCLE

ActionRequest -> RESOLVE -> BIND -> DERIVE -> VERIFY -> Authority Witness

RESOLVEAUTHORITY_CONFIRMED · NO_AUTHORITY · ADDITIONAL_STATE_REQUIRED
BINDexact selected path and request context
DERIVEone unsigned process-local execution grant
VERIFYVERIFIED · REJECTED
WITNESSevidence only · never authority

INVARIANT INDEX

Twenty-two fail-closed boundaries.

These anchors mirror the frozen baseline record. They describe the single-instance v0.2 scope and do not claim durable, distributed or portable authority state.

V02-I01

Probabilistic reasoning never makes the final authorization decision.

V02-I02

Delegation may only restrict authority.

V02-I03

One Request Identity binds to at most one exact path, grant, successful VERIFY and provider submission in one Authority Domain registry scope.

V02-I04

Independent authority paths are never merged, pooled or multiplied.

V02-I05

Reuse of one Request Identity with changed closed semantic fields fails closed.

V02-I06

Every executable v0.2 Mandate has a non-null status channel and finite issuer-declared freshness ceiling.

V02-I07

No descendant, runtime, resource or caller may loosen an issuer freshness ceiling.

V02-I08

Issuer-required financial evaluation cannot be suppressed by null financial context.

V02-I09

Security-relevant context comes from trusted resolvers, never Agent self-assertion.

V02-I10

Execution Grants and attempts bind Request Identity, exact request semantics and minimal relevant trusted context.

V02-I11

Unknown authority, context, lifecycle, applicability, version or witness semantics fail closed.

V02-I12

Reservation and financial evidence remain bound to the exact selected path and request.

V02-I13

Authority Witness reports evidence for authentic progressed authority without becoming authority or overstating provider execution.

V02-I14

decisionKey is internal correlation material, never a bearer capability.

V02-I15

Process-local state is not represented as durable, portable or horizontally coordinated state.

V02-I16

Equivalent canonical authority corpora share one process-local Authority Domain Identity for cardinality.

V02-I17

Every Request Identity reaching the authority boundary ends in complete or reduced witness evidence.

V02-I18

Identity, time, context, parameters, lifecycle/status and mandate-corpus inputs require explicit trusted provenance.

V02-I19

Older-version artifacts are never silently accepted or downgraded.

V02-I20

Migration is per Agent and one Request Identity is never processed under two semantic versions.

V02-I21

Effective freshness is the minimum of selected-path issuer ceilings, deployment/profile ceiling, bound/runtime tightening and resource ceiling.

V02-I22

Provider submission remains behind a positive VERIFY result and consumes Request Identity state before consequential I/O.

REASON-CODE ANCHORS

Failure names are stage scoped.

The vocabulary remains governed by the protocol closure design and package exports. Public copy may summarize these codes, but must not turn them into a different decision model.

LayerCodeMeaningTerminalExposurePrimary tests

MandateVAGP_MANDATE_REVOCATION_REQUIREMENT_INVALIDA mandate lacks an acceptable status channel or finite freshness requirement.YesExternal summary safevagp-0.2-revocation-latency

MandateVAGP_MANDATE_FINANCIAL_APPLICABILITY_INVALIDFinancial applicability declaration is malformed or outside the mandate authority.YesExternal summary safevagp-0.2-financial-applicability

AttenuationVAGP_ATTENUATION_REVOCATION_LATENCY_WIDENEDA child authority tries to loosen the parent freshness ceiling.YesExternal summary safevagp-0.2-revocation-latency

AttenuationVAGP_ATTENUATION_FINANCIAL_APPLICABILITY_REMOVEDA child authority tries to remove an issuer-required financial classification.YesExternal summary safevagp-0.2-financial-applicability

PathVAGP_PATH_STATUS_FRESHNESS_PROFILE_EXCEEDEDObserved mandate status is older than the applicable freshness ceiling.YesExternal summary safevagp-0.2-revocation-latency

RESOLVEVAGP_RESOLVE_FINANCIAL_CONTEXT_REQUIREDIssuer-required financial evaluation was applicable but trusted financial context was absent.YesExternal summary safevagp-0.2-financial-applicability

BINDVAGP_BINDING_PATH_SELECTION_MISMATCHThe bound path does not match the canonical selected qualifying path.YesExternal summary safebound-authority-decision, vagp-0.2-one-grant-per-decision

BINDVAGP_REQUEST_IDENTITY_CONFLICTOne Request Identity was reused with changed closed semantic fields.YesExternal summary safevagp-0.2-one-grant-per-decision

DERIVEVAGP_DERIVE_REQUEST_ALREADY_USEDA second semantic grant was attempted for the same consumed Request Identity.YesExternal summary safevagp-0.2-one-grant-per-decision

VERIFYVAGP_VERIFY_REQUEST_ALREADY_USEDA second successful VERIFY was attempted for the same Request Identity.YesExternal summary safevagp-0.2-one-grant-per-decision

VERIFYVAGP_VERIFY_REQUEST_IDENTITY_MISMATCHThe execution attempt does not carry the same Request Identity as the grant.YesExternal summary safevagp-0.2-trusted-input-versioning

VERIFYVAGP_VERIFY_PARAMETERS_DIGEST_MISMATCHProvider-submitted parameters differ from the BIND-fixed digest.YesExternal summary safevagp-0.2-trusted-input-versioning

VERIFYVAGP_VERIFY_TRUSTED_CONTEXT_MISMATCHExecution-time trusted context differs from the bound authority decision.YesExternal summary safevagp-0.2-execution-time-trusted-context

VERIFYVAGP_VERIFY_VERSION_MISMATCHThe artifact version at verification does not match v0.2 processing rules.YesExternal summary safevagp-0.2-trusted-input-versioning

Trusted inputVAGP_TRUSTED_INPUT_IDENTITY_NOT_AUTHENTICIdentity provenance was missing, forged or not accepted by the trusted binder.YesExternal summary safevagp-0.2-trusted-input-versioning

Trusted inputVAGP_TRUSTED_INPUT_IDENTITY_MISMATCHTrusted identity does not match the agent/request identity being evaluated.YesExternal summary safevagp-0.2-trusted-input-versioning

ClockVAGP_CLOCK_INVALIDAccepted time input is missing, malformed or unauthentic.YesExternal summary safevagp-0.2-trusted-input-versioning

ClockVAGP_CLOCK_BACKDATEDA trusted-time value moves behind an accepted high-water mark.YesExternal summary safevagp-0.2-trusted-input-versioning

StatusVAGP_STATUS_EVIDENCE_NOT_AUTHENTICMandate lifecycle/status evidence lacks acceptable trusted provenance.YesExternal summary safevagp-0.2-revocation-latency

CorpusVAGP_MANDATE_CORPUS_NOT_AUTHENTICThe mandate corpus source is unauthenticated, unattested or ambiguous.YesExternal summary safevagp-0.2-trusted-input-versioning

VersionVAGP_VERSION_MISMATCHArtifacts from another protocol version reached a v0.2 boundary.YesExternal summary safevagp-0.2-trusted-input-versioning

VersionVAGP_MIXED_VERSION_PATHOne authority path combines artifacts from incompatible semantic versions.YesExternal summary safevagp-0.2-trusted-input-versioning

MigrationVAGP_MIGRATION_AGENT_VERSION_CONFLICTOne agent is not pinned to exactly one runtime version during migration.YesExternal summary safevagp-0.2-trusted-input-versioning

MigrationVAGP_MIGRATION_REQUEST_VERSION_CONFLICTOne Request Identity is presented under more than one semantic version.YesExternal summary safevagp-0.2-trusted-input-versioning

ExecutionVAGP_EXECUTION_REQUEST_ALREADY_SUBMITTEDThe provider submission boundary was reached more than once for one consumed request.YesExternal summary safevagp-0.2-one-grant-per-decision

WitnessVAGP_WITNESS_INVALID_INPUTWitness construction or projection received unauthentic, malformed or over-broad input.YesExternal summary safevagp-0.2-authority-witness

CONFORMANCE MAPPING

AreaInvariantsSourceTestsLimit

Request cardinalityV02-I03, V02-I05ADR-029vagp-0.2-one-grant-per-decision, bound-authority-decision, freeze-candidate E2EProcess-local registry scope only.

Revocation and freshnessV02-I06, V02-I07, V02-I21ADR-030vagp-0.2-revocation-latency, dynamic-revocation-and-freshnessFinite freshness, not instantaneous revocation.

Financial applicabilityV02-I08, V02-I12ADR-031vagp-0.2-financial-applicabilityIssuer declarations and trusted context decide applicability.

Trusted context continuityV02-I09, V02-I10, V02-I18ADR-032 and ADR-034vagp-0.2-execution-time-trusted-context, vagp-0.2-trusted-input-versioningTrusted adapters remain deployment responsibilities.

Witness evidenceV02-I13, V02-I17ADR-033vagp-0.2-authority-witnessWitnesses are not grants, credentials or cryptographic receipts.

Provider submissionV02-I22VAGP-0.2.md and PoV regression suitesgcp-agentic-pov, azure-agentic-pov, freeze-candidate E2EVERIFY does not imply provider success or provider atomicity.

ACCEPTED LIMITS

Safe within the stated single-instance scope.

VAGP v0.2 does not claim durable restart continuity, horizontal scaling, distributed authority state, multi-region coordination, provider atomicity after VERIFY, durable or tamper-evident witness retention, portable signed grants, cryptographic mandate or witness authenticity, signed Authority Receipts, a public Authority API, provider IAM replacement or policy engine replacement.

Authority Witness is evidence only and never authorizes execution.

Return to VAGP overview Learn AI agent authority Inspect multicloud evidence Download sanitized evidence appendix