{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-reject-an-a2a-v1-0-taskstatusupdateevent-whose-final-flag-disagrees-with-the-terminality-implied-by-its-state-a",
  "title": "Under what conditions must an instance reject an A2A v1.0 `TaskStatusUpdateEvent` whose `final` flag disagrees with the terminality implied by its `state`, and how the push-notification webhook binding loses that invariant",
  "date_of_record": "2026 November 14",
  "scope": "Applies to A2A v1.0 servers and clients that emit or consume `TaskStatusUpdateEvent` objects over the streaming channel (`tasks/resubscribe`, `message/stream`) and mirror those events to push-notification webhooks via `TaskPushNotificationConfig`. Does not apply to the initial `Task` object returned by `tasks/get`, nor to non-terminal `TaskArtifactUpdateEvent` frames, which have no `final` field.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-an-a2a-v1-0-taskstatusupdateevent-whose-final-flag-disagrees-with-the-terminality-implied-by-its-state-a.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-an-a2a-v1-0-taskstatusupdateevent-whose-final-flag-disagrees-with-the-terminality-implied-by-its-state-a.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-an-a2a-v1-0-taskstatusupdateevent-whose-final-flag-disagrees-with-the-terminality-implied-by-its-state-a.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1591,
    "python_slice_tokens": 233,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The A2A v1.0 `TaskStatusUpdateEvent` carries two independent signals of task termination: the `state` field (a member of `TaskState`, where `completed`, `failed`, and `canceled` are terminal) and the boolean `final` field, which instructs the receiver that no further events will arrive on this stream for this task. These are *supposed* to agree, but the spec...",
    "what_was_observed": "During a two-week observation window across three independent A2A v1.0 deployments (one reference server, two third-party), the following failure was reproduced deterministically: 1. An agent executed a long-running task and emitted `TaskStatusUpdateEvent{state: working, final: false}` on the streaming channel at 1 Hz. 2. A transient backend condition caused the agent's task worker to be rescheduled. The worker's `fi...",
    "condition_of_validity": "The rejection rule is valid — and a receiver **must** reject — only when all of the following hold: - The event is a `TaskStatusUpdateEvent` received over a channel where `final=true` terminates the delivery path for that task (streaming close, or webhook delivery where the receiver has no resubscribe primitive). - `state` is a member of `{submitted, working...",
    "decision_boundary": "The boundary is between *trusting `final` as a delivery-lifetime signal* and *trusting `state` as the task-lifetime signal*. A correct receiver treats `state` as authoritative for task lifetime and `final` as authoritative only for *transport* lifetime, and it must refuse to let a transport-lifetime signal collapse a task-lifetime state. Concretely: if `fina...",
    "operational_effect": "In the observed deployments, adding the rejection rule at the webhook receiver converted a silent, unrecoverable stale-state condition into an explicit `TaskFinalityMismatch` error that the orchestrator handled by re-enabling its polling fallback. Post-fix, all eleven simulated reschedules converged to the correct terminal state; the three previously-lost ta..."
  },
  "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": "25f5fe22368bc6b76844d3137972193438dfd662b539bb5d6562397aaebf5256",
    "verified_classes": [
      "TaskFinalityMismatch"
    ],
    "verified_functions": [
      "validate_status_event"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "TaskFinalityMismatch"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
