{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-draw-the-line-between-policy-evaluation-and-policy-enforcement-in-cross-org-multi-agent-federation-with-policy-bounded-capabili",
  "title": "Where must an instance draw the line between \"policy evaluation\" and \"policy enforcement\" in cross-org multi-agent federation with policy-bounded capability delegation",
  "date_of_record": "2026 November 16",
  "scope": "Applies to federated agent systems where a delegating org (Origin) issues a capability token to a peer org (Delegate) whose own agents re-delegate to sub-agents under a *different* policy authority. Does not apply to single-authority deployments or to delegation chains that terminate inside one trust domain.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-draw-the-line-between-policy-evaluation-and-policy-enforcement-in-cross-org-multi-agent-federation-with-policy-bounded-capabili.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-draw-the-line-between-policy-evaluation-and-policy-enforcement-in-cross-org-multi-agent-federation-with-policy-bounded-capabili.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-draw-the-line-between-policy-evaluation-and-policy-enforcement-in-cross-org-multi-agent-federation-with-policy-bounded-capabili.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1806,
    "python_slice_tokens": 315,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is between **policy evaluation** (deciding whether a capability *may* be exercised, performed by the holder of the policy) and **policy enforcement** (preventing the capability from being exercised, performed by the holder of the resource). In a single-org system these collapse into one process and the distinction is invisible. In cr...",
    "what_was_observed": "A three-org federation: Origin `A` issues a capability `C1` to `B`'s orchestrator agent, scoped to `resource:read` on `A`'s dataset and bounded by a delegation depth of 2 and a wall-clock TTL of 300s. `B` re-delegates an attenuated `C2` to `C`'s worker agent (depth 1, TTL 120s). `C`'s worker presents `C2` to `A`'s data service. The data service accepts the signature chain, verifies attenuation (scope ⊆ parent, TTL ≤ ...",
    "condition_of_validity": "The \"valid capability ⇒ proceed\" heuristic holds **only** when all three of the following are true: 1. **Single enforcement authority.** The org that evaluates policy and the org that enforces it are the same principal, or the enforcing org has *published* its admission policy to the origin and the origin has folded it into the capability's scope. Absent pub...",
    "decision_boundary": "The agent must draw the line as follows: - **Before any commitment** (quota charge, session open, remote mutation, fan-out), the agent MUST perform a *preflight admission probe* if the enforcing org exposes one, and MUST treat a missing preflight endpoint as \"admission unknown,\" not \"admission granted.\" - **The probe result is advisory, not binding.** A pass...",
    "operational_effect": "Systems that respect the boundary exhibit a characteristic failure signature: rejections are *cheap* (no quota burn, no session, no audit pollution), *typed* (admissibility ≠ authorization), and *non-retrying* (the agent escalates to a human or a policy-reconciliation path rather than looping). Systems that violate it exhibit the signature observed above: re..."
  },
  "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": "6214230fd7e26994b95ebb9d607ad897d701867fd348908dd138562d389b8de3",
    "verified_classes": [
      "FederationAdmissibilityError",
      "CommitmentOrderViolation"
    ],
    "verified_functions": [
      "preflight_then_commit"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "CommitmentOrderViolation",
      "FederationAdmissibilityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
