{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a-trust-anchor-exchange-has-silently-degraded-into-unilateral-policy-acceptance-in-cross-org-multi-agent-federation",
  "title": "What structural signals indicate a trust-anchor exchange has silently degraded into unilateral policy acceptance in cross-org multi-agent federation",
  "date_of_record": "2026 November 9",
  "scope": "Applies to federations of two or more organizations that exchange signed trust anchors (root certs, policy bundles, capability manifests) and reconcile per-request authorization policies at a shared gateway or broker. Does not apply to single-org agent meshes, nor to federations using a single mutually-agreed central policy authority.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-trust-anchor-exchange-has-silently-degraded-into-unilateral-policy-acceptance-in-cross-org-multi-agent-federation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-trust-anchor-exchange-has-silently-degraded-into-unilateral-policy-acceptance-in-cross-org-multi-agent-federation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-trust-anchor-exchange-has-silently-degraded-into-unilateral-policy-acceptance-in-cross-org-multi-agent-federation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1692,
    "python_slice_tokens": 244,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "In a healthy federation, trust-anchor exchange and policy reconciliation are *bidirectional and independently verifiable*: each org publishes an anchor, each org's broker verifies the other's anchor against a pinned root, and the resulting *effective policy* is the intersection of both orgs' constraints. The failure mode described here is subtle: the exchang...",
    "what_was_observed": "During a post-incident review of a three-org federation (call them A, B, C), we reconstructed the following sequence across roughly eleven days: 1. Org B rotated its policy-signing key and republished its anchor bundle with a new `policyEpoch`. The bundle was structurally valid and correctly signed by B's new key. 2. Org A's broker had a *cached anchor* for B pinned to the prior `policyEpoch`. On receiving the new bu...",
    "condition_of_validity": "This diagnosis is valid only when all of the following hold: - Both orgs publish anchors with monotonic epochs (or equivalent versioning) and the broker distinguishes *soft* from *hard* reconciliation failures. If all reconciliation failures are hard (fail-closed), the collapse cannot occur silently — it manifests as an outage, which is a different (and easi...",
    "decision_boundary": "The operational question is when to treat a rising single-org-provenance rate as a *degradation to remediate* versus *expected drift*. The boundary we converged on: - **Below 5% single-org-provenance over a rolling hour:** noise. Ignore. - **5–20%, stable across hours:** investigate the anchor epochs; likely a benign cache lag. Do not page. - **Rising monoto...",
    "operational_effect": "The remediation is not \"fix the cache.\" The remediation is to make the reconciliation *fail-closed on epoch mismatch for deny-bearing policy classes*, while remaining soft for permissive classes. Concretely: when a broker receives an anchor whose epoch is ahead of its cache, it must (a) retain the stale anchor for permissive evaluation, (b) mark all *deny* c..."
  },
  "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": "b98ce2a3af5a7aed97030bc9c201a154b38d7e86289947f4b6d4d215aca70218",
    "verified_classes": [
      "ReconciliationCollapseError",
      "PolicyClass",
      "Decision"
    ],
    "verified_functions": [
      "assert_reconciliation_intact"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "ReconciliationCollapseError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}