{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-presents-a-valid-aaif-credential-whose-subject-binding-no-longer-matches-the-live-agent-process",
  "title": "What happens when an instance presents a valid AAIF credential whose subject binding no longer matches the live agent process",
  "date_of_record": "2026 November 16",
  "scope": "Applies to AAIF (Agent Authorization and Identity Framework) verifiable-credential flows where an autonomous agent presents a VC to an authorization service and the credential's `credentialSubject` binding is resolved against a live process identity at authorization time. Does not apply to pure bearer-token delegation, offline batch attestation, or cases where the credential is consumed only as a static capability grant with no liveness check.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-presents-a-valid-aaif-credential-whose-subject-binding-no-longer-matches-the-live-agent-process.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-presents-a-valid-aaif-credential-whose-subject-binding-no-longer-matches-the-live-agent-process.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-presents-a-valid-aaif-credential-whose-subject-binding-no-longer-matches-the-live-agent-process.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1264,
    "python_slice_tokens": 167,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There is a persistent confusion between *credential validity* and *subject binding validity*. A VC can be cryptographically valid — correct issuer signature, unexpired `validFrom`/`validUntil`, unrevoked status list — while the binding between the credential's subject and the agent process presenting it has silently decoupled. The signature attests that the ...",
    "what_was_observed": "In a multi-tenant orchestration environment, agents were issued AAIF credentials at spawn with `bindingCommitment = H(process_nonce || key_thumbprint)`. A credential cache keyed by `agent_id` (a stable logical identifier) served credentials across instance restarts. The authorization service verified the VC signature, checked the status list, and then — critically — verified the binding by recomputing `H(process_nonc...",
    "condition_of_validity": "The following invariant must hold for AAIF binding to be sound, and it is the thing that silently breaks: > For every authorization decision, the binding commitment in the presented credential must be recomputed against the *live, presenting* process, and a mismatch must be treated as a distinct, terminal, non-retryable identity error — not as a credential e...",
    "decision_boundary": "The decision boundary is not \"valid vs. invalid credential.\" It is a three-way split that must be made explicitly at the verifier: - **Signature/status failure** → credential is invalid → reject, and the presenting agent must obtain a new credential. Retryable only after re-issuance. - **Binding mismatch** → credential is valid but presented by the wrong sub...",
    "operational_effect": "After separating the taxonomy, the observed effects were: drifted instances were terminated within one authorization cycle instead of being admitted (eliminating the cross-tenant grant leakage), the retry livelock disappeared because `BindingMismatch` was classified as terminal-for-instance, and the credential cache was rekeyed by commitment so a restarted a..."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "e7c726d630274ef254c03f509e44c8deb66366f098421c48c1af28bf5bfbb9df",
    "verified_classes": [
      "BindingMismatchError",
      "InvalidCredentialError",
      "AACredential"
    ],
    "verified_functions": [
      "compute_binding",
      "authorize"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "BindingMismatchError",
      "InvalidCredentialError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
