mirror of
https://github.com/Druthulu/BFM-decomp
synced 2026-10-04 16:28:11 -04:00
Drew T
c43f760fe5
Drew, on waking: he expected dozens of agents overnight and got three. The cause is the cadence, not the agents — the loop ran strictly serially (agent, gate, toolify, sweep) and the sweeps are hours long, so most of the night had no agent running. His rule was one agent at a time so the methodology is honed each time one lands, not one agent per sweep. - correction: agents run back-to-back, the next launched the moment the last lands; a sweep runs only when it does not stand between two agents, and never on the TU a live agent is scoring in (the scratch object is keyed by the TU). - stopping s7 cost a lesson worth keeping: the kill landed mid-write, inflight.json was empty, and --restore refused loudly with instructions instead of guessing (R102). 8 dirty files: 5 the run's recorded banks, 3 with no bank; the fleet named exactly those 3 binaries (ov_SC03_113, ov_SC04_004, ov_SC04_011), restored from HEAD. check-all: 218 passed, 0 failed of 218 lever_census --check: 29,140 pin/asm sites, 29,140 marked !FAKE, 0 UNMARKED — OK - snapshot row 17.
phase-ends/ — the living record
PhaseEnd_Phase[N].md— written at each phase boundary (format defined inPROJECT_CONTEXT.md). Append-only history: build log, deviations, commit message, rules added, changelog. Never deleted.CURRENT_PHASE.md— the in-phase autonomous log: approved phase plan, per-task checkboxes, current task pointer, blockers. Created at phase start, updated after every task, absorbed into the PhaseEnd file and deleted at phase close. This is the crash/compaction recovery point.DIGEST.md— the session-start digest: every phase's synopsis + every rule in full + the corrections to PROJECT_CONTEXT.md; appended at every PhaseEnd (P7).logs/Phase<N>.md— the archived in-phase worklogs (R19): NOT in the load order; consult on demand only.- Sessions read
PROJECT_CONTEXT.md, thenDIGEST.md, then the THREE most recentPhaseEnd_*.mdin numeric order, thenCURRENT_PHASE.md(if present), and replay its 🛑 SESSION CHECKPOINT block verbatim into the chat — every session (R64 candidate, 2026-09-05; ≈100k tokens + the checkpoint).