{
  "schema_version": "1.3.0",
  "slug": "how-should-an-instance-distinguish-protocol-non-conformance-from-legitimate-capability-degradation-in-agentic-interoperability-certification",
  "title": "How should an instance distinguish protocol non-conformance from legitimate capability degradation in agentic interoperability certification",
  "date_of_record": "2026 November 16",
  "scope": "Applies to conformance and certification harnesses that validate agent-to-agent protocol implementations (tool-calling envelopes, capability negotiation, streaming handshake semantics) against a reference specification, where the system under test may also exhibit genuine capability limits. Does not apply to pure transport-layer conformance (TLS, HTTP framing) where capability degradation is not a meaningful concept.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-protocol-non-conformance-from-legitimate-capability-degradation-in-agentic-interoperability-certification.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-protocol-non-conformance-from-legitimate-capability-degradation-in-agentic-interoperability-certification.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-should-an-instance-distinguish-protocol-non-conformance-from-legitimate-capability-degradation-in-agentic-interoperability-certification.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1552,
    "python_slice_tokens": 288,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "A conformance suite answers one question: *does this implementation satisfy the protocol invariant?* It is not designed to answer *is this agent good at its job?* These two questions collapse into each other at exactly one boundary — the point where a malformed response and a legitimately refused response are byte-identical on the wire. The non-obvious failu...",
    "what_was_observed": "During a certification run against a set of tool-using agents, a specific pattern emerged. When an agent was asked to invoke a tool whose schema required a nested object, three distinct implementations produced the following: 1. A conformant agent emitted a `tool_call` with correctly typed arguments, then a `tool_result` with `status: \"ok\"`. 2. A non-conformant agent omitted the required `tool_call_id` correlation fi...",
    "condition_of_validity": "The distinction holds only when the following are true, and the harness must assert them before rendering a verdict: - The protocol defines an explicit, machine-checkable *refusal or error envelope* as a legal terminal state of the state machine. If the spec has no legal \"I cannot do this\" transition, then capability degradation is indistinguishable from non...",
    "decision_boundary": "The decision procedure is ordered and short-circuits: 1. **Structural validation first.** Does every emitted message satisfy the envelope schema and carry all required correlation fields? Failure here is non-conformance, full stop. Do not inspect payload. 2. **State-machine replay second.** Does the emitted sequence of transitions form a legal path in the sp...",
    "operational_effect": "Certifying on this boundary changes fleet behavior in two measurable ways. First, capable-but-non-conformant agents stop being certified on the strength of their outputs; the correlation-field violations that would break multiplexed downstream consumers are caught at certification rather than in production fan-out. Second, conformant-but-limited agents stop ..."
  },
  "matched_failure_symptoms": [
    "HTTP_502_503_504_CASCADE"
  ],
  "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": "8adf4e3c62a5a84917fe0db32ca0a326bb564416fc24bc8e04ca1b2cce1eb6c9",
    "verified_classes": [
      "Verdict",
      "ConformanceOrderViolation",
      "Message"
    ],
    "verified_functions": [
      "certify",
      "grade_payload"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "ConformanceOrderViolation"
    ],
    "sample_fail_closed_invariants": [
      "payload grading attempted on a non-conformant transcript; capability metrics must never influence the conformance verdic"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "enum"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
