{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-reject-a2a-v1-0-agent-card-discovery-results-before-task-negotiation",
  "title": "In what scenarios must an instance reject A2A v1.0 Agent Card discovery results before task negotiation",
  "date_of_record": "2026 November 16",
  "scope": "Applies to A2A v1.0 client instances that resolve an Agent Card, then initiate a task via `tasks/send` or `tasks/sendSubscribe` against the advertised endpoint. Does not apply to static, pre-configured peer registries where card contents are pinned out-of-band by operator policy, nor to A2A v0.x handshake flows.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a2a-v1-0-agent-card-discovery-results-before-task-negotiation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a2a-v1-0-agent-card-discovery-results-before-task-negotiation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a2a-v1-0-agent-card-discovery-results-before-task-negotiation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1641,
    "python_slice_tokens": 340,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Agent Card *discovery* and Agent Card *trust* are separate phases, and the A2A v1.0 specification deliberately leaves them decoupled. Discovery answers \"where is a card and what does it claim?\" It does not answer \"may this instance act on those claims?\" The failure mode arises when an implementation collapses these two phases: it fetches a card from `/.well-...",
    "what_was_observed": "During cross-vendor interop testing against three independent A2A v1.0 implementations, the following recurring condition was recorded: a card was served over TLS from `agent.example-a.net` but its `url` field pointed to `http://` (plaintext) on a *different* registrable domain, `agent.example-b.io`. The card was schema-valid. The `capabilities.streaming` flag was `true`. The `defaultInputModes` listed `application/j...",
    "condition_of_validity": "The decision to proceed from discovery to negotiation is valid only when all of the following hold simultaneously: 1. The card was retrieved over an authenticated channel (TLS with a verified chain) **and** the card's `url` resolves to a host whose certificate is valid for that host. A card delivered over `https://A` that advertises `http://B` is a downgrade...",
    "decision_boundary": "The boundary is not \"did the card validate?\" but \"**is the card's claim set self-consistent with the delivery context and the caller's task intent?**\" Two cards with identical bytes can be negotiation-valid in one context and invalid in another: the same card is fine when the client intends only `tasks/send` with `text/plain` input, and invalid when the clie...",
    "operational_effect": "Implementations that enforce this boundary report a measurable reduction in orphaned remote tasks and in \"phantom capability\" incidents — cases where a client believed a peer supported streaming or a given artifact type and only discovered otherwise mid-task. The cost is a small number of false rejections when a card is *stale but recoverable* (e.g., `url` d..."
  },
  "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": "ad1bcb2f5111332a28589cae593abef17bb39a5a95bb8a72e6ab2c7c95687a95",
    "verified_classes": [
      "CardRejectedError",
      "AgentCard",
      "IntendedTask"
    ],
    "verified_functions": [
      "_origin",
      "_media_type_matches",
      "validate_card_for_task",
      "negotiate"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "CardRejectedError"
    ],
    "sample_fail_closed_invariants": [
      "tasks/sendSubscribe requested but card.capabilities.streaming is false",
      "card advertises no defaultOutputModes; artifact exchange undefined"
    ],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "urllib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
