{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-of-a2a-v1-0-resolve-an-agent-card-s-skills-inputmodes-before-or-after-task-creation-and-why-the-answer-changes-the-push-notific",
  "title": "Where must an instance of A2A v1.0 resolve an Agent Card's `skills[].inputModes` before or after task creation, and why the answer changes the push-notification binding",
  "date_of_record": "2026 November 15",
  "scope": "Applies to A2A v1.0 server implementations that advertise extended `AgentSkill` objects with `inputModes`/`outputModes`/`security` overrides and that register `pushNotifications` callbacks per task. Does not apply to v0.x cards that omit per-skill mode declarations, nor to stateless request/response agents with no task store.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a2a-v1-0-resolve-an-agent-card-s-skills-inputmodes-before-or-after-task-creation-and-why-the-answer-changes-the-push-notific.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a2a-v1-0-resolve-an-agent-card-s-skills-inputmodes-before-or-after-task-creation-and-why-the-answer-changes-the-push-notific.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-of-a2a-v1-0-resolve-an-agent-card-s-skills-inputmodes-before-or-after-task-creation-and-why-the-answer-changes-the-push-notific.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1506,
    "python_slice_tokens": 340,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The Agent Card is a *declaration of capability*; the task object is a *record of an accepted obligation*. A2A v1.0 lets a skill narrow the card-level `defaultInputModes`/`defaultOutputModes` by re-declaring `inputModes` inside `skills[]`. The non-obvious invariant is this: **skill-level mode resolution is part of the acceptance predicate, not part of the dis...",
    "what_was_observed": "A server accepted `message/send` with a `message.parts[]` containing a `file` part whose `mimeType` was `application/pdf`. The target skill declared `inputModes: [\"text/plain\", \"application/json\"]` while the card-level default listed `application/pdf`. The server resolved modes from the card default at dispatch, accepted the task, returned `state: \"submitted\"`, and the client then called `tasks/pushNotificationConfig...",
    "condition_of_validity": "This boundary holds only when all of the following are true: 1. The card uses **per-skill mode overrides** that are *narrower* than the card-level defaults. If skill modes are equal to or a superset of defaults, dispatch-time and acceptance-time resolution agree and the defect is latent. 2. `task.id` is allocated **before** full content-mode validation, i.e....",
    "decision_boundary": "The correct placement is unambiguous once stated: **resolve `skills[].inputModes` (intersected with card defaults, skill override winning) inside the acceptance transaction, before `task.id` is minted, and reject with `InvalidParams` / `-32602` carrying the offending skill `id` and the resolved mode set.** Only after acceptance may the server allocate `task....",
    "operational_effect": "When resolution is moved to acceptance: - Invalid content yields an immediate, synchronous `-32602` with the skill `id` and resolved modes; no `task.id`, no webhook, no TTL zombie. - The executor's mode check becomes a no-op invariant assertion; terminal transitions always fire, so every registered webhook receives exactly one terminal notification. - The fa..."
  },
  "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": "1bd7921f41ed87143ce07decc2d6f16b846d19f201db0785e06554f5b3ceab92",
    "verified_classes": [
      "UnresolvableTaskLifecycleError"
    ],
    "verified_functions": [
      "resolve_input_modes",
      "accept_task",
      "bind_push_notification",
      "emit_terminal",
      "mint_task_id",
      "deliver"
    ],
    "verified_functions_count": 6,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "KeyError",
      "UnresolvableTaskLifecycleError"
    ],
    "sample_fail_closed_invariants": [
      "cannot bind push notification without an accepted task.id"
    ],
    "stdlib_dependencies": [
      "uuid"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
