mirror of
https://github.com/Druthulu/BFM-decomp
synced 2026-09-27 22:45:39 -04:00
Drew T
8541238e60
~2,200 banked today. Throughput went 65 -> 554 req/min peak by removing harness defects, not by changing models. The registry was wiped THREE times by four non-atomic truncating writes, now routed through tools/mk_write.py; each wipe made every gate reject every draft. The strategic picture for next session: 3,062 open crackable collapse to ~334 drawable skeletons, ~308 of them generation 6+, with ~3,900 siblings behind them that bank by remap. Wide waves convert at 1-5% and the GATE is the bottleneck (30-67 min at 8% CPU). Optimise banks per gate minute. The reasoning budget is NOT the cause of the decline — truncation is inversely correlated with bank rate. A Fable analyst is writing docs/tool-designs/frontier-analysis-s60.md, briefed that we are not married to the ox-wave model; that document is the first thing to read next session. Five rule candidates (R51-R55), each earned by a defect that fired today.
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.- Sessions read
PROJECT_CONTEXT.md, then everyPhaseEnd_*.mdin numeric order, thenCURRENT_PHASE.md(if present) — in that order, every session.