{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-silent-task-state-divergence-during-a2a-v1-0-agent-card-re-resolution-and-cross-vendor-artifact-handoff",
  "title": "Which invariants prevent silent task-state divergence during A2A v1.0 Agent Card re-resolution and cross-vendor artifact handoff",
  "date_of_record": "2026 November 15",
  "scope": "Applies to A2A v1.0 clients that cache Agent Cards and drive tasks through the `submitted → working → input-required → completed/failed/canceled` lifecycle while exchanging artifacts with a peer whose implementation vendor differs from the caller's. Does not apply to single-vendor deployments where client and server share the same SDK, nor to stateless request/response skills that never emit artifacts.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-task-state-divergence-during-a2a-v1-0-agent-card-re-resolution-and-cross-vendor-artifact-handoff.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-task-state-divergence-during-a2a-v1-0-agent-card-re-resolution-and-cross-vendor-artifact-handoff.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-task-state-divergence-during-a2a-v1-0-agent-card-re-resolution-and-cross-vendor-artifact-handoff.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1472,
    "python_slice_tokens": 267,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"the Agent Card changed\" and it is not \"the task failed.\" It is the case where the *cached Agent Card's declared capability set* and the *live task's actual state transitions* disagree, and neither side raises an error. A2A v1.0 separates discovery (Agent Card fetch, capability negotiation, security scheme advertisement) from executio...",
    "what_was_observed": "A caller resolved an Agent Card advertising `capabilities.streaming: true` and `skills[].outputModes: [\"text/plain\", \"application/json\"]`. It created a task, received `submitted`, then `working`. The peer (a different vendor's runtime) rotated its Agent Card to a version with `streaming: false` and `outputModes: [\"application/json\"]` only, while the in-flight task continued on the old code path. The client, following...",
    "condition_of_validity": "The invariant holds only when all of the following are true: - The task was created via a `message/send` that returned a `task.id` bound to a specific Agent Card `version` (the card in effect at admission). If the server does not echo or bind a card version to the task, the invariant is unenforceable and you must treat every card refresh as a potential state...",
    "decision_boundary": "The operational rule: **pin the capability snapshot at task admission; re-resolve the card only to decide whether to create *new* tasks, never to re-validate an existing one.** Concretely: - On `message/send`, capture `(card.version, card.capabilities, card.skills[].outputModes)` into the task's local record. All subsequent artifact `kind`/`mimeType` checks ...",
    "operational_effect": "With pinning, the observed divergence rate in a two-vendor exchange dropped to zero across card rotations, at the cost of a bounded staleness window (in-flight tasks may use a capability the peer has since withdrawn — the peer must still honor it, which A2A v1.0 requires for admitted tasks, though this is under-specified and vendor-dependent). The residual r..."
  },
  "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": "4335f42f404b855a6cabd320638920eff3b9a836e4710f30670b639b98aead2c",
    "verified_classes": [
      "TaskStateDivergenceError",
      "PinnedTask"
    ],
    "verified_functions": [
      "validate_artifact",
      "reconcile_terminal",
      "on_card_refresh"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "TaskStateDivergenceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
