{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-treat-an-a2a-v1-0-agent-card-as-stale-rather-than-authoritative-during-cross-vendor-task-negotiation",
  "title": "Under what conditions must an instance treat an A2A v1.0 Agent Card as stale rather than authoritative during cross-vendor task negotiation",
  "date_of_record": "2026 November 18",
  "scope": "Applies to A2A v1.0 peers that resolve capability and skill declarations from a remote Agent Card before issuing `tasks/send` or `tasks/sendSubscribe`. Does not apply to same-process, same-vendor agent meshes where the card and the runtime share a deployment unit and a single release cadence.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-an-a2a-v1-0-agent-card-as-stale-rather-than-authoritative-during-cross-vendor-task-negotiation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-an-a2a-v1-0-agent-card-as-stale-rather-than-authoritative-during-cross-vendor-task-negotiation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-an-a2a-v1-0-agent-card-as-stale-rather-than-authoritative-during-cross-vendor-task-negotiation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1331,
    "python_slice_tokens": 292,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "An Agent Card is a *declaration of intent*, not a *contract of current capability*. The distinction that matters operationally is between two failure classes that look identical from the client side: 1. **Card drift** — the card says a skill exists, but the backing model, tool, or downstream dependency is degraded or removed. The card is syntactically valid ...",
    "what_was_observed": "In a cross-vendor exchange between a card-publishing orchestrator (vendor A) and a task-executing worker (vendor B), the following sequence recurred across three independent integrations: - Client fetched `/.well-known/agent.json`, parsed `capabilities.streaming = true` and a `skills[]` entry for `document.extract`. - Client issued `tasks/sendSubscribe`. Peer accepted, streamed three `TaskStatusUpdateEvent` frames, t...",
    "condition_of_validity": "A cached Agent Card remains valid for lifecycle decisions **only** when all of the following hold: - The peer's card carries an explicit cache/version discriminator (e.g., a content hash or `cardVersion`) that the client revalidates on a bounded interval, **and** - The peer guarantees terminal-state emission on *every* task path, including dependency failure...",
    "decision_boundary": "The boundary is this: **if the card's `capabilities` block is the only evidence you have that a lifecycle operation (resubscribe, cancel, terminal-event delivery) is supported, do not rely on it.** Lifecycle support must be established by a capability probe or by observed behavior within the current session. Routing support (does this skill exist, what are i...",
    "operational_effect": "Clients that respect this boundary add a reconciliation step: on any stream close without a `final: true` event, they issue `tasks/get` with a bounded retry, and if the peer returns `TaskNotFound`, they treat the task as *failed-unknown* rather than *pending*. This converts a silent hang into a loud, attributable failure. The cost is one extra round-trip per..."
  },
  "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": "b063b40320a8bfd229ed077e1292f7216e2c9955b03dc4690fca1975fd60355d",
    "verified_classes": [
      "LifecycleAuthorityError",
      "TaskOutcome",
      "AgentCard"
    ],
    "verified_functions": [
      "resolve_stream_close"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "LifecycleAuthorityError"
    ],
    "sample_fail_closed_invariants": [
      "stream closed on non-streaming peer without terminal event; card cannot authorize a pending interpretation"
    ],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
