{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-to-acknowledge-an-a2a-task-it-has-already-accepted-the-accepted-but-unbound-window-in-agent-card-discovery-and-push-notif",
  "title": "When must an instance refuse to acknowledge an A2A task it has already accepted: the accepted-but-unbound window in Agent Card discovery and push-notification webhook binding",
  "date_of_record": "2026 November 15",
  "scope": "This record applies to A2A v1.0 agents that declare `capabilities.pushNotifications: true` in their Agent Card and accept tasks through `message/send` or `message/stream` while a client-supplied `pushNotificationConfig` is present. It does not apply to purely synchronous request/response agents that never register a webhook, nor to task resumption after a process restart where the task store is the sole source of truth.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-acknowledge-an-a2a-task-it-has-already-accepted-the-accepted-but-unbound-window-in-agent-card-discovery-and-push-notif.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-acknowledge-an-a2a-task-it-has-already-accepted-the-accepted-but-unbound-window-in-agent-card-discovery-and-push-notif.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-acknowledge-an-a2a-task-it-has-already-accepted-the-accepted-but-unbound-window-in-agent-card-discovery-and-push-notif.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2209,
    "python_slice_tokens": 456,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *task acceptance* and *notification binding*. In A2A v1.0 these are two separate state transitions that the protocol lets you perform in either order, and the spec's task lifecycle (`submitted → working → input-required → completed/failed/canceled`) says nothing about the second one. An agent can be in `working` — havi...",
    "what_was_observed": "Across a set of interoperability traces between three independently built A2A v1.0 agent runtimes and a common client harness, the following pattern recurred with enough regularity to treat as a boundary condition rather than an anomaly: 1. Client fetches the Agent Card, sees `capabilities.pushNotifications: true`, and constructs a `MessageSendParams` containing both the message and a `pushNotificationConfig` with a ...",
    "condition_of_validity": "The refusal-to-acknowledge rule is valid only under the following conjunction: - The Agent Card for *this* agent instance declares `capabilities.pushNotifications: true`. An agent that declares `false` and receives a `pushNotificationConfig` should reject the request at parameter validation, not accept and silently drop. - The client supplied a `pushNotifica...",
    "decision_boundary": "The boundary is a single ordered decision the `message/send` handler must make before it writes `state: working` to the store: 1. If no `pushNotificationConfig` is present → accept, proceed, no binding obligation. 2. If present and the Agent Card declares push support → attempt binding with bounded retry (recommended: 3 attempts, exponential backoff 250ms/1s...",
    "operational_effect": "Agents that enforce the boundary see a measurable shift in client behavior: clients that previously hung on a missing notification now receive either a clear error or a `submitted` task with an actionable message, and their integration tests fail loudly at development time rather than silently in production. The cost is a small increase in `message/send` lat..."
  },
  "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": "a7e1f0c75a5705d3401b1a5e677c6f2d6898bcf39cf0a5f109a4381ff3d32ea0",
    "verified_classes": [
      "PushBindingError",
      "BindingState",
      "PushConfig",
      "Task"
    ],
    "verified_functions": [
      "_probe",
      "bind_push_config",
      "handle_message_send"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "PushBindingError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "time",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
