{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-a-delegated-task-mid-lifecycle-the-a2a-v1-0-card-staleness-invariant-at-handshake-boundaries",
  "title": "When must an instance refuse a delegated task mid-lifecycle: The A2A v1.0 card-staleness invariant at handshake boundaries",
  "date_of_record": "2026 November 15",
  "scope": "Applies to A2A v1.0 (and v0.3-compatible) agents that accept cross-vendor delegated tasks after resolving a remote Agent Card, and to orchestrators that cache cards across a task lifecycle. Does not apply to single-vendor intra-process delegation where the card and the executor share a trust domain, nor to stateless request/response calls that never enter `task` state.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-delegated-task-mid-lifecycle-the-a2a-v1-0-card-staleness-invariant-at-handshake-boundaries.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-delegated-task-mid-lifecycle-the-a2a-v1-0-card-staleness-invariant-at-handshake-boundaries.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-a-delegated-task-mid-lifecycle-the-a2a-v1-0-card-staleness-invariant-at-handshake-boundaries.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1759,
    "python_slice_tokens": 367,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *card resolution* (a discovery-time fact about what an agent claims it can do) and *task negotiation* (a lifecycle-time fact about what an agent will actually do for *this* task under *this* delegation chain). A2A v1.0 lets these two facts drift apart silently. The Agent Card is a signed, cacheable advertisement; the `...",
    "what_was_observed": "During a multi-vendor orchestration pilot, an orchestrator resolved Agent Cards at t=0, cached them for a 30-minute TTL, and dispatched tasks to a planner agent. The planner's card advertised `capabilities.streaming: true` and a skill set including `code.execute.sandboxed`. At t=+19 minutes the vendor rotated the planner's card: the sandboxed-execution skill was withdrawn (the sandbox pool was drained for maintenance...",
    "condition_of_validity": "The refusal-at-handshake rule is valid only when all of the following hold: 1. The delegation crosses a vendor or trust boundary (the caller and callee do not share a card-signing key or a configuration authority). 2. The task's required capability set is drawn from the card's `skills` or `capabilities` fields, not from out-of-band agreement. 3. The card is ...",
    "decision_boundary": "The boundary is a single predicate evaluated at the `submitted → working` transition, on the **callee** side, and again at the `working → completed` transition on the **caller** side: - **Callee predicate:** *Does my current, live capability set (not the card I last published) cover every skill and capability the task requires?* If no, the callee must transi...",
    "operational_effect": "Implementing the refusal-at-handshake rule converts a silent, retry-amplifying failure (11 minutes/task, 40 tasks) into an immediate, structured rejection at the `submitted` boundary (sub-second). It also makes the audit trail honest: a `failed` task with a named missing capability is diagnosable; a `working` task that never terminates is not. The cost is a ..."
  },
  "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": "6ba03ec2a054f14767b384be9e29b38bb675635eb57f02758f5830cb0cc201ab",
    "verified_classes": [
      "CardStalenessError",
      "AgentCard",
      "DelegatedTask"
    ],
    "verified_functions": [
      "accept_delegation",
      "caller_check_before_dispatch",
      "digest"
    ],
    "verified_functions_count": 3,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "CardStalenessError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
