{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-treat-sse-stream-resumption-as-a-fresh-subscription-rather-than-a-continuation",
  "title": "Under what conditions must an instance treat SSE stream resumption as a fresh subscription rather than a continuation",
  "date_of_record": "2026 November 18",
  "scope": "Applies to MCP servers and clients implementing the HTTP-native transport with `text/event-stream` responses and `Last-Event-ID`-based resumability (per the streamable HTTP transport spec). Does not apply to stdio transports or to WebSocket-based MCP transports, where session continuity is bound to the socket lifetime rather than to an event ID cursor.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-sse-stream-resumption-as-a-fresh-subscription-rather-than-a-continuation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-sse-stream-resumption-as-a-fresh-subscription-rather-than-a-continuation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-treat-sse-stream-resumption-as-a-fresh-subscription-rather-than-a-continuation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2124,
    "python_slice_tokens": 423,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The streamable HTTP transport allows a client to reconnect a dropped SSE stream by presenting `Last-Event-ID` and asking the server to resume delivery after that event. The failure mode is conflating *cursor resumability* with *subscription continuity*. An event ID is an opaque, per-stream cursor. A subscription is a server-side resource that produces events...",
    "what_was_observed": "In a deployment serving tool-call progress events over SSE, a client's TCP connection was severed by a load balancer idle timeout at 60s. The client reconnected with `Last-Event-ID: 4417`. The server's event store retained 10,000 events per stream in a ring buffer, but the stream had been idle for 40s and the subscription's producing tool call had been cancelled and cleaned up 5s prior. The server nonetheless accepte...",
    "condition_of_validity": "The resume-as-continuation assumption holds only when all of the following are simultaneously true: 1. The event store retains every event from the requested `Last-Event-ID` through the current head, with no eviction in that range. This is a bounded-time property: it holds only within the replay window `W` measured in events or seconds, whichever the store e...",
    "decision_boundary": "The decision is not \"can I find this event ID?\" but \"does this event ID still denote a live subscription under the caller's current authority, and can I prove delivery continuity from it?\" Concretely, the server's resume path must evaluate, in order: - **Authority check:** does the presented `Last-Event-ID` belong to a stream whose owning session matches the...",
    "operational_effect": "Treating resumption as continuation produces three failure signatures that are easy to misdiagnose: silent hangs (client waits for a terminal event that was emitted into an orphaned stream), silent data loss (events between the last delivered ID and the replay window floor are never re-requested), and cross-scope replay (events from a prior session or tenant..."
  },
  "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": "050468b4d3245cfff120da012dc8c0721fc5a099ce9650d8fb1ecf76d3d88ce1",
    "verified_classes": [
      "ResumeContinuityError",
      "EventStore"
    ],
    "verified_functions": [
      "resume_stream",
      "__init__"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 8,
    "raised_exceptions": [
      "ResumeContinuityError"
    ],
    "sample_fail_closed_invariants": [
      "cursor_scope_mismatch",
      "cursor_scope_mismatch",
      "replay_window_exceeded",
      "cursor_ahead_of_head"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
