Batch job not request handler; volume mounts would rot as projects are added;
HTTP keeps the observer relocatable to another machine. BIT stays in Docker.
Brian caught that the spec stated a frame and then violated it. The test is
'does it produce or derive facts -> BIT; does it require knowing Brian -> Lyra.'
The git observer produces facts and knows nothing about Brian; cadence health
derives from BIT's own time_logs and goal fields. Both belong in BIT.
Putting them in Lyra would have made BIT's data true only while Lyra was
running -- the exact coupling the separable frame exists to prevent. It also
makes BIT better standalone: auto-logged time plus cadence on the project
cards, which today show only a creation date.
Restructured into Part A (BIT, deterministic, no LLM) and Part B (Lyra, the
pick and the surfacing). Observer ships in BIT's repo but runs on the host and
POSTs over HTTP, so repos need no volume mounts.
Long-horizon project tracking. Key finding: BIT records every project as
last-touched 2026-03-21 while project-lyra has 177 commits across 30 working
days since. A manual tracker doesn't decay to neutral, it decays to actively
demoralizing — absence of records looks like absence of work.
Frame mirrors the pokerlog: BIT is the system of record, Lyra is a client.
BIT enumerates what's possible (/actionable returns 68 tasks); Lyra picks one.
Also found: the sessions table already exists as TimeLog on BIT's dev branch
(Feb 2026, never deployed), along with project goals and a pomodoro widget.
The blockers branch (deployed) has the dependency graph and actionable view.
Neither branch has both; divergence is 3 commits.
serversdown