SDLC Status Dashboard

2026-08-10 11:20:05 +00:00

Current Phase
documentation
Phases Done
3 / 9
Completion
33%
Re-enter At
existing-solutions
3 completed6 remaining

Pipeline Progress ?
⚪ not started not yet begun
✏️ draft initial version
🔍 in review under review
🚧 in progress actively worked on
⛔ blocked waiting on dependency
✅ done completed
⏭️ skipped not applicable

Foundation
Done: completed requirementsNot Started: not yet begun existing-solutionsNot Started: not yet begun codebase-analysisNot Started: not yet begun feasibilityDone: completed specificationNot Started: not yet begun plan
Build
Not Started: not yet begun implementationDone: completed testing
Ship
Not Started: not yet begun documentation
❓ Open Questions📖 Vocabulary

Requirements: Session Sync & Management

Overview

The syncThe process of discovering new/changed session files and updating the database engine discovers sessionA single conversation or interaction with an AI coding agent, typically one run/launch files from all configured AI coding agentAn AI coding tool that produces session files (Claude, Codex, Cursor, etc.) directories on disk, parses them using agentAn AI coding tool that produces session files (Claude, Codex, Cursor, etc.)-specific parsers, sanitizes the extracted data, and writes it into the SQLiteEmbedded relational database used as the primary session archive database. It provides incremental and full resync modes, a file watcher for live updates, and supports remote syncSyncing sessions from other machines via SSH or HTTP from other machines via SSHSecure Shell and S3Simple Storage Service (Amazon S3-compatible)-compatible storage.

Stakeholders

Stakeholder Interest
End user Sessions are automatically discovered and indexed without manual intervention
Operator Can trigger resyncs and monitor syncThe process of discovering new/changed session files and updating the database status
Developer Extensible provider system for adding new agentAn AI coding tool that produces session files (Claude, Codex, Cursor, etc.) parsers

Functional Requirements

ID Priority Requirement
FR-1MustThe system shall discover sessionA single conversation or interaction with an AI coding agent, typically one run/launch files from all configured agentAn AI coding tool that produces session files (Claude, Codex, Cursor, etc.) directories on startup Must The system shall discover sessionA single conversation or interaction with an AI coding agent, typically one run/launch files from all configured agentAn AI coding tool that produces session files (Claude, Codex, Cursor, etc.) directories on startup
FR-2MustThe system shall parse sessionA single conversation or interaction with an AI coding agent, typically one run/launch files using agentAn AI coding tool that produces session files (Claude, Codex, Cursor, etc.)-specific parsers to extract messages, tool calls, and usage data Must The system shall parse sessionA single conversation or interaction with an AI coding agent, typically one run/launch files using agentAn AI coding tool that produces session files (Claude, Codex, Cursor, etc.)-specific parsers to extract messages, tool calls, and usage data
FR-3MustThe system shall sanitize parsed data (clamp tokens, blank timestamps, coerce roles, strip control characters) Must The system shall sanitize parsed data (clamp tokens, blank timestamps, coerce roles, strip control characters)
FR-4MustThe system shall write parsed sessions to SQLiteEmbedded relational database used as the primary session archive in batches of 100 with 8 parallel workers Must The system shall write parsed sessions to SQLiteEmbedded relational database used as the primary session archive in batches of 100 with 8 parallel workers
FR-5MustThe system shall support incremental syncThe process of discovering new/changed session files and updating the database (only changed files) and full resync Must The system shall support incremental syncThe process of discovering new/changed session files and updating the database (only changed files) and full resync
FR-6MustThe system shall provide a file watcher using fsnotifyGo library for filesystem event notification with configurable debounce Must The system shall provide a file watcher using fsnotifyGo library for filesystem event notification with configurable debounce
FR-7MustThe system shall run a periodic full scan every 15 minutes Must The system shall run a periodic full scan every 15 minutes
FR-8MustThe system shall track failed/unparseable files by path and mtime via a skip cache Must The system shall track failed/unparseable files by path and mtime via a skip cache
FR-9ShouldThe system shall support syncing sessions from remote machines via SSHSecure Shell Should The system shall support syncing sessions from remote machines via SSHSecure Shell
FR-10ShouldThe system shall support S3Simple Storage Service (Amazon S3-compatible)-compatible object storage as a sessionA single conversation or interaction with an AI coding agent, typically one run/launch source Should The system shall support S3Simple Storage Service (Amazon S3-compatible)-compatible object storage as a sessionA single conversation or interaction with an AI coding agent, typically one run/launch source
FR-11ShouldThe system shall emit SSEServer-Sent Events notifications after each write pass for live UI updates Should The system shall emit SSEServer-Sent Events notifications after each write pass for live UI updates
FR-12ShouldThe system shall auto-start the daemon on demand for commands that need fresh data Should The system shall auto-start the daemon on demand for commands that need fresh data

Non-Functional Requirements

ID Priority Category Requirement
NFR-1MustSync should process at least 100 sessions per second Must Performance Sync should process at least 100 sessions per second
NFR-2MustFailed parses must not crash the syncThe process of discovering new/changed session files and updating the database engine; errors are tracked and skipped Must Reliability Failed parses must not crash the syncThe process of discovering new/changed session files and updating the database engine; errors are tracked and skipped

Acceptance Criteria

  • FR-1MustThe system shall discover sessionA single conversation or interaction with an AI coding agent, typically one run/launch files from all configured agentAn AI coding tool that produces session files (Claude, Codex, Cursor, etc.) directories on startup
    • Given agentAn AI coding tool that produces session files (Claude, Codex, Cursor, etc.) sessionA single conversation or interaction with an AI coding agent, typically one run/launch files exist on disk
    • When the server starts
    • Then all sessionA single conversation or interaction with an AI coding agent, typically one run/launch files are discovered and queued for parsing
  • FR-2MustThe system shall parse sessionA single conversation or interaction with an AI coding agent, typically one run/launch files using agentAn AI coding tool that produces session files (Claude, Codex, Cursor, etc.)-specific parsers to extract messages, tool calls, and usage data
    • Given a sessionA single conversation or interaction with an AI coding agent, typically one run/launch file for a supported agentAn AI coding tool that produces session files (Claude, Codex, Cursor, etc.)
    • When the syncThe process of discovering new/changed session files and updating the database engine processes it
    • Then messages, tool calls, and usage data are extracted
  • FR-5MustThe system shall support incremental syncThe process of discovering new/changed session files and updating the database (only changed files) and full resync
    • Given a previously synced sessionA single conversation or interaction with an AI coding agent, typically one run/launch file is modified
    • When the file watcher detects the change
    • Then only that sessionA single conversation or interaction with an AI coding agent, typically one run/launch is re-parsed and updated
  • FR-6MustThe system shall provide a file watcher using fsnotifyGo library for filesystem event notification with configurable debounce
    • Given the server is running
    • When a new sessionA single conversation or interaction with an AI coding agent, typically one run/launch file is created
    • Then it is detected and synced within the debounce window

Open Questions

  1. What are the performance characteristics of S3Simple Storage Service (Amazon S3-compatible)-based sessionA single conversation or interaction with an AI coding agent, typically one run/launch discovery at scale?