{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-reject-a-resumed-mcp-streamable-http-session-rather-than-silently-downgrade-to-sse-fallback",
  "title": "Where must an instance reject a resumed MCP Streamable-HTTP session rather than silently downgrade to SSE fallback",
  "date_of_record": "2026 November 15",
  "scope": "Applies to MCP servers implementing the Streamable HTTP transport (single POST endpoint returning either `application/json` or `text/event-stream`, with `Mcp-Session-Id` and `Last-Event-ID` resumption) that also advertise an SSE fallback path. Does not apply to pure legacy HTTP+SSE two-endpoint servers, nor to stdio transports, where session identity is process-scoped and resumption is not negotiated.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-reject-a-resumed-mcp-streamable-http-session-rather-than-silently-downgrade-to-sse-fallback.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-reject-a-resumed-mcp-streamable-http-session-rather-than-silently-downgrade-to-sse-fallback.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-reject-a-resumed-mcp-streamable-http-session-rather-than-silently-downgrade-to-sse-fallback.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1713,
    "python_slice_tokens": 321,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure mode is not \"resumption failed\" and it is not \"fallback engaged.\" It is the *conflation* of the two. A resumed session carries an implicit replay contract: the client asserts `Last-Event-ID: N` meaning \"I have consumed every event up to N on this session's stream; resume after N.\" An SSE fallback carries a *different* contract: \"this client canno...",
    "what_was_observed": "A Streamable-HTTP MCP server was deployed behind a load balancer with per-node in-memory event buffers keyed by `Mcp-Session-Id`. Sessions were created on node A. A client POSTed a `tools/call`, received a 200 `text/event-stream` with events `id: 41`, `id: 42`, then the TCP connection was severed mid-stream (LB idle timeout at 60s while the tool ran long). The client reconnected per spec: POST to the same endpoint wi...",
    "condition_of_validity": "The silent-downgrade behavior is only defensible when **all** of the following hold: 1. The inbound request carries **no** `Last-Event-ID` header (the client is not asserting a replay position), **or** the server can prove the session was never established on any node (a true cold start, e.g. session TTL expired cluster-wide and the client is re-initializing...",
    "decision_boundary": "The decision is a function of two request properties and one server property, evaluated in this order: The last two rows are the boundary. The common implementation error is to treat \"unknown session on this node\" as equivalent to \"new client,\" collapsing rows 2 and 4. They are not the same: row 2's client has no replay obligation; row 4's client does, and h...",
    "operational_effect": "When the boundary is enforced, the long-tool scenario degrades correctly: the client receives a resumption-impossible error, and the agent framework can choose to (a) re-initialize a new session and re-issue the call under an idempotency key, or (b) surface the failure to the orchestrator. Duplicate side effects become a deliberate, observable decision rathe..."
  },
  "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": "e75c2a27071ec7c4876b712769654c9acb5c87f53d938d5bfd9730c4d0f25fa8",
    "verified_classes": [
      "ResumptionImpossibleError",
      "InboundRequest",
      "SessionState"
    ],
    "verified_functions": [
      "negotiate_transport"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "ResumptionImpossibleError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
