mirror of
https://github.com/Druthulu/BFM-decomp
synced 2026-10-01 23:52:03 -04:00
Drew T
3b3728b19d
Drew asked for the next-session recommendation to be logged. Added a ranked "START HERE" block above the open-actions list: 1. func_8017C730 @ ov_SC03_013 FIRST (~30 min, +1,061 ins) -- the match ALREADY EXISTS; pure integration, no agent. Minimal preamble (bandsetup + 5 externs + 18 gte_* macros) then the §81 carve chain. Explicitly warns NOT to re-carry the whole region file (standalone MATCH that fails the real gate -- the §77 corollary, measured). 2. THEN func_80183814 (5,122, the biggest left) with one Opus 5 agent @ xHigh, and an HONEST expectation reset: the family bonanza is over. All six behemoths banked this session were one renderer family with matched relatives bracketing them -- that is why 5 of 9 levers were readable rather than discoverable. func_80183814 has 0 fingerprint overlap and 37 callees; it is a different subsystem. Budget TWO passes (the func_8017BF14 shape, not the func_8017C954 near-one-shot); a 99% round 1 is on-plan, not a stall. 3. Then func_8017D2DC (32 callees -- §71 IS usable) and func_8017DC1C (ZERO callees -- §71 CANNOT fire; use §79 DATA-symbol fingerprinting, shared syms only, and read a matched relative's fingerprint from its banked C since matched fns have no nonmatchings/*.s). A 0.00 from §71 on a leaf means "cannot answer", not "no relative" -- that error cost a whole agent brief today. Also notes that behemoths were the ONLY thing that moved distinct-code this session (+26,730 of +31,649), so they stay the lever if the queue holds.
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.