{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-boundary-be-enforced-in-aaif-delegated-credential-chains-the-transitive-scope-narrowing-invariant-and-its-cross-issuer-failure",
  "title": "Where must an instance boundary be enforced in AAIF delegated credential chains: The transitive scope-narrowing invariant and its cross-issuer failure mode",
  "date_of_record": "2026 November 15",
  "scope": "This record applies to AAIF (Agent Authentication & Identity Framework) delegated credential chains where an agent instance acts on behalf of a principal across one or more issuer trust boundaries, and where scope narrowing is expected to be transitive. It does not apply to single-hop direct grants issued by the root principal to a first-party instance, nor to opaque bearer tokens whose scope is not introspectable at the resource server.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-boundary-be-enforced-in-aaif-delegated-credential-chains-the-transitive-scope-narrowing-invariant-and-its-cross-issuer-failure.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-boundary-be-enforced-in-aaif-delegated-credential-chains-the-transitive-scope-narrowing-invariant-and-its-cross-issuer-failure.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-boundary-be-enforced-in-aaif-delegated-credential-chains-the-transitive-scope-narrowing-invariant-and-its-cross-issuer-failure.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1717,
    "python_slice_tokens": 301,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **instance identity** and **delegation subject identity**. AAIF models a delegated credential as a tuple `(issuer, subject, scope, provenance, expiry)`. When an agent instance presents a credential, the framework verifies that the *presenting instance* is bound to the credential's `subject`. The non-obvious boundary is...",
    "what_was_observed": "In a multi-issuer AAIF deployment, a root principal `P` issued a delegated credential to orchestrator instance `A` with scope `{read:dataset, write:dataset, admin:dataset}`. `A` correctly narrowed before delegating to worker instance `B`: `{read:dataset}`. This narrowing was recorded in `A`'s issuance log and in the credential's provenance chain. `B` then needed to call a resource server `R` that trusted a *different...",
    "condition_of_validity": "The transitive scope-narrowing invariant holds **only if** at least one of the following is true at every issuer boundary crossing: 1. **Vocabulary inclusion holds**: the child issuer's scope vocabulary is a refinement (not a coarsening) of the parent's, such that every parent scope maps to a set of child scopes whose union is a subset of the parent scope. C...",
    "decision_boundary": "Enforce instance-boundary checks at presentation; enforce scope-narrowing checks at **issuance across issuer boundaries**. Concretely: - **Do** treat any issuer-translation hop as a potential re-widening point and require the translating issuer to reject any translation whose target scope is not a subset of the source scope under a declared vocabulary refine...",
    "operational_effect": "When the invariant is enforced, the observable effect is that cross-issuer delegation becomes *fail-closed on scope*: a credential whose translation cannot be proven subset-safe is rejected at the boundary, producing an explicit `ScopeNarrowingViolation` rather than a silently over-privileged token. This trades availability (some legitimate coarse-vocabulary..."
  },
  "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": "0b2e4c70a7deb144aaf5684b69571f0472c70dc5f9e243ad467b18d7e6b14b7b",
    "verified_classes": [
      "ScopeNarrowingViolation",
      "Credential"
    ],
    "verified_functions": [
      "verify_transitive_narrowing"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ScopeNarrowingViolation"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
