{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-to-treat-a-terminal-a2a-task-state-as-authoritative-for-artifact-streaming-negotiation",
  "title": "Under what conditions must an instance refuse to treat a terminal A2A Task state as authoritative for artifact streaming negotiation",
  "date_of_record": "2026 November 17",
  "scope": "This record applies to A2A v1.0 clients and orchestrators that discover remote agents via Agent Cards and negotiate artifact streaming against tasks whose lifecycle state has reached a terminal value (`completed`, `failed`, `canceled`). It does not apply to the initial task submission handshake, to non-streaming unary `tasks/send` flows that never open a stream, or to agents that advertise no streaming capability in their Agent Card.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-treat-a-terminal-a2a-task-state-as-authoritative-for-artifact-streaming-negotiation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-treat-a-terminal-a2a-task-state-as-authoritative-for-artifact-streaming-negotiation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-treat-a-terminal-a2a-task-state-as-authoritative-for-artifact-streaming-negotiation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1738,
    "python_slice_tokens": 387,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between a *terminal task state* and a *terminal artifact stream*. In A2A v1.0 these are two separate state machines that happen to share a task identifier. The task lifecycle state machine transitions `submitted → working → {completed | failed | canceled}` (plus `input-required` as a non-terminal pause). The artifact streaming...",
    "what_was_observed": "During a multi-agent orchestration run against a v1.0 agent that advertised `capabilities.streaming: true` and `capabilities.pushNotifications: false`, the following sequence was captured on a task that produced three artifacts: 1. Client opened `tasks/sendSubscribe`. 2. Server emitted `TaskStatusUpdateEvent { state: \"working\" }`. 3. Server emitted `TaskArtifactUpdateEvent { artifact: A1, append: false, lastChunk: fa...",
    "condition_of_validity": "The rule \"a terminal status event authorizes stream teardown\" is valid only when **all** of the following hold: - The Agent Card for the discovered agent declares `capabilities.streaming: true` **and** the negotiated `TaskPushNotificationConfig` (if any) confirms the server will not deliver artifacts out-of-band. - The terminal status event and the artifact ...",
    "decision_boundary": "The boundary is drawn at the point where the client must choose between two incompatible actions on observing a terminal `TaskStatusUpdateEvent`: - **If** the stream is live (original subscription) **and** the terminal status arrived with the stream still open, the client must *continue consuming* until the artifact stream's own final marker, then close. Ter...",
    "operational_effect": "Instances that collapse the two state machines into one exhibit two failure signatures: (a) silent artifact truncation on live streams where status precedes artifact persistence, and (b) false-success on resubscribe replays where retention expired, reported as a completed task with missing artifacts. Both pass health checks, because neither produces a transp..."
  },
  "matched_failure_symptoms": [
    "OOM_KILL_OR_MEMORY_EXHAUSTION"
  ],
  "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": "5e416e1edbd65be8a1b73fb3e07b1fc62a213a082d126aa99b6f9b91a7338e1b",
    "verified_classes": [
      "ArtifactStreamNegotiationError",
      "TaskState",
      "StreamContext"
    ],
    "verified_functions": [
      "authorize_stream_teardown"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ArtifactStreamNegotiationError"
    ],
    "sample_fail_closed_invariants": [
      "Artifact events received from agent whose Agent Card declared capabilities.streaming=false; reconcile via unary tasks/ge",
      "Terminal status observed on live stream before artifact final marker; refusing teardown to avoid silent tail loss.",
      "Resubscribe replay returned terminal status with zero artifact events and no replay-complete marker; artifacts are UNKNO",
      "Replay contained artifact events but no final marker; replay is truncated."
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
