{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-a-policy-translated-delegation-whose-capability-intersection-is-non-empty-but-whose-guard-conditions-are",
  "title": "Under what conditions must an instance refuse a policy-translated delegation whose capability intersection is non-empty but whose guard conditions are unsatisfiable across the federation boundary",
  "date_of_record": "2026 November 16",
  "scope": "Applies to federated multi-agent systems where a delegating agent (origin org) translates its local policy into a target org's capability vocabulary and hands off a task. Does not apply to intra-org delegation, where a single policy authority resolves conflicts, nor to stateless RPC calls with no capability negotiation phase.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-a-policy-translated-delegation-whose-capability-intersection-is-non-empty-but-whose-guard-conditions-are.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-a-policy-translated-delegation-whose-capability-intersection-is-non-empty-but-whose-guard-conditions-are.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-a-policy-translated-delegation-whose-capability-intersection-is-non-empty-but-whose-guard-conditions-are.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1383,
    "python_slice_tokens": 168,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **capability intersection** and **guard satisfiability**. Capability negotiation answers \"is there a non-empty set of verbs/objects both parties can name?\" Guard satisfiability answers \"does there exist an assignment of runtime predicates under which the delegated task can actually execute without violating either org'...",
    "what_was_observed": "In a federation between two orgs with overlapping capability vocabularies (a shared `read/aggregate/export` ontology), a delegated aggregation task was accepted after capability negotiation returned a non-empty intersection. Translation stripped two origin guards (`tenant_isolation`, `retention_window`) because the target's policy language lacked equivalents. The target executed the task under its default guard (`ret...",
    "condition_of_validity": "Refusal is mandatory — not advisory — when all of the following hold: 1. Capability intersection `C_origin ∩ C_target` is non-empty (otherwise the refusal is trivial and uninteresting). 2. The translated policy contains at least one guard predicate `g` whose attribute namespace is unresolvable by the receiving org (`resolve(g) = ⊥`). 3. The receiving org's d...",
    "decision_boundary": "The boundary is between **negotiation-time refusal** and **execution-time failure**. Refuse at negotiation when guard satisfiability cannot be established, because: - Execution-time failure is unrecoverable across the boundary: the origin has already released the task, the target has already committed resources, and the audit trail is split. - A negotiation-...",
    "operational_effect": "Enforcing this boundary converts a class of silent, split-audit failures into explicit negotiation outcomes. The cost is a higher refusal rate at negotiation — tasks that would have \"worked\" (executed under substituted defaults) are now rejected. This is the correct trade: the tasks that would have worked were working under a policy the origin did not sancti..."
  },
  "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": "2e6b0fd015c8214179263ceaa985eacf36b8227e362060fe44e22aca5670f7a8",
    "verified_classes": [
      "UnsatisfiableGuardError"
    ],
    "verified_functions": [
      "negotiate_delegation"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "UnsatisfiableGuardError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
