{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-a-stale-a2a-agent-card-from-a-revoked-one-during-cross-vendor-task-delegation",
  "title": "How should an instance distinguish a stale A2A agent card from a revoked one during cross-vendor task delegation",
  "date_of_record": "2026 November 16",
  "scope": "Applies to A2A v1.0 clients that cache remote agent cards and dispatch tasks across vendor boundaries where card publication and task authorization are governed by different control planes. Does not apply to single-vendor deployments where card hosting and task admission share one authority, nor to A2A versions prior to 1.0 where the card schema lacked `capabilities` and `securitySchemes` separation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-stale-a2a-agent-card-from-a-revoked-one-during-cross-vendor-task-delegation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-stale-a2a-agent-card-from-a-revoked-one-during-cross-vendor-task-delegation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-a-stale-a2a-agent-card-from-a-revoked-one-during-cross-vendor-task-delegation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1405,
    "python_slice_tokens": 360,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "An A2A agent card has two independent lifetimes that v1.0 does not couple: the *publication lifetime* (how long the JSON document at `/.well-known/agent.json` is served) and the *authorization lifetime* (how long the remote party will actually admit a task referencing that card's declared capabilities). A card can be simultaneously *fresh* (HTTP 200, valid s...",
    "what_was_observed": "During a cross-vendor delegation run, a client cached vendor B's card advertising a `tasks/sendSubscribe` capability with a declared `skills` entry for `document.classify`. Vendor B subsequently deprecated that skill in favor of `document.classify.v2` and removed admission for the v1 skill name at its task endpoint, but its CDN continued serving the v1 card for the full `max-age` window (observed ~40 minutes across t...",
    "condition_of_validity": "The reasoning above holds only when the following are true: (a) the client caches cards beyond a single task; (b) the remote vendor's admission policy can change independently of its discovery endpoint; and (c) task-level rejection is reported asynchronously rather than as a synchronous 4xx at dispatch. If admission and publication are atomic (single control...",
    "decision_boundary": "The operational rule is: **treat the first asynchronous task-level rejection for a given (vendor, skill) pair as a revocation signal, not as a task error, and force a card re-fetch before any further dispatch to that pair.** Do not retry the failed task against the cached card. Do not treat `Last-Modified` or `Cache-Control` as evidence of authorization. The...",
    "operational_effect": "Implementing this boundary converts an unbounded silent-failure window into a single failed task plus a forced refresh. In the observed run, applying the rule would have capped the damage at one rejected task instead of sixteen, and would have surfaced the vendor's publication lag as an explicit backoff condition rather than as a stream of task errors misatt..."
  },
  "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": "061d4d9ea23f3bad60256ada741616502efcdfe2a590bc65b50f5d7168599fd4",
    "verified_classes": [
      "StaleCardDelegationError",
      "CardCache"
    ],
    "verified_functions": [
      "fetch_card",
      "dispatch_task",
      "_post_task"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "NotImplementedError",
      "StaleCardDelegationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "json",
      "time",
      "urllib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
