{
  "schema_version": "1.3.0",
  "slug": "what-structural-signals-indicate-capability-negotiation-has-silently-degraded-into-optimistic-delegation-in-a2a-v1-0",
  "title": "What structural signals indicate capability negotiation has silently degraded into optimistic delegation in A2A v1.0",
  "date_of_record": "2026 November 17",
  "scope": "Applies to A2A v1.0 task delegation between a delegating agent (client) and a receiving agent (server) where capability negotiation has completed via Agent Card exchange and the delegator has begun issuing `tasks/send` or `tasks/sendSubscribe` calls. Does not apply to single-agent tool invocation, nor to A2A versions prior to v1.0 where `skills` were optional and untyped.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-capability-negotiation-has-silently-degraded-into-optimistic-delegation-in-a2a-v1-0.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-capability-negotiation-has-silently-degraded-into-optimistic-delegation-in-a2a-v1-0.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-structural-signals-indicate-capability-negotiation-has-silently-degraded-into-optimistic-delegation-in-a2a-v1-0.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1379,
    "python_slice_tokens": 216,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A2A v1.0 separates two things that are easy to conflate: **declared capability** (what an Agent Card advertises in `capabilities` and `skills`) and **negotiated capability** (what the delegator has actually confirmed the receiver will honor for a given task). The protocol only *requires* the receiver to reject a task it cannot perform; it does not require th...",
    "what_was_observed": "Across a delegation mesh of three orchestrators and eleven worker agents, the following pattern recurred. The delegator fetches the Agent Card once at startup, caches it, and validates only that the card is well-formed and that `capabilities.streaming` matches its intended call style. It then dispatches tasks with a free-text `message` and no `skillId` binding. Workers implemented per the reference server accept any ...",
    "condition_of_validity": "The distinction holds — and the failure is real rather than a benign default — only when all of the following are true: 1. The receiver's Agent Card declares `skills` with distinct `id` values and non-overlapping `inputModes`/`outputModes`. 2. The receiver has a fallback path that accepts schema-valid messages without a matched skill (the common reference im...",
    "decision_boundary": "Do not treat \"Agent Card resolved and task accepted\" as evidence of capability agreement. Treat it as evidence of *transport* agreement only. The decision boundary is this: **a task is safely delegated only if the delegator can name the specific `skills[].id` that will service it, and that id appears in the receiver's card at dispatch time (not cache time).*...",
    "operational_effect": "Enforcing skill-id binding at dispatch and validating artifact `mediaType` against the negotiated `outputModes` eliminated the silent-completion class entirely in the observed mesh: the 9% misreported tasks dropped to 0%, and the residual failures surfaced as explicit `rejected` states the delegator could retry against a correctly-skilled worker. The cost wa..."
  },
  "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": "32de80b372757e4e7808e1df9419cd1b1ac585e422bf7829485cc9e43708a60c",
    "verified_classes": [
      "CapabilityNegotiationError",
      "AgentCard",
      "Task"
    ],
    "verified_functions": [
      "assert_negotiated",
      "delegate"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "CapabilityNegotiationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
