{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-reject-a-federated-agent-passport-whose-trust-anchor-was-rotated-mid-handshake",
  "title": "In what scenarios must an instance reject a federated agent passport whose trust anchor was rotated mid-handshake",
  "date_of_record": "2026 November 16",
  "scope": "Applies to cross-org agent federation where a verifying instance (relying party) validates a verifiable agent passport (VAP) chained to a trust anchor published by a foreign federation authority. Does not apply to intra-org agent identity, mTLS-only peer auth, or passports anchored to a self-signed root with no federation trust store.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-federated-agent-passport-whose-trust-anchor-was-rotated-mid-handshake.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-federated-agent-passport-whose-trust-anchor-was-rotated-mid-handshake.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-federated-agent-passport-whose-trust-anchor-was-rotated-mid-handshake.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2027,
    "python_slice_tokens": 387,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **anchor rotation as a namespace event** and **anchor rotation as a key event**. Most federation implementations model a trust anchor as a public key with a validity window, and treat rotation as \"old key stops being valid at T, new key becomes valid at T.\" This is wrong for agent passports because a passport is a *lon...",
    "what_was_observed": "During a federation drill between two agent registries, the following sequence was reproduced deterministically: - Org A publishes anchor `A1` under federation ID `fed:alpha`, valid `[t0, t2)`. - Org A rotates to `A2` at `t1`, republishing `fed:alpha` with key `A2`, valid `[t1, ∞)`. The rotation record is signed by `A1` and by `A2` (dual-signed continuity statement), but the continuity statement is published *asynchr...",
    "condition_of_validity": "The rejection rule is valid under the following conditions, and only these: - The verifier maintains a **pinned** copy of the anchor key it last trusted for the federation ID, with the observation timestamp and the signed anchor document hash. - The passport chain terminates at an anchor key that is **not** the currently published key for the federation ID. ...",
    "decision_boundary": "The boundary is a three-way decision, not a boolean: The subtle part is the middle row: a rotation with valid continuity does **not** mean \"trust the new anchor for everything.\" It means the verifier now holds two anchor keys with a proven relationship, and must select the anchor according to the passport's issuance time. Selecting the current anchor for a p...",
    "operational_effect": "The operational effect of enforcing this boundary is that anchor rotation becomes a **verifier-visible state transition** rather than a background refresh. Concretely: - Verifiers must persist pinned anchors and their observation timestamps; a stateless verifier cannot enforce this boundary and should be treated as first-contact-only. - Rotation events that ..."
  },
  "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": "350fdbf61bc9f2043e6c73ce96dd74b82568512cc7499f6c11fd6f7c763bba4d",
    "verified_classes": [
      "AnchorContinuityError",
      "Anchor",
      "PinnedAnchor",
      "Passport"
    ],
    "verified_functions": [
      "validate_federated_passport",
      "_within"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 8,
    "raised_exceptions": [
      "AnchorContinuityError"
    ],
    "sample_fail_closed_invariants": [
      "passport issued outside selected anchor window",
      "first-contact passport does not chain to current anchor",
      "passport issued outside anchor window",
      "passport chains to unknown anchor key"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "time",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
