{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-reject-a-peer-s-agent-card-during-a2a-v1-0-discovery-despite-a-valid-signature",
  "title": "Under what conditions must an instance reject a peer's Agent Card during A2A v1.0 discovery despite a valid signature",
  "date_of_record": "2026 November 17",
  "scope": "Applies to A2A v1.0 Agent Card publication, retrieval, and signature verification between heterogeneous runtimes (e.g., a JVM-based orchestrator discovering a Python worker, or a Rust edge gateway discovering a Node.js planner) where the card carries a detached JWS over a canonicalized capability manifest. Does not apply to intra-process agent registration, nor to cards fetched over mutually authenticated transport where the signature is redundant.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-peer-s-agent-card-during-a2a-v1-0-discovery-despite-a-valid-signature.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-peer-s-agent-card-during-a2a-v1-0-discovery-despite-a-valid-signature.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-a-peer-s-agent-card-during-a2a-v1-0-discovery-despite-a-valid-signature.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1711,
    "python_slice_tokens": 396,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There is a persistent conflation between *signature validity* and *card admissibility*. A signature proves that the bytes of the Agent Card were produced by the holder of a given key. It does **not** prove that the card is internally consistent, that its declared capabilities are mutually satisfiable, or that the runtime that emitted it can actually honor th...",
    "what_was_observed": "Across a mixed fleet (Python 3.11 workers, a Go gateway, a TypeScript planner), the following recurring inadmissibility classes appeared in cards bearing valid detached JWS signatures: 1. **Canonicalization drift.** The emitter canonicalized the manifest with JSON-LD compaction using a context that resolved differently under the verifier's context loader (one resolved `@vocab` to a remote URL, the other to a bundled ...",
    "condition_of_validity": "A signature-valid Agent Card is admissible **only if** all of the following hold at the verifier: - The canonicalization function used to verify is byte-identical to the one the emitter used, *including* context resolution. If the verifier cannot pin the emitter's context bundle, it must treat the card as unverified-of-semantics even when the JWS verifies. -...",
    "decision_boundary": "The decision boundary is between **reject-at-discovery** and **admit-with-degradation**. Reject-at-discovery is correct when the inadmissibility is a *contradiction* (classes 2, 3, 4): no amount of negotiation can repair an unsatisfiable card, and admitting it wastes a handshake round-trip and pollutes peer-selection state. Admit-with-degradation is correct ...",
    "operational_effect": "Enforcing admissibility at discovery converts a class of distributed, hard-to-attribute negotiation stalls into a local, deterministic, loggable rejection with a specific reason code. In the observed fleet, moving contradiction checks from negotiation to discovery reduced median time-to-first-successful-invocation from a bimodal distribution (fast successes,..."
  },
  "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": "b92f9bfc504e0945f3df30c5578b820baa21f7e31264ae5c3fa53ce072812987",
    "verified_classes": [
      "CardInadmissibleError",
      "Card"
    ],
    "verified_functions": [
      "_version_tuple",
      "_range_contains",
      "assert_admissible",
      "discover",
      "__init__"
    ],
    "verified_functions_count": 5,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "CardInadmissibleError"
    ],
    "sample_fail_closed_invariants": [
      "SIG_INVALID",
      "VERSION_RANGE_INVERTED",
      "VERSION_NO_INTERSECTION",
      "CAPABILITY_CONTRADICTION"
    ],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
