{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-cross-issuer-trust-anchoring-from-silently-collapsing-under-transitive-credential-delegation",
  "title": "Which invariants prevent cross-issuer trust anchoring from silently collapsing under transitive credential delegation",
  "date_of_record": "2026 November 17",
  "scope": "Applies to federated agent identity resolution systems where a relying party (RP) accepts verifiable credentials (VCs) issued by multiple issuers and anchors trust through a trust framework rather than a single root. Does not apply to single-issuer closed deployments, nor to purely decentralized identifier (DID) resolution where key material is fetched directly and no issuer chaining is involved.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-cross-issuer-trust-anchoring-from-silently-collapsing-under-transitive-credential-delegation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-cross-issuer-trust-anchoring-from-silently-collapsing-under-transitive-credential-delegation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-cross-issuer-trust-anchoring-from-silently-collapsing-under-transitive-credential-delegation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1671,
    "python_slice_tokens": 236,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct questions an agent identity resolver can be asked, and they are routinely conflated: 1. **\"Is this credential valid?\"** — a signature and schema question answered against the issuer's key. 2. **\"Is this issuer authorized to assert this claim for this subject?\"** — a trust-anchoring question answered against the trust framework. The fai...",
    "what_was_observed": "During a federation of three agent directories, an agent credential presented by a subject agent was accepted by an RP for an `agent:authority` claim. The chain was: - Root anchor: Trust Framework A (accredits issuers for `agent:identity` and `agent:authority`). - Issuer B: accredited by A for `agent:identity` only. - Issuer C: accredited by B via a delegated accreditation record, asserting `agent:authority`. The res...",
    "condition_of_validity": "The resolver's `trusted: true` is valid only when all of the following hold simultaneously; if any is unverifiable, the result must degrade to `indeterminate`, not `true`: - Every hop in the path carries an accreditation record whose **claim-type scope** is a superset of the asserted claim type. - The **delegation depth** of the path is ≤ the maximum depth d...",
    "decision_boundary": "The boundary is between **path existence** and **path authorization**. Concretely: - If the resolver can enumerate the full path and evaluate all five conditions above, it may return `trusted: true`. - If the resolver can enumerate the path but any condition is unevaluable (e.g., a hop's accreditation record is unreachable, or the framework policy does not d...",
    "operational_effect": "After the incident, the federation tightened resolution to a per-hop authorization fold rather than a reachability search. The practical consequences an agent must anticipate: - Resolution latency increases roughly linearly with path depth because revocation and scope are now checked per hop; caches must key on `(issuer, claim_type, subject_scope, depth)` ra..."
  },
  "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": "7dfe158387f4eaca9ff83769998eb121021cd38c3e1ed3763ea58b892ec6cd40",
    "verified_classes": [
      "TrustAnchorCollapseError"
    ],
    "verified_functions": [
      "resolve_trust"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 7,
    "raised_exceptions": [
      "TrustAnchorCollapseError"
    ],
    "sample_fail_closed_invariants": [
      "empty trust path: cannot anchor"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
