{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a2a-v1-0-agent-card-discovery-silently-succeed-against-a-stale-non-authoritative-card-and-then-fail-only-at-the-third-delegati",
  "title": "Why does an instance of A2A v1.0 Agent Card discovery silently succeed against a stale, non-authoritative card and then fail only at the third delegation hop?",
  "date_of_record": "2026 November 14",
  "scope": "Applies to A2A v1.0 (and draft-compatible v0.3+) cross-vendor agent delegation where the calling agent resolves a peer via Agent Card discovery (`/.well-known/agent.json` or registry-mediated resolution) and then chains tasks through one or more intermediary agents. Does not apply to single-hop, same-vendor, or statically-pinned-card deployments where the card digest is verified out-of-band.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a2a-v1-0-agent-card-discovery-silently-succeed-against-a-stale-non-authoritative-card-and-then-fail-only-at-the-third-delegati.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a2a-v1-0-agent-card-discovery-silently-succeed-against-a-stale-non-authoritative-card-and-then-fail-only-at-the-third-delegati.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a2a-v1-0-agent-card-discovery-silently-succeed-against-a-stale-non-authoritative-card-and-then-fail-only-at-the-third-delegati.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1429,
    "python_slice_tokens": 328,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct notions of \"the agent is reachable\" that A2A v1.0 conflates at the discovery layer: 1. **Card liveness** — the discovery endpoint returned an HTTP 200 with a structurally valid Agent Card whose `skills`, `capabilities`, and `securitySchemes` parse correctly. 2. **Card authority** — the returned card reflects the *current* task-lifecycl...",
    "what_was_observed": "In a three-hop delegation chain (Orchestrator → Vendor-A broker → Vendor-B worker), the orchestrator resolved Vendor-B's card successfully and initiated a task. The card advertised `capabilities.pushNotifications: true` and a `TaskState` set including `input-required`. The first two hops returned `submitted → working` transitions correctly. At the third hop, the worker had been upgraded to a build that removed `input...",
    "condition_of_validity": "The \"card parses ⇒ peer honors lifecycle\" invariant is only valid when **all** of the following hold: - The card's `version` and any `capabilities` extensions are matched against the executor's actual build, not merely schema-validated. - The discovery response carries a cache directive whose TTL is shorter than the executor's upgrade cadence, **or** the car...",
    "decision_boundary": "The operational decision is **whether to trust a resolved card directly or to perform an active lifecycle probe before delegating a stateful task.** - **Trust directly** when the task is stateless or single-transition (`message/send` with a self-contained payload that terminates in one round-trip), or when the card digest was pinned out-of-band by the caller...",
    "operational_effect": "Treating a parsed card as authoritative produces **silent hangs** rather than errors: the caller waits on a terminal state the executor will never send, burning the full task deadline before failing with an uninformative timeout. Downstream, this manifests as orphaned tasks on the worker (which did receive the continuation but rejected it internally) and inf..."
  },
  "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": "31f7ca1c0e1501318d60216e8b380108127fdf88821c02b79ba1d1a0f667b8bb",
    "verified_classes": [
      "StaleAgentCardError",
      "ResolvedCard"
    ],
    "verified_functions": [
      "verify_card_authority"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "StaleAgentCardError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
