{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-presents-a-delegated-credential-whose-scope-graph-is-acyclic-but-whose-attestation-chain-is-not",
  "title": "What happens when an instance presents a delegated credential whose scope graph is acyclic but whose attestation chain is not",
  "date_of_record": "2026 November 16",
  "scope": "Applies to AAIF delegated credentials where a principal issues a scoped token to an agent, and that agent re-delegates to a downstream agent with an attestation chain linking each hop. Does not apply to single-hop bearer tokens, nor to credential systems where scope is a flat set rather than a directed graph.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-presents-a-delegated-credential-whose-scope-graph-is-acyclic-but-whose-attestation-chain-is-not.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-presents-a-delegated-credential-whose-scope-graph-is-acyclic-but-whose-attestation-chain-is-not.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-presents-a-delegated-credential-whose-scope-graph-is-acyclic-but-whose-attestation-chain-is-not.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1553,
    "python_slice_tokens": 386,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "AAIF separates two orthogonal structures that are routinely conflated in implementation: 1. **The scope graph** — a directed graph of capability grants (e.g., `read:db/orders` → `read:db/orders/row` → `write:db/orders/row/status`). The invariant is that a delegated credential's scope must be a *subgraph* of the delegator's scope: no edge in the child may ref...",
    "what_was_observed": "A three-hop delegation was constructed: principal `P` → agent `A1` → agent `A2` → agent `A3`. At hop 3, `A3` presented a credential whose scope was correctly narrowed (`read:db/orders/row/status`), so the scope-subgraph check passed cleanly. However, the attestation chain contained the link `A2→A3` signed by a key that `A2` had itself received from `A1` via a prior, now-revoked delegation. Because the revocation was ...",
    "condition_of_validity": "The scope-subgraph check is a *necessary but not sufficient* condition for a delegated credential to be honored. It is sufficient only when the following hold simultaneously: - The attestation chain is a simple path (no repeated issuer key), AND - Every link's signing key was authorized at the link's `issued_at` timestamp, AND - Revocation of any link propag...",
    "decision_boundary": "An agent operating under AAIF delegation must treat the two checks as a conjunction, never as alternatives: - If the scope-subgraph check passes but the attestation chain contains a repeated issuer key, **reject** — the chain is forked or looped and the key-authorization table must be re-walked from the root. - If the chain is a simple path but any link's si...",
    "operational_effect": "The practical consequence is that AAIF verifiers must walk the attestation chain *independently* of the scope check, maintaining a set of seen issuer keys and consulting the key-authorization table at each link's timestamp. This roughly doubles verification cost per hop (two graph walks instead of one) and requires that revocation events be dual-written: onc..."
  },
  "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": "eb194a089e2769b5fa4881f37573823ca2d97230871d708148bc28b87b0fce4b",
    "verified_classes": [
      "AttestationChainError",
      "Link",
      "KeyAuthorizationTable"
    ],
    "verified_functions": [
      "verify_delegated_credential",
      "authorized_at"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "AttestationChainError"
    ],
    "sample_fail_closed_invariants": [
      "scope-subgraph narrowing check failed"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
