{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-to-complete-an-a2a-capability-handshake-with-a-federated-peer-across-organizational-boundaries",
  "title": "Under what conditions must an instance refuse to complete an A2A capability handshake with a federated peer across organizational boundaries",
  "date_of_record": "2026 November 17",
  "scope": "Applies to Agent-to-Agent (A2A) federation handshakes where the calling agent and the callee agent are governed by different trust domains (distinct orgs, distinct signing roots, distinct policy engines). Does not apply to intra-org A2A where both agents share a control plane and a single policy authority; in that case the negotiation is a configuration lookup, not a trust decision.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-complete-an-a2a-capability-handshake-with-a-federated-peer-across-organizational-boundaries.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-complete-an-a2a-capability-handshake-with-a-federated-peer-across-organizational-boundaries.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-complete-an-a2a-capability-handshake-with-a-federated-peer-across-organizational-boundaries.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1507,
    "python_slice_tokens": 310,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A capability handshake under A2A is usually modeled as a negotiation: the caller presents an `AgentCard`, the callee replies with a `Capabilities` manifest, and both sides intersect their supported skill sets, transports, and auth schemes. The intuitive failure model is *negotiation failure* — no intersection, so the call aborts cleanly. The non-obvious boun...",
    "what_was_observed": "In a federation between two orgs, the caller's `AgentCard` carried a `securitySchemes` block referencing an OAuth2 issuer. The callee's policy engine had a stale allowlist that still contained the issuer's *previous* JWKS endpoint. Because the JWT `kid` happened to collide with a key still cached from the old endpoint, signature verification returned valid. The handshake completed. The capability intersection was non...",
    "condition_of_validity": "The handshake is sound **only if** all of the following hold at the moment of completion, not at the moment of card retrieval: 1. The peer's signing chain resolves to a trust anchor present in the local policy engine's *current* anchor set, and that anchor has not been revoked since the card was fetched. 2. Every key used to verify the card is fresh — resolv...",
    "decision_boundary": "The boundary is *verifiability of identity at completion time*, not *parseability of the card* or *intersectability of capabilities*. Three cases sit on the refuse side and are routinely misclassified as success: - **Stale-key cache hit.** Signature verifies against a cached key whose source endpoint has rotated. Refuse; re-resolve. - **Issuer-scoped grant r...",
    "operational_effect": "Treating this boundary correctly converts a class of silent trust-widening incidents into loud, attributable refusals. The cost is a small increase in handshake latency (live JWKS resolution on cache miss) and a small increase in false refusals during key rotation windows. The benefit is that the effective trust set is always reconstructible from current anc..."
  },
  "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": "185b0f0d0b7a669d48c5ff42104fe3c256dd58bcfc511e6a99bd380806d09d3e",
    "verified_classes": [
      "FederationHandshakeRefused",
      "HandshakeContext"
    ],
    "verified_functions": [
      "complete_handshake"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "FederationHandshakeRefused"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
