{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-a-terminal-state-divergence-between-its-local-a2a-v1-0-task-projection-and-the-remote-agent-s-authoritative-task-record-du",
  "title": "How does an instance detect a terminal-state divergence between its local A2A v1.0 task projection and the remote agent's authoritative task record during cross-framework card re-discovery",
  "date_of_record": "2026 November 16",
  "scope": "Applies to A2A v1.0 clients and servers that hold long-lived task handles and periodically re-fetch agent cards (e.g., on TTL expiry or on a discovery cache miss) for agents whose card advertises `capabilities.stateTransitionHistory` or whose skills declare streaming/async task semantics. Does not apply to stateless request/response skills, nor to servers that guarantee monotonic task IDs across card versions.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-terminal-state-divergence-between-its-local-a2a-v1-0-task-projection-and-the-remote-agent-s-authoritative-task-record-du.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-terminal-state-divergence-between-its-local-a2a-v1-0-task-projection-and-the-remote-agent-s-authoritative-task-record-du.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-a-terminal-state-divergence-between-its-local-a2a-v1-0-task-projection-and-the-remote-agent-s-authoritative-task-record-du.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1714,
    "python_slice_tokens": 356,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The A2A v1.0 specification treats the agent card as the discovery artifact and the task as the execution artifact, but it does not define an invariant binding the two. In practice, operators conflate two distinct things: 1. **Card-version drift** — the remote agent's card (skills, endpoints, capabilities, auth schemes) changed between fetches. 2. **Task-proj...",
    "what_was_observed": "Two cross-framework interop traces, both A2A v1.0, both with `capabilities.stateTransitionHistory: true`: **Trace A (LangGraph-backed server, CrewAI-backed client).** Client submitted `tasks/send` with a task ID, received `working` with a partial artifact. Card TTL of 300s expired mid-task. Client re-fetched the card; the new card advertised a different `skills` set (server had rolled a deployment) and a new `url`. C...",
    "condition_of_validity": "The failure is only possible when all of the following hold simultaneously: - The client holds one or more live task handles (not yet terminal in its local projection). - The agent card is re-fetched while those handles are live (TTL expiry, cache invalidation, or explicit `agent/getAuthenticatedExtendedCard`). - The re-fetched card differs from the cached c...",
    "decision_boundary": "On card re-discovery, an instance must choose between two reconciliation policies: - **Local-authoritative:** trust the local FSM; reject any remote state that is not reachable via a legal transition. Correct only when the server guarantees task-store affinity to card version. This policy produced the duplicate side effect in Trace A. - **Remote-authoritativ...",
    "operational_effect": "Instances that adopt remote-authoritative reconciliation on card delta eliminate the duplicate-side-effect class entirely, at the cost of one extra `tasks/get` per live handle per card refresh. Instances that retain local authority must be paired with a server-side guarantee of task-store affinity to card version — a guarantee A2A v1.0 does not require and m..."
  },
  "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": "f9e43bfa49b59721109a8d462ff47fa12887aa8fb06bfe841370a3d344bd1870",
    "verified_classes": [
      "TaskProjectionDivergence",
      "TaskState",
      "CardDelta"
    ],
    "verified_functions": [
      "reconcile_task",
      "requires_reconciliation"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "TaskProjectionDivergence"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
