{
  "schema_version": "1.3.0",
  "slug": "which-invariants-prevent-silent-task-orphaning-when-a2a-v1-0-agent-card-discovery-races-against-cross-framework-push-notification-binding",
  "title": "Which invariants prevent silent task orphaning when A2A v1.0 Agent Card discovery races against cross-framework push notification binding",
  "date_of_record": "2026 November 15",
  "scope": "Applies to A2A v1.0 agents that advertise a push-notification endpoint in their Agent Card and accept tasks from remote callers whose lifecycle may outlive the caller's connection. Does not apply to purely synchronous request/response agents, nor to agents whose Agent Card is served from an immutable, versioned registry with no in-band mutation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-task-orphaning-when-a2a-v1-0-agent-card-discovery-races-against-cross-framework-push-notification-binding.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-task-orphaning-when-a2a-v1-0-agent-card-discovery-races-against-cross-framework-push-notification-binding.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/which-invariants-prevent-silent-task-orphaning-when-a2a-v1-0-agent-card-discovery-races-against-cross-framework-push-notification-binding.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1543,
    "python_slice_tokens": 210,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *card-declared capability* and *card-declared binding*. An Agent Card is a discovery artifact: it tells a remote client what the agent can do and where. A push notification binding is a runtime contract: it tells the agent where to deliver state transitions for a specific task. These two are conflated constantly becaus...",
    "what_was_observed": "In a cross-framework deployment (caller on framework A, agent on framework B, both A2A v1.0 compliant), the following sequence reproduced intermittently under load: 1. Caller fetches Agent Card at `/.well-known/agent-card.json`. Card declares `pushNotifications: { supported: true, endpoint: \"https://agent-b.example/push/v1\" }` and a `capabilities.streaming` flag. 2. Caller submits a task via `tasks/send` with a `push...",
    "condition_of_validity": "The orphaning invariant holds — i.e., tasks can be silently orphaned — precisely when all of the following are true: - The Agent Card is mutable in-band (re-fetched, hot-reloaded, or served with a changing `version`) during the lifetime of an in-flight task. - The push binding is *card-derived* rather than *task-derived*: the caller's webhook validation depe...",
    "decision_boundary": "The decision boundary is whether the push binding is bound to the **task** or to the **card generation**. Two rules resolve it: - **Bind notifications to a per-task binding token, not to the card's endpoint field.** The card advertises *that* push is supported and *where the negotiation endpoint is*; the negotiation endpoint issues a task-scoped token that r...",
    "operational_effect": "Implementations that cross the boundary exhibit a characteristic signature: task completion rate near 100%, delivery success rate that degrades in step with deployment frequency, and a growing population of tasks in terminal state whose delivery is marked failed but which no reconciler ever revisits. The caller's task store shows tasks stuck in `working` ind..."
  },
  "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": "7cdd4ff3fe510ae91372b77779e78473d4814b88d80c49e3c1e4c5aa0a6898d5",
    "verified_classes": [
      "OrphanedTaskError"
    ],
    "verified_functions": [
      "resolve_push_binding",
      "deliver_terminal_state"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "OrphanedTaskError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
