{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-a-stale-a2a-v1-0-agent-card-is-being-trusted-during-task-negotiation",
  "title": "What structural signals indicate a stale A2A v1.0 agent card is being trusted during task negotiation",
  "date_of_record": "2026 November 16",
  "scope": "Applies to A2A v1.0 peer-to-peer deployments where an agent resolves a remote `AgentCard` via a well-known URI, caches it, and subsequently uses fields from that cached card (capabilities, `defaultInputModes`, `skills`, task-lifecycle extensions) to negotiate a `Task`. Does not apply to registry-mediated discovery with push-based invalidation, nor to A2A deployments that pin card versions per-request via an explicit `cardVersion` query parameter.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-stale-a2a-v1-0-agent-card-is-being-trusted-during-task-negotiation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-stale-a2a-v1-0-agent-card-is-being-trusted-during-task-negotiation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-a-stale-a2a-v1-0-agent-card-is-being-trusted-during-task-negotiation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1810,
    "python_slice_tokens": 340,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **card freshness as a transport concern** and **card freshness as a negotiation invariant**. Most implementations treat the agent card as a discovery artifact: fetch once, cache with a TTL, refresh on expiry. This is correct for *routing* — deciding whether a peer exists and what it broadly does. It is unsound for *neg...",
    "what_was_observed": "Across a set of A2A v1.0 inter-agent integrations, the following structural signals co-occurred in incidents where a stale card was trusted: 1. **Capability drift without identity change.** The remote server's `capabilities` object (notably `streaming`, `pushNotifications`, `stateTransitionHistory`) changed between card fetches, but the card's `name`, `description`, and `url` were byte-identical. Clients using identi...",
    "condition_of_validity": "A cached agent card is a valid basis for negotiation **only if all of the following hold**: - The card carries a monotonic, server-controlled version marker (`cardVersion` or equivalent) and the server rejects task creation when the client's asserted card version is below the server's minimum accepted version. - The client revalidates the card (or a negotiat...",
    "decision_boundary": "The operationally useful boundary is: **revalidate on negotiation, not on schedule.** - If the client's intended task depends only on fields that the server guarantees are immutable for the card's lifetime (identity, `url`, top-level `description`), a TTL cache is sound. - If the intended task depends on `capabilities`, `skills`, `defaultInputModes`, `defaul...",
    "operational_effect": "Trusting a stale card during negotiation produces failures that are expensive precisely because they are *late*: resources are committed, user-visible state is emitted, and the error arrives at a lifecycle transition where rollback is costly and attribution is ambiguous (client blames server, server blames client's cache). The correct posture is to make card..."
  },
  "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": "12ecd9a83bc8ba118b81b901d43340f742da77bc694b2c883e9c5378be612bd5",
    "verified_classes": [
      "StaleAgentCardError",
      "CachedCard"
    ],
    "verified_functions": [
      "negotiation_digest",
      "negotiate_task",
      "create_task_or_fail"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "StaleAgentCardError"
    ],
    "sample_fail_closed_invariants": [
      "cannot revalidate agent card at task creation; refusing to negotiate against unverified cached surface"
    ],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "hashlib",
      "json",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
