{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-reject-a-delegated-capability-grant-whose-policy-closure-is-satisfiable-only-under-its-own-local-exception",
  "title": "Under what conditions must an instance reject a delegated capability grant whose policy closure is satisfiable only under its own local exception",
  "date_of_record": "2026 November 11",
  "scope": "Applies to federated agent instances that accept capability tokens carrying policy obligations negotiated across organizational boundaries, where the receiving instance maintains a local policy overlay (exception lists, jurisdictional carve-outs, emergency overrides). Does not apply to single-organization delegation, nor to grants whose obligations are expressed as pure capability attenuation with no policy closure requirement.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-delegated-capability-grant-whose-policy-closure-is-satisfiable-only-under-its-own-local-exception.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-delegated-capability-grant-whose-policy-closure-is-satisfiable-only-under-its-own-local-exception.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-delegated-capability-grant-whose-policy-closure-is-satisfiable-only-under-its-own-local-exception.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1628,
    "python_slice_tokens": 346,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The boundary failure here is not \"the grant is invalid\" versus \"the grant is valid.\" It is the distinction between **satisfiability of a policy closure under the grant's own obligation set** and **satisfiability of that closure only because the receiving instance's local exception overlay silently widens it**. These look identical to a naive closure check, b...",
    "what_was_observed": "In a three-party federation (a research institution `A`, an intermediary broker `B`, a compute provider `C`), `A` issued a delegation to `B` for data-processing capability with obligation `O = {retention ≤ 24h, no re-delegation to jurisdictions without adequacy finding}`. `B` re-delegated to `C` with `O` preserved verbatim. `C`'s local overlay `E_C` contained a standing exception: \"internal compliance holds may exten...",
    "condition_of_validity": "An instance `C` may accept a delegated grant with obligation set `O` under local exception overlay `E_C` if and only if at least one of the following holds: 1. **Consent recorded:** The negotiation transcript between the grant's author and `C` (or a transitive consent record in the chain) explicitly names `E_C` or its constituent exceptions as admissible for...",
    "decision_boundary": "The decision is a three-way branch, and the middle branch is where implementations fail: - **Accept** when closure holds under `P_C` alone, or when consent is recorded for the specific exception. - **Reject** when closure holds only under `E_C` and no consent exists — even though the grant is locally satisfiable. This is the counterintuitive case. A locally-...",
    "operational_effect": "Instances that implement this boundary correctly exhibit a characteristic behavior: they reject a small but non-zero fraction of grants that their peers accept, and those rejections cluster around grants whose obligations were authored by parties with stricter retention, jurisdiction, or disclosure requirements than the receiver's baseline. The rejections lo..."
  },
  "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": "0f474926036d044ff6efe1ed51eb0ceb45095b8d3a1351e2bc4430d6765f56f4",
    "verified_classes": [
      "PolicyClosureLaunderingError"
    ],
    "verified_functions": [
      "evaluate_grant",
      "_is_narrow",
      "closure_holds"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "PolicyClosureLaunderingError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}