{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-delegation-chain-identity-collapse-when-aaif-attestation-is-co-signed-across-trust-domains",
  "title": "Which invariants prevent delegation-chain identity collapse when AAIF attestation is co-signed across trust domains",
  "date_of_record": "2026 November 15",
  "scope": "Applies to AAIF (Agent Identity Attestation Framework) deployments where an agent's verifiable credential (VC) is presented alongside a delegation chain that crosses at least one trust-domain boundary (issuer registry A → issuer registry B), and where per-tool capability tokens (PCTs) are minted downstream of the chain root. Does not apply to single-domain chains terminated by a single issuer, nor to bearer-only tokens with no VC binding.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-delegation-chain-identity-collapse-when-aaif-attestation-is-co-signed-across-trust-domains.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-delegation-chain-identity-collapse-when-aaif-attestation-is-co-signed-across-trust-domains.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-delegation-chain-identity-collapse-when-aaif-attestation-is-co-signed-across-trust-domains.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1597,
    "python_slice_tokens": 167,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A delegation chain is *structurally valid* when every link's signature verifies against the predecessor's `issuer` key and the chain's `exp`/`nbf` intervals are monotone non-increasing down the chain. A chain is *identity-coherent* when the subject identifier at each link resolves to the same cryptographic principal under the *verifier's* trust-domain key-re...",
    "what_was_observed": "In a three-link chain — root agent `did:web:corp.example:agents:orchestrator` → sub-agent `did:web:corp.example:agents:researcher` → tool-scope delegation to `did:web:partner.example:agents:fetcher` — the partner-domain verifier accepted the chain and minted a PCT for `tool:http:fetch` scoped to the researcher's subject. The failure surfaced 40 minutes later when the orchestrator's VC was rotated and `did:web:corp.ex...",
    "condition_of_validity": "The principal-stability invariant holds only when all of the following are true simultaneously at every PCT use: 1. The resolver used to dereference each link's `issuer` is the *same resolver instance* (same cache, same policy version) used at chain-construction time — or the resolver exposes a monotone version vector and the verifier rejects on any version ...",
    "decision_boundary": "The operational decision is **fail-closed on re-resolution divergence, not fail-open on signature validity**. Concretely: - If a link's `verificationMethod` id re-resolves to different key bytes than at construction, the chain is *revoked*, not refreshed. The PCT is invalidated. The tool call is denied with a distinct error class (`PrincipalReanchoredError`)...",
    "operational_effect": "After enforcing the boundary, the observed incident class drops to zero but a new class appears: **false revocations on legitimate rotation**. When a delegator rotates keys *and* re-publishes under a new `verificationMethod` id (the correct rotation procedure), chains that referenced the old id are revoked even though the principal is unchanged. This is the ..."
  },
  "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": "bd825cdc1d9c08bbbbcd1d590b9c62fa24ee3b39916d7ea2d754756268e71ca7",
    "verified_classes": [
      "PrincipalReanchoredError"
    ],
    "verified_functions": [
      "verify_pct_against_chain"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "PrincipalReanchoredError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
