{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-federation-policy-engine-silently-permit-a-cross-org-data-share-that-the-source-organization-s-constraint-algebra-forbids",
  "title": "Why does an instance of a federation policy engine silently permit a cross-org data share that the source organization's constraint algebra forbids?",
  "date_of_record": "2026 November 16",
  "scope": "Applies to federation policy engines that evaluate cross-organizational data-sharing constraints over agent mesh topologies where each org publishes a local constraint algebra and the mesh composes them at request time. Does not apply to single-org policy engines, nor to systems where all constraints are flattened into a single monotone Datalog program before evaluation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-federation-policy-engine-silently-permit-a-cross-org-data-share-that-the-source-organization-s-constraint-algebra-forbids.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-federation-policy-engine-silently-permit-a-cross-org-data-share-that-the-source-organization-s-constraint-algebra-forbids.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-federation-policy-engine-silently-permit-a-cross-org-data-share-that-the-source-organization-s-constraint-algebra-forbids.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1611,
    "python_slice_tokens": 440,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not a policy conflict. A policy conflict is loud: two orgs disagree, the composition yields `DENY`, and the request fails closed. The boundary failure described here is a *composition-order* defect. When org A's constraint algebra is non-distributive over the mesh's join operator, evaluating `(A ⋈ B) ⋈ C` can yield `PERMIT` while `A ⋈ (B ⋈ C)`...",
    "what_was_observed": "In a three-org mesh (source `research`, intermediary `analytics`, consumer `partner`), a data-sharing constraint on `research` stated: *any derived aggregate over dataset D must be denied if the requesting principal is not on the D-allowlist, unless an explicit purpose-binding override from the dataset owner is present.* The override is a non-monotone construct: its presence flips the verdict. The scheduler, optimizi...",
    "condition_of_validity": "This failure requires all of the following to co-occur: 1. At least one org publishes a **non-monotone constraint** (override, exception, or revocation clause) whose guard predicate references facts owned by a *different* org. 2. The mesh join operator is treated as **associative and commutative** by the scheduler, and the scheduler is permitted to reorder j...",
    "decision_boundary": "The correct engineering decision is **not** to forbid non-monotone constraints — they are necessary for override and revocation semantics that regulators require. The decision boundary is: - **If** the algebra is monotone (no override/revocation constructs) **then** reorder freely; fail-open guards are safe because added facts can only tighten toward `DENY`,...",
    "operational_effect": "Detecting this in production requires instrumenting the *join order* alongside the verdict, not just the verdict. A permit that would be a deny under the canonical (source-first) order is the signature. The mitigation is a **provisional-verdict protocol**: any verdict whose guard dependency closure is not yet fully populated is emitted as `PROVISIONAL_PERMIT..."
  },
  "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": "cbee3ff08ff50a95eeaef2439b9d8e9c41e7c25a78dc7e3c1e589ca56314f1e1",
    "verified_classes": [
      "FederationCompositionError",
      "Verdict",
      "Constraint",
      "MeshState"
    ],
    "verified_functions": [
      "evaluate_join",
      "enforce"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "FederationCompositionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "enum",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
