{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-refuse-a-delegated-aaif-credential-rather-than-accept-it-under-scope-narrowing",
  "title": "In what scenarios must an instance refuse a delegated AAIF credential rather than accept it under scope-narrowing",
  "date_of_record": "2026 November 16",
  "scope": "Applies to any AAIF-conformant agent that receives a scoped delegation token (a *delegation grant*) from a parent principal and must decide whether to accept, narrow, or reject it before issuing downstream sub-delegations or performing the granted action. Does not apply to root credential issuance by the identity provider, nor to bearer tokens that carry no delegation chain metadata.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-a-delegated-aaif-credential-rather-than-accept-it-under-scope-narrowing.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-a-delegated-aaif-credential-rather-than-accept-it-under-scope-narrowing.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-a-delegated-aaif-credential-rather-than-accept-it-under-scope-narrowing.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1586,
    "python_slice_tokens": 356,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **scope-narrowing** (a legitimate, always-permitted transformation of a delegated credential) and **scope-disjointness with revocation shadow** (an illegitimate acceptance that silently resurrects authority the issuer already revoked). Both look identical at the wire level: a child agent presents a grant whose scope set is...",
    "what_was_observed": "In a three-tier delegation chain (orchestrator → planner → executor), the planner was revoked for the `filesystem:write:/tmp/staging` scope at epoch 41. The orchestrator's grant to the planner carried epoch 40. The planner had already, at epoch 39, issued a sub-grant to the executor for `filesystem:write:/tmp/staging/scratch`. On revocation, the executor's grant was not in the revocation set — only the planner's was....",
    "condition_of_validity": "Acceptance of a delegated grant is valid only when all of the following hold simultaneously: 1. **Subset:** `grant.scope ⊆ parent.scope` at presentation time. 2. **Epoch floor:** `grant.epoch ≥ parent.revocation_epoch` for every ancestor in the chain, not merely the immediate parent. 3. **Revocation-set disjointness:** `grant.scope ∩ ancestor.revoked_scopes ...",
    "decision_boundary": "The instance must **reject** the grant (not accept, not narrow further) when: - The grant's epoch is strictly less than any ancestor's current revocation epoch, even if the grant's scope is disjoint from the revoked scope. Epoch staleness is itself a signal that the chain has diverged. - The grant's scope intersects a revoked scope of any ancestor whose revo...",
    "operational_effect": "Enforcing the epoch-floor invariant converts a class of silent authority-resurrection bugs into loud, attributable rejections. The cost is that every delegation presentation must carry the full ancestor epoch vector (or a Merkle commitment to it), which increases token size linearly in chain depth. In practice chains deeper than four are rare, and the vector..."
  },
  "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": "e90b8a85d1888fc6d69547ab4bf9a18850ad9e1ac356d65b4d2826cc65a518f5",
    "verified_classes": [
      "StaleDelegationEpochError",
      "RevocationScopeOverlapError",
      "Grant",
      "RevocationRecord"
    ],
    "verified_functions": [
      "accept_delegation"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "PermissionError",
      "RevocationScopeOverlapError",
      "StaleDelegationEpochError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
