{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a-federation-trust-boundary-has-been-silently-inverted-by-policy-exchange-ordering",
  "title": "What structural signals indicate a federation trust boundary has been silently inverted by policy exchange ordering",
  "date_of_record": "2026 November 17",
  "scope": "Applies to cross-org multi-agent federations where trust is established via exchanged policy documents (capability grants, delegation chains, or signed policy bundles) and where agents act on behalf of principals across organizational boundaries. Does not apply to single-org agent meshes with a shared trust root, nor to stateless request/response gateways that re-authenticate on every hop.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-federation-trust-boundary-has-been-silently-inverted-by-policy-exchange-ordering.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-federation-trust-boundary-has-been-silently-inverted-by-policy-exchange-ordering.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-federation-trust-boundary-has-been-silently-inverted-by-policy-exchange-ordering.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1591,
    "python_slice_tokens": 272,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct notions of \"trust\" in a federation: **structural trust** (which orgs are permitted to speak to which, encoded in the topology of the trust graph) and **policy trust** (which specific capabilities an agent is granted at a given moment, encoded in exchanged policy documents). The common failure is not that either is wrong in isolation, b...",
    "what_was_observed": "In a three-org federation (A = resource owner, B = intermediary, C = downstream consumer), the intended trust topology was `A → B → C` for a delegated read capability on A's data store. Each org published a signed policy bundle on a shared exchange bus. Because bundles carried no explicit `grantor`/`grantee` role tag — only a `subject` and a `scope` — the receiving agents inferred direction from a heuristic: \"the org...",
    "condition_of_validity": "The \"last-writer-wins over received bundles\" resolution rule is valid **only** when every bundle carries an explicit, signed `grantor` and `grantee`, and when the applying agent rejects any bundle whose `grantor` does not already appear as a trusted peer in its own structural trust set. Under those conditions, ordering cannot invert an edge because the direc...",
    "decision_boundary": "The operational decision is whether to **fail closed on ambiguous direction** or **accept and reconcile later**. Fail-closed means: if a received bundle's grantor cannot be determined from signed fields alone, reject it and emit a structural alarm. This costs availability during schema-migration windows between orgs. Accept-and-reconcile means: apply the bun...",
    "operational_effect": "After the incident, the federation adopted signed `grantor`/`grantee` fields and a rule that any bundle lacking them is rejected at the exchange boundary with a structural alarm. The consistency sweep was retained as a backstop, checking the invariant: *for every effective edge `X → Y`, there exists a signed bundle with `grantor=X, grantee=Y`.* The sweep now..."
  },
  "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": "695de7029ebab327fbfda1104d18029a0b598a4ea79e3214fbbfaf9cfac5e8a6",
    "verified_classes": [
      "TrustEdgeInversionError",
      "PolicyBundle"
    ],
    "verified_functions": [
      "resolve_edge",
      "apply_bundles"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "TrustEdgeInversionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
