mirror of
https://github.com/Druthulu/BFM-decomp
synced 2026-09-30 07:31:59 -04:00
Drew T
4e17a7e77b
- decision-log (R31): §8 unblocked the SINGLE heaviest byte-weight chunk of the game — 9 of the 10 heaviest unmatched family cores are switch (jr) functions (func_80178D40 890x134 = 477K ins alone); jr substantial = 191 fams / 5.53M templatable ins. My "45 small jr families" recommendation (129K ins) was a light-tail trap — Drew caught it against the endgame plan (heaviest-byte-weight-first). Corrected next play: Fable5 crack the heavy jr cores -> §8 x134 bank -> parallel R22 verify; needs Task 7 (Fable5) un-paused (§8 makes that worth it now). - CURRENT_PHASE.md: SESSION-3 checkpoint as the fresh-session resume point (4 commits this session: tiny-band commit:0531, §8 PoC commit:0532, §8 x134 commit:0533, R22 parallel commit:0534; distinct-code 30.3->39.1%, instr-weighted 58.2->63.0%, R22 now ~50s)
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.