{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-trust-anchor-divergence-during-cross-org-agent-federation-and-why-reputation-exchange-masks-it-until-policy-enforceme",
  "title": "What structural signals indicate trust anchor divergence during cross-org agent federation (and why reputation exchange masks it until policy enforcement)",
  "date_of_record": "2026 November 18",
  "scope": "Applies to federations of autonomous agents where each participating organization publishes a trust anchor (root key or policy issuer) that peers use to validate delegated credentials, and where reputation is exchanged as a secondary signal. Does not apply to single-org agent meshes, nor to federations with a single shared root of trust under one administrative domain.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-trust-anchor-divergence-during-cross-org-agent-federation-and-why-reputation-exchange-masks-it-until-policy-enforceme.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-trust-anchor-divergence-during-cross-org-agent-federation-and-why-reputation-exchange-masks-it-until-policy-enforceme.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-trust-anchor-divergence-during-cross-org-agent-federation-and-why-reputation-exchange-masks-it-until-policy-enforceme.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1560,
    "python_slice_tokens": 315,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two failure classes that look identical at the API surface but have different remediation paths: 1. **Reputation divergence** — peers disagree about an agent's score because their observations differ. This is expected, self-correcting, and bounded by the reputation exchange protocol's convergence properties. 2. **Trust anchor divergence** — peers d...",
    "what_was_observed": "During a multi-week federation run across six orgs with independent anchors: - Reputation rank correlation (Spearman) between all pairs stayed above 0.94 throughout. No alert fired. - Policy decisions on the *same* delegated credential diverged by org pair. Org A accepted a delegation chain that Org B rejected with `untrusted_issuer`. The credential was identical; the anchors were not. - The divergence appeared only ...",
    "condition_of_validity": "This analysis holds when all of the following are true: - Each org's anchor is independently rotated on its own schedule (no coordinated ceremony). - Delegated credentials carry an issuer chain that terminates at an org anchor, and validation is performed locally against a pinned or cached anchor set. - Reputation messages are signed by the *exchanging* peer...",
    "decision_boundary": "The operative rule: **treat reputation convergence as uninformative about anchor agreement; monitor anchor-pin set divergence directly.** Concretely, before trusting any \"federation healthy\" signal derived from reputation, compute the symmetric difference between each peer's pinned anchor fingerprint set and the federation directory's published set. If that ...",
    "operational_effect": "When anchor divergence is present but reputation converges, the federation enters a state where: - Each org's agents make locally correct policy decisions that are globally inconsistent. - Audit logs show no errors — only disagreements, which are harder to alert on because each side's decision is defensible. - The split becomes visible only at the moment the..."
  },
  "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": "f89c7aee273ea8a37812d9feedea8adac58b1ad8e2aafdb8a9b937c8da3f5c05",
    "verified_classes": [
      "AnchorDivergenceError",
      "FederationView"
    ],
    "verified_functions": [
      "fingerprint",
      "check_anchor_agreement",
      "enforce_cross_org_decision"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "AnchorDivergenceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
