Consider a SQLite store instead of a plain markdown file.
Only worth it for the multi-session / shared-queue clobber case: several Claude Code sessions writing one SIDECAR.md and overwriting each other.
Cost: Claude can no longer just Edit a file (needs a CLI/tool), and the human loses 'just cat it.' Topology unclear — revisit only if concurrent writes actually bite. A partitioned-file approach (one fragment per session, merged view) may beat a DB.
Parked from the sidecar dogfood queue.
Consider a SQLite store instead of a plain markdown file.
Only worth it for the multi-session / shared-queue clobber case: several Claude Code sessions writing one
SIDECAR.mdand overwriting each other.Cost: Claude can no longer just
Edita file (needs a CLI/tool), and the human loses 'justcatit.' Topology unclear — revisit only if concurrent writes actually bite. A partitioned-file approach (one fragment per session, merged view) may beat a DB.Parked from the sidecar dogfood queue.