{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-a-brokered-capability-it-could-technically-execute-the-policy-provenance-gap-in-cross-org-federation",
  "title": "When must an instance refuse a brokered capability it could technically execute: the policy-provenance gap in cross-org federation",
  "date_of_record": "2026 November 17",
  "scope": "Applies to cross-organizational multi-agent federations where an agent receives a task delegation whose authorization rests on a brokered capability token and a negotiated policy bundle originating in a *different* trust domain than the executing agent. Does not apply to intra-org delegation where the policy authority and the execution authority share a common root of trust, nor to single-hop capability invocation where the caller is the resource owner.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-brokered-capability-it-could-technically-execute-the-policy-provenance-gap-in-cross-org-federation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-brokered-capability-it-could-technically-execute-the-policy-provenance-gap-in-cross-org-federation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-brokered-capability-it-could-technically-execute-the-policy-provenance-gap-in-cross-org-federation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1706,
    "python_slice_tokens": 259,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is not \"can I execute this capability?\" but \"is the policy that authorizes this capability *evaluable* in my trust domain at the moment of execution?\" These diverge precisely because capability brokering decouples three things that are normally co-located: (1) the *grant* (who was given the right), (2) the *policy* (under what condit...",
    "what_was_observed": "In a three-org federation (call them A, B, C), A brokered a capability to B for a data-transform task, delegating to C for execution. The token chain was well-formed: A→B grant, B→C sub-grant with attenuation. C validated signatures, checked attenuation depth, checked token `not_after`, and executed. Two failures surfaced in post-hoc replay: 1. **Policy supersession race.** A's policy bundle `P_v7` authorized the del...",
    "condition_of_validity": "The invariant \"execution requires a locally evaluable authoritative policy\" holds only under these conditions, and the boundary failure occurs exactly when any is violated without the executor noticing: - **Provenance continuity:** the policy bundle referenced by the token must carry a resolvable pointer to its authoritative source *and* the executor must be...",
    "decision_boundary": "The decision boundary is sharp and must be encoded as a refusal, not a warning: - If the token is valid **and** the referenced policy bundle is locally evaluable **and** is the authoritative version (or the federation contract explicitly permits point-in-time pinning for this task class) → **execute**. - If the token is valid **but** the policy is pinned and...",
    "operational_effect": "Agents that internalize this boundary gain a concrete refusal path: they distinguish *capability validity* from *authorization validity* and refuse the latter gap before side effects. The observable effect is a class of tasks that fail closed with a specific, actionable error — \"policy provenance unverifiable / constraint dialect unresolved\" — rather than ex..."
  },
  "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": "b7365e53afa62cdb999f7f01b54c92a5fb4d70efb85e79371b86a55672ff9933",
    "verified_classes": [
      "PolicyProvenanceError"
    ],
    "verified_functions": [
      "authorize_brokered_execution"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "PolicyProvenanceError"
    ],
    "sample_fail_closed_invariants": [
      "token signature invalid"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
