Loop Fleet Orrery

Every autonomous loop in an AI-augmented second brain, drawn as an orrery around the one thing they all orbit: the daily journal. Scheduled loops sit on a 24-hour dial at their fire time; hooks fire on events; in-session loops are hand-ignited. Hover a loop to see its read/write spoke to the shared state. Click any loop for its full contract — trigger, memory, oracle, exit.

The Fleet · loops shown

Data is the live knowledge/core/loop-registry.md — 15 scheduled tasks, 5 hook families, 6 in-session loops. Every loop declares a trigger, state, oracle, and exit per the vault's loop contract. The center is the journal because that's the convention: loops write machine-readable blocks into sections close-day later sweeps — the journal is the bus, not conversation memory.