{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a2a-v1-0-agent-card-discovery-failure-at-the-task-delegation-boundary",
  "title": "What structural signals indicate A2A v1.0 Agent Card discovery failure at the task-delegation boundary",
  "date_of_record": "2026 November 18",
  "scope": "Applies to cross-framework delegation where a client agent resolves a remote agent via an A2A v1.0 Agent Card and then submits a `tasks/send` or `tasks/sendSubscribe` request. Does not apply to same-process tool calls, MCP-style tool invocation, or intra-framework orchestration where the card is not the discovery surface.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a2a-v1-0-agent-card-discovery-failure-at-the-task-delegation-boundary.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a2a-v1-0-agent-card-discovery-failure-at-the-task-delegation-boundary.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a2a-v1-0-agent-card-discovery-failure-at-the-task-delegation-boundary.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1645,
    "python_slice_tokens": 353,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is this: **Agent Card discovery success is not delegation readiness.** A card can be fetched, parsed, schema-valid, and semantically plausible while the remote endpoint rejects every task because the card's declared `capabilities` and `skills` describe the *advertised* agent, not the *currently mounted* handler set. A2A v1.0 treats t...",
    "what_was_observed": "Across a mixed deployment (LangGraph-based client, CrewAI-based server, an AutoGen-based server, and a hand-rolled FastAPI server), the following patterns recurred: 1. **Card/route drift after redeploy.** The server's card was a committed static file; the skill handlers were registered dynamically. A rolling deploy that dropped one skill left the card advertising it for the full TTL of client-side card caches. Client...",
    "condition_of_validity": "This boundary analysis holds when *all* of the following are true: - The client resolves agents through the A2A well-known card rather than a static registry with pinned versions. - The card is served as a static or cached artifact, i.e. not derived per-request from the live handler registry. - The RPC surface (`tasks/send`, `tasks/sendSubscribe`, `tasks/get...",
    "decision_boundary": "The operational rule: **treat the Agent Card as a hint for candidate selection, never as a contract for delegation.** Concretely: - On `-32601` or a `Task` in `failed` state, do **not** retry the same task against the same card. Invalidate the cached card, re-fetch, and if the skill is still advertised, mark the `(agent_url, skill_id)` pair as *card-inconsis...",
    "operational_effect": "The practical consequence is that card freshness and handler liveness must be monitored as two independent signals. A card that is `200` and schema-valid tells you the discovery surface is alive; it tells you nothing about whether any skill is dispatchable. Teams that instrument only discovery health see a fully green mesh while delegation error rates climb,..."
  },
  "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": "b49ece4e107e3c7b49a009ef3b3a05a2b679228e1379c61e069488408a84099b",
    "verified_classes": [
      "CardInconsistentError",
      "CardCache"
    ],
    "verified_functions": [
      "delegate",
      "get",
      "put",
      "invalidate"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "CardInconsistentError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
