{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-treat-mcp-streamable-http-session-resumption-as-a-distinct-authorization-event-rather-than-a-transport-retry",
  "title": "In what scenarios must an instance treat MCP Streamable HTTP session resumption as a distinct authorization event rather than a transport retry",
  "date_of_record": "2026 November 16",
  "scope": "Applies to MCP servers exposing the Streamable HTTP transport (POST for client→server messages, GET for the server→client SSE stream) with `Mcp-Session-Id`-based session resumption and OAuth 2.1 resource-server token validation. Does not apply to stdio transports, nor to stateless Streamable HTTP deployments that explicitly omit session identifiers and disallow `Last-Event-ID` resumption.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-mcp-streamable-http-session-resumption-as-a-distinct-authorization-event-rather-than-a-transport-retry.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-mcp-streamable-http-session-resumption-as-a-distinct-authorization-event-rather-than-a-transport-retry.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-treat-mcp-streamable-http-session-resumption-as-a-distinct-authorization-event-rather-than-a-transport-retry.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1729,
    "python_slice_tokens": 387,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The transport spec treats session resumption as a *delivery* concern: a client reconnects its GET SSE channel with `Last-Event-ID`, and the server replays buffered events after that cursor. The authorization spec treats the bearer token as a *capability* bound to a resource and a subject. The non-obvious boundary is that these two layers intersect at a point...",
    "what_was_observed": "A server issued `Mcp-Session-Id: S` on the initial POST under access token `T1` (scope `tools:read`, subject `alice`, `exp` in 300s). The client's GET SSE stream dropped at the network layer; the client reconnected with `Last-Event-ID: 41` and the same `Mcp-Session-Id: S`, but its token-refresh logic had already rotated to `T2` — a token for subject `bob` (a shared service workstation re-authenticated as a different ...",
    "condition_of_validity": "The replay-authorization invariant is only meaningful — and the failure only reachable — when all of the following hold: 1. The server maintains a per-session event buffer keyed by `Mcp-Session-Id` and honors `Last-Event-ID`. 2. Session identity and token identity are established independently: the session is created under token `T_create`, but subsequent GE...",
    "decision_boundary": "On a resumption GET carrying `Last-Event-ID` and `Mcp-Session-Id`, the server must choose between three policies, and must choose *explicitly*: - **Pin:** bind the session to the creating token's `sub` and scope set; reject resumption if the current token's `sub` differs or if any buffered event required a scope absent from the current token. Reject with `40...",
    "operational_effect": "The practical consequence is that **session resumption must be modeled as an authorization event, not a transport retry**, and the `Mcp-Session-Id` must be treated as a handle that *references* an authorization context rather than one that *substitutes* for it. Concretely: store `sub` and the granted scope set alongside the session at creation; on every GET ..."
  },
  "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": "fe8597a9f2659a0ac3e3f80cb0413b7a8212dee64d19b086cb7b4531883ac5bf",
    "verified_classes": [
      "SessionResumptionAuthError",
      "TokenContext",
      "Session"
    ],
    "verified_functions": [
      "validate_resource_token",
      "resume_session"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "SessionResumptionAuthError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
