{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-terminal-state-divergence-in-a2a-v1-0-task-lifecycle-negotiation-across-vendor-boundaries",
  "title": "What structural signals indicate terminal-state divergence in A2A v1.0 task lifecycle negotiation across vendor boundaries",
  "date_of_record": "2026 November 18",
  "scope": "Applies to A2A v1.0 agent-to-agent delegation where the caller and callee are operated by different vendors and the callee's task transitions through `submitted → working → terminal`. Does not apply to intra-vendor delegation, to streaming-only `message/stream` sessions without a persisted task object, or to A2A versions prior to 1.0 where `TaskState` lacked the `rejected`/`auth-required` split.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-terminal-state-divergence-in-a2a-v1-0-task-lifecycle-negotiation-across-vendor-boundaries.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-terminal-state-divergence-in-a2a-v1-0-task-lifecycle-negotiation-across-vendor-boundaries.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-terminal-state-divergence-in-a2a-v1-0-task-lifecycle-negotiation-across-vendor-boundaries.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1614,
    "python_slice_tokens": 271,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not \"the remote agent returned an error.\" It is that the **agent card's declared capabilities and the task's actual lifecycle state can disagree in a way that is locally consistent on each side**. The caller sees a `working` task that never terminates; the callee has already moved the task to a terminal state it considers final but which the c...",
    "what_was_observed": "A delegation from a caller (vendor A) to a callee (vendor B) over JSON-RPC. The callee's agent card advertised: - `capabilities.streaming: false` - `capabilities.pushNotifications: true` - `defaultInputModes: [\"text/plain\"]`, `defaultOutputModes: [\"text/plain\"]` The caller, seeing `streaming: false`, issued `tasks/send` (synchronous) and waited for a terminal response. The callee, because `pushNotifications: true` wa...",
    "condition_of_validity": "The divergence is *reachable* only when all of the following hold: - The callee advertises any out-of-band completion capability (`pushNotifications: true`) while advertising `streaming: false`. These two flags are not mutually exclusive in the spec, and vendors routinely set `pushNotifications` to mean \"we can\" rather than \"we will.\" - The caller treats `st...",
    "decision_boundary": "Do not treat `capabilities.streaming: false` as a promise of synchronous terminality. Treat it as \"no incremental delivery.\" The correct inference from the card is: - If `streaming: false` AND `pushNotifications: false`, a `tasks/send` returning `working` is a protocol violation — fail fast. - If `streaming: false` AND `pushNotifications: true`, a `tasks/sen...",
    "operational_effect": "Callers that adopt the corrected inference (poll on non-terminal synchronous return) convert a 72-hour silent orphan into a bounded polling loop that terminates within the callee's retention window. The reconciliation step — on `TaskNotFound`, mark the local task `unknown-terminal` and require human or supervisor review rather than retry — prevents the infin..."
  },
  "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": "082eb96532e88a601e73109451c589b90c348ed99d8e6ae79360276c745fbdb5",
    "verified_classes": [
      "TaskState",
      "LifecycleDivergenceError"
    ],
    "verified_functions": [
      "classify_send_response",
      "reconcile_get_response"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "LifecycleDivergenceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
