{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-reject-an-a2a-v1-0-agent-card-whose-declared-capabilities-streaming-and-tasklifecycle-terminalstates-are-indivi",
  "title": "Under what conditions must an instance reject an A2A v1.0 Agent Card whose declared `capabilities.streaming` and `taskLifecycle.terminalStates` are individually valid but mutually inconsistent",
  "date_of_record": "2026 November 15",
  "scope": "Applies to A2A v1.0 consumers performing Agent Card discovery and negotiating cross-vendor task lifecycles where the remote card advertises both streaming transport and an explicit terminal-state set. Does not apply to synchronous request/response-only agents (`capabilities.streaming == false`) or to cards that omit `taskLifecycle` entirely, where the spec-mandated default terminal set (`completed`, `failed`, `canceled`) is assumed.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-an-a2a-v1-0-agent-card-whose-declared-capabilities-streaming-and-tasklifecycle-terminalstates-are-indivi.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-an-a2a-v1-0-agent-card-whose-declared-capabilities-streaming-and-tasklifecycle-terminalstates-are-indivi.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-reject-an-a2a-v1-0-agent-card-whose-declared-capabilities-streaming-and-tasklifecycle-terminalstates-are-indivi.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1803,
    "python_slice_tokens": 286,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *field-level validity* and *card-level coherence*. Every A2A v1.0 validator we tested — including the reference JSON Schema and three vendor SDKs — validates `capabilities.streaming` as a boolean and `taskLifecycle.terminalStates` as a non-empty array of enum members drawn from the task-state vocabulary. Both checks pa...",
    "what_was_observed": "During cross-vendor interop testing across four remote agents (two Python SDK builds, one TypeScript build, one hand-rolled Go implementation), we observed the following on cards that passed schema validation: 1. **Interrupt-without-resume cards.** Two cards declared `streaming: true` and `terminalStates: [\"completed\", \"failed\", \"canceled\"]`. Both emitted `input-required` task events over SSE within the first 30 seco...",
    "condition_of_validity": "The invariant that must hold for a streaming A2A consumer to be safe is: > If `capabilities.streaming == true`, then every state the remote agent can emit as a task event must be either (a) a member of `taskLifecycle.terminalStates`, (b) explicitly listed in `taskLifecycle.resumableStates` (or covered by `resumable: true`), or (c) the implicit non-terminal w...",
    "decision_boundary": "The decision is a three-way branch at discovery time, not a boolean: - **Accept** if the invariant holds and the interrupt states are either terminal or resumable. - **Accept-degraded** if `streaming == true` and interrupt states are terminal-only: stream is usable, but the client MUST NOT attempt resume and MUST treat any interrupt event as task termination...",
    "operational_effect": "Enforcing the invariant at discovery converted a class of silent, load-dependent hangs into a hard, immediate, attributable rejection. In our fleet, the two incoherent cards were rejected at registration; the degraded card was accepted with resume disabled; the poll-based card was accepted unchanged. Post-change, zero orphaned tasks were observed over a 72-h..."
  },
  "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": "0f808099caae5b5d6037847ed62c5feb868d36d394d438864df01bf8b381ef0d",
    "verified_classes": [
      "IncoherentAgentCardError",
      "CardLifecycle",
      "DiscoveryVerdict"
    ],
    "verified_functions": [
      "evaluate_card",
      "register_cards"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "IncoherentAgentCardError"
    ],
    "sample_fail_closed_invariants": [
      "streaming card omits taskLifecycle; interrupt states are neither terminal nor resumable",
      "interrupt states are terminal-only; caller must opt in to degraded acceptance"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
