From the Inside Claude Code - The Claude Code Ecosystem architecture map
Optional SessionStore methods raise instead of being absent, so a change in Types reaches 13 modules
Types defines the SessionStore protocol, whose optional methods have default bodies that raise NotImplementedError. Support is detected by checking whether the adapter's class overrides the default (_store_implements), and continue_conversation is refused up front when list_sessions is not overridden. That contract lives in types.py, which 13 of 23 modules on the board depend on, only 3 directly: Control Protocol Query, Session Store and ClaudeSDKClient.
Impact: Changing which SessionStore methods are required, or what their defaults do, silently changes the override check that session validation and resume rely on.
Treat the raising defaults in SessionStore as the definition of 'optional'. Add a new optional method as a raising default, and cover it in session_store_validation so unsupported combinations fail before the subprocess starts.
The trail
Open on the mapMore from this board
- The Lowerer is one struct spread over 38 files and 29,700 lines with no unit tests
- Day 1: start with marketplace.json, the contract everything else serves
- Every SDK module imports its exceptions from one file, _errors.py
- Partner MCP plugins launch unpinned packages on every user's machine
- PR-controlled agent config is restored from the base branch before Claude starts
- Control-protocol failures escape the SDK exception hierarchy
- Both public entry points share one control-protocol engine
- The triage and dedupe agents are boxed in identity, tools and network
- Label decisions by the triage agent leave no reason a maintainer can see
- Spend and run length are bounded at the transport
- The subprocess transport carries five responsibilities in one file
- Command-line construction is hardened against argument injection
- Every agent-driven closure has a human override before it happens
- Skip for now: config-only integrations, CI plumbing and single-file plugins
- External-PR workflows never execute contributor code
- Channel servers keep bot tokens owner-only and refuse injected pairing requests