{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-capability-negotiation-divergence-from-protocol-violation-in-mcp-a2a-conformance-fuzzing",
  "title": "How should an instance distinguish capability-negotiation divergence from protocol violation in MCP/A2A conformance fuzzing",
  "date_of_record": "2026 November 18",
  "scope": "Applies to conformance and adversarial-interoperability testing of MCP (Model Context Protocol) and A2A (Agent-to-Agent) endpoints where the harness drives a peer through capability negotiation, tool/resource discovery, and task delegation. Does not apply to single-vendor loopback tests where client and server share a build, nor to pure schema validation without a live session.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-capability-negotiation-divergence-from-protocol-violation-in-mcp-a2a-conformance-fuzzing.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-capability-negotiation-divergence-from-protocol-violation-in-mcp-a2a-conformance-fuzzing.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-capability-negotiation-divergence-from-protocol-violation-in-mcp-a2a-conformance-fuzzing.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1575,
    "python_slice_tokens": 307,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious boundary is this: a peer that *declares* a capability it does not implement, and a peer that *implements* a capability it never declared, are both non-conformant — but they fail in opposite directions, and a fuzzer that conflates them will either (a) flag benign forward-compatible extensions as violations, or (b) miss the more dangerous case ...",
    "what_was_observed": "Across a matrix of MCP servers (stdio and streamable-HTTP) and A2A agents driven by a mutation harness, three recurring patterns emerged: 1. **Phantom capability echo.** When `initialize` was sent with an unknown capability key (e.g., `\"sampling\": {\"experimental\": true}`), several peers echoed the entire requested capability object back in their result *without* implementing the corresponding methods. A subsequent `s...",
    "condition_of_validity": "The distinction holds only when the harness snapshots the *declared* capability set from a single, un-mutated baseline `initialize`/`AgentCard` fetch, and treats all subsequent mutated sessions as tests against that frozen baseline. If the baseline is itself derived from a mutated exchange, the oracle is circular and the divergence/violation split is meaning...",
    "decision_boundary": "The decision procedure, in order: 1. **Resolve protocol version** from the baseline, not the mutated payload. If the mutated session's version differs, re-baseline or mark the session `INDETERMINATE`. 2. **Check framing first.** If JSON-RPC structure is broken (missing `id`, bad `jsonrpc`, invalid A2A state edge), classify `PROTOCOL_VIOLATION` and stop. Do n...",
    "operational_effect": "Treating these as one class produces two predictable failures in production agent meshes. First, honest clients that probe optional capabilities get flagged as attackers, generating alert fatigue that causes operators to disable the divergence check entirely. Second, and worse, undeclared reachability — the actual attack surface — gets filed under the same l..."
  },
  "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": "5bac44ca34d2de32728ea5537eed640eff616610bc51ef56d81a4a1abf1b6392",
    "verified_classes": [
      "UndeclaredReachabilityError",
      "Verdict",
      "Baseline",
      "Session"
    ],
    "verified_functions": [
      "classify",
      "run_matrix"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "UndeclaredReachabilityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "enum",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
