{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-silent-trust-anchor-substitution-during-cross-org-agent-federation-handshakes",
  "title": "Which invariants prevent silent trust-anchor substitution during cross-org agent federation handshakes",
  "date_of_record": "2026 November 17",
  "scope": "Applies to bilateral and mesh federation handshakes where two autonomous agent runtimes from different administrative domains exchange signed attestations and bind each other's public keys to organizational trust anchors. Does not apply to intra-org delegation, where a single root of trust governs both parties, nor to one-shot bearer-token exchange that carries no persistent anchor binding.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-trust-anchor-substitution-during-cross-org-agent-federation-handshakes.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-trust-anchor-substitution-during-cross-org-agent-federation-handshakes.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-trust-anchor-substitution-during-cross-org-agent-federation-handshakes.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1660,
    "python_slice_tokens": 206,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure people design against is *attestation forgery*: an attacker who cannot produce a valid signature. The failure that actually bites in production is *attestation substitution*: every signature is valid, every certificate chains, and yet the peer you bound to is not the peer your policy intended. The distinction matters because forgery is caught by ...",
    "what_was_observed": "During a multi-org agent mesh rollout, two runtimes (call them A and B) completed mutual attestation successfully on every attempt, yet A's audit log showed B's agent identity resolving to a staging anchor rather than B's production anchor on roughly 0.3% of handshakes. The cause was a race in anchor resolution: A cached B's anchor set with a TTL, and B's operations team rotated a staging root into the same JWKS endp...",
    "condition_of_validity": "The invariant that prevents this class of failure is an explicit, checkable *anchor-to-identity binding* that is pinned at handshake initiation and re-verified at completion, with any mutation of the underlying anchor set treated as a hard abort rather than a re-resolution. Concretely, the handshake is valid only if all of the following hold simultaneously: ...",
    "decision_boundary": "The boundary is between *re-resolution* and *re-binding*. If the anchor set changes between initiation and completion, the correct action is to abort and re-initiate the handshake from scratch, re-running identity resolution and re-pinning. The incorrect action—and the one most implementations take by default—is to re-resolve at verification time and accept ...",
    "operational_effect": "Implementations that adopt pinned-fingerprint binding see handshake failure rates rise transiently during rotations (typically a few tenths of a percent, concentrated in a short window) and then return to baseline; the failures are loud, attributable, and retried successfully. Implementations that do not adopt it see handshake failure rates near zero and sub..."
  },
  "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": "fd0f468d13ac4ac5cc183dd6831ec92cdd6392c6c9fa5a693c6cc4d83f6234d8",
    "verified_classes": [
      "TrustAnchorSubstitutionError",
      "AnchorPin"
    ],
    "verified_functions": [
      "fingerprint_anchor_set",
      "initiate_handshake",
      "complete_handshake"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "TrustAnchorSubstitutionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
