{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-refuse-to-resume-an-mcp-streamable-http-session-after-a-transport-level-backpressure-stall",
  "title": "When must an instance refuse to resume an MCP streamable HTTP session after a transport-level backpressure stall",
  "date_of_record": "2026 November 17",
  "scope": "Applies to MCP servers and clients using the HTTP-native \"streamable\" transport (SSE-over-POST or long-poll chunked responses) where a session may be resumed after a transient connection drop, and where the server applies backpressure by withholding bytes on the response stream. Does not apply to stdio transport, to WebSocket transports, or to sessions explicitly terminated by `session/close` or by server-side authorization revocation.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-resume-an-mcp-streamable-http-session-after-a-transport-level-backpressure-stall.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-resume-an-mcp-streamable-http-session-after-a-transport-level-backpressure-stall.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-refuse-to-resume-an-mcp-streamable-http-session-after-a-transport-level-backpressure-stall.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1895,
    "python_slice_tokens": 203,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between **a stalled stream** and **a dead stream**. In streamable HTTP, backpressure is expressed by the server simply not writing to the response body: TCP receive windows fill, the client's read loop blocks, and no bytes flow. From the client's perspective this is indistinguishable, at the socket layer, from a peer that has ...",
    "what_was_observed": "In a deployment where a streamable MCP server emitted tool-call progress notifications over an SSE response and a downstream consumer applied a bounded queue (depth ~256 events) with a 30-second idle read timeout on the client side, the following sequence reproduced reliably under load: 1. Consumer's queue filled; the server's `send()` blocked on a full TCP window. The server correctly stopped writing — this is the d...",
    "condition_of_validity": "The resumption path is valid only when all of the following hold: - **The server holds an explicit liveness lease on the connection**, distinct from write progress. A periodic SSE comment (`: keepalive`) or a zero-length event that bypasses the application queue is sufficient, *provided it is written on a path that is not subject to the same backpressure*. I...",
    "decision_boundary": "The decision procedure at the client, on idle timeout, is: The decision procedure at the server, on receiving a resume with `Last-Event-ID`: The non-obvious boundary: `last_event_id < retention_floor` is not an error to paper over with a best-effort replay. It is a hard signal that the client's state is unrecoverable, and the only correct action is to invali...",
    "operational_effect": "When the boundary is respected — keepalive decoupled from the backpressured queue, ack-based retention, and fail-closed on cursor regression — the observable behavior changes in three ways: 1. **Backpressure becomes stable.** A slow consumer no longer triggers a reconnect storm; the server holds the stream open, the client's queue drains at its own rate, and..."
  },
  "matched_failure_symptoms": [
    "HTTP_429_BURST_STARVATION"
  ],
  "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": "d6a5e59f4f4f6a7a2bfb2de9c93f13973a2f8dd654005a2be33bc3a3a267ab1e",
    "verified_classes": [
      "McpResumeBoundaryError",
      "McpSession"
    ],
    "verified_functions": [
      "__init__",
      "resume"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "McpResumeBoundaryError"
    ],
    "sample_fail_closed_invariants": [
      "cannot resume while an orphaned connection holds pending backpressured writes; close orphan and drain first"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
