{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-reject-a-peer-agent-card-whose-capabilities-statetransitionhistory-is-absent-during-cross-vendor-delegation",
  "title": "In what scenarios must an instance reject a peer Agent Card whose `capabilities.stateTransitionHistory` is absent during cross-vendor delegation",
  "date_of_record": "2026 November 18",
  "scope": "Applies to A2A v1.0 clients that discover a remote Agent Card via `/.well-known/agent.json` (or the `agentCard` field of an extended `Message`) and then delegate a task whose completion requires the peer to emit a terminal `TaskState` (`completed`, `failed`, `canceled`, `rejected`). Does not apply to fire-and-forget submissions where the caller never inspects terminal state, nor to same-vendor delegation where the peer's state machine is statically known.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-peer-agent-card-whose-capabilities-statetransitionhistory-is-absent-during-cross-vendor-delegation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-peer-agent-card-whose-capabilities-statetransitionhistory-is-absent-during-cross-vendor-delegation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-reject-a-peer-agent-card-whose-capabilities-statetransitionhistory-is-absent-during-cross-vendor-delegation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1625,
    "python_slice_tokens": 351,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "An A2A Agent Card is a *declaration of interface*, not a *guarantee of behavior*. The `capabilities` object is the only structured place a peer advertises behavioral properties, and `capabilities.stateTransitionHistory` (boolean, default `false` per the v1.0 schema) is the single field that tells a delegating agent whether the remote will retain and expose t...",
    "what_was_observed": "During a cross-vendor handshake against a peer advertising `protocolVersion: \"1.0\"`, `capabilities.streaming: true`, and no `stateTransitionHistory` key, the following sequence reproduced on three independent deployments: 1. The delegator submitted `tasks/send` with a `taskId` it generated locally and recorded in its own ledger as `submitted`. 2. The peer accepted, returned a `Task` with `status.state: \"working\"`, an...",
    "condition_of_validity": "The gating rule is valid only when **all** of the following hold: - The delegation is cross-vendor, i.e., the caller has no out-of-band knowledge of the peer's persistence model. - The task is *stateful and long-lived* — its terminal state must be observed by the caller, not merely fired. - The caller's own recovery logic (reconciliation on reconnect, idempo...",
    "decision_boundary": "The boundary is drawn at **card validation time, before any `tasks/send`**, not at reconnect time. By the time the SSE stream drops, the decision is already made and the delegator has no leverage. Concretely: - If `capabilities.stateTransitionHistory` is present and `true`: delegate; the peer commits to replay semantics; the caller may rely on `tasks/resubsc...",
    "operational_effect": "Enforcing the boundary at card-validation time converts a mid-task deadlock into a pre-submission refusal, which is recoverable: the delegator can fall back to a peer that advertises history, or downgrade its own expectation to \"poll-once-after-terminal\" and proceed with an explicit `unknown`-tolerant state machine. The cost is a small number of false reject..."
  },
  "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": "0f23844bc2f517254779338524baa3753071ca9eed7a7d4cd58294b2143a90f9",
    "verified_classes": [
      "AgentCardBoundaryError",
      "AgentCardBoundaryError"
    ],
    "verified_functions": [
      "validate_peer_card_for_delegation",
      "validate_peer_card_for_delegation"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 6,
    "raised_exceptions": [
      "AgentCardBoundaryError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
