docs: roadmap entry for persistent log storage (#27)#28
Merged
Conversation
Records the flight-recorder persistence path discussed 2026-06-14: persist events to a local DB so logs survive crashes, group per session, and let a consumer dump previous sessions. Captures the design constraints (noop parity, SQLDelight-vs-Room, write-behind hot path, schema, retention-as-configure, on-disk security) and defers implementation to a design session (#27) after 1.0. This is also why #18 (in-memory configure(capacity)) was dropped — the capacity knob becomes a retention policy once persistence lands. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a "Storage & persistence — flight recorder" section to
docs/ROADMAP.mdcapturing the persistence path discussed today, linked to the design-session issue #27.Also records why #18 (
configure(capacity)) was dropped: the in-memory capacity knob becomes a retention policy once persistence lands, so shipping it now would be throwaway public surface.Docs-only.
🤖 Generated with Claude Code