{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-a-delegated-capability-token-it-cannot-attenuate-the-scope-narrowing-invariant-in-aaif",
  "title": "When must an instance refuse a delegated capability token it cannot attenuate: the scope-narrowing invariant in AAIF",
  "date_of_record": "2026 November 15",
  "scope": "This record applies to AAIF deployments where an agent instance receives a delegated capability token from a parent agent and may either use it directly or mint a further-attenuated child token. It does not apply to root-issued tokens, to token refresh flows, or to instances operating under a hard resource-server allowlist that short-circuits local scope checks.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-delegated-capability-token-it-cannot-attenuate-the-scope-narrowing-invariant-in-aaif.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-delegated-capability-token-it-cannot-attenuate-the-scope-narrowing-invariant-in-aaif.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-delegated-capability-token-it-cannot-attenuate-the-scope-narrowing-invariant-in-aaif.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1490,
    "python_slice_tokens": 261,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is the difference between **a token that is valid** and **a token that is attenuable by this instance**. AAIF delegation assumes monotonic narrowing: a child token's authority set must be a subset of the parent's authority set, and the child's constraints (expiry, audience, budget) must be at least as tight. Most implementations vali...",
    "what_was_observed": "In a three-tier deployment (orchestrator → planner → worker), the planner received tokens carrying a `resource_selector` constraint written in a Cedar-like predicate. The planner's policy engine understood a subset of that grammar and silently passed unknown predicates through to the worker unchanged, treating them as opaque strings. The worker's engine understood the full grammar. The result: a planner asked to atte...",
    "condition_of_validity": "The refusal-to-attenuate rule holds when all of the following are true: 1. The instance is minting a child token, not merely forwarding the parent. Forwarding an unmodified token is safe regardless of parseability, because no narrowing claim is made. 2. The parent token carries at least one constraint the instance's local evaluator cannot fully interpret, or...",
    "decision_boundary": "The boundary is drawn at *provability of subset*, not at *plausibility of subset*. An instance that cannot construct a proof that the child's authority set is contained in the parent's must refuse to mint, even when the child looks obviously narrower to a human reader. \"Obviously narrower\" is exactly the intuition that fails on negation, on set-complement op...",
    "operational_effect": "Instances that implement the rule surface a class of failures earlier and more cheaply: the planner in the case above would have refused to mint the combined-predicate child, forcing the worker to either use the parent token (correct, narrower than the buggy child) or request an issuer-attenuated token. The blast radius collapses from \"silent privilege expan..."
  },
  "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": "586ddf227688a6a15b147592cf6c0dff4919d468434d36b535e189835d10387a",
    "verified_classes": [
      "UnattenuableCapabilityError"
    ],
    "verified_functions": [
      "attenuate"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "UnattenuableCapabilityError"
    ],
    "sample_fail_closed_invariants": [
      "parent token failed validity checks; cannot attenuate",
      "child authority not provably a subset of parent authority; refuse to mint"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
