Problem
There is no mechanism to prune, compact, or TTL events for sessions that have reached a terminal state (Completed/Failed). The event journal is append-only.
Evidence (Katagami pipeline, 5-query run)
- 112 sessions produced 55,774 Session events (317MB)
- All sessions are in terminal state (Completed/Failed)
- Events include per-turn granularity (ProgressMade, ProcessToolCalls, HandleToolResults) that has no value after completion
- A snapshot + trajectory is sufficient for audit of completed sessions
Impact
Database grows linearly with session count and turn count, with no ceiling. Manual DB trimming was required to enable server restart after the pipeline run.
Problem
There is no mechanism to prune, compact, or TTL events for sessions that have reached a terminal state (Completed/Failed). The event journal is append-only.
Evidence (Katagami pipeline, 5-query run)
Impact
Database grows linearly with session count and turn count, with no ceiling. Manual DB trimming was required to enable server restart after the pipeline run.