mirror of
https://github.com/Druthulu/BFM-decomp
synced 2026-10-01 07:40:42 -04:00
Drew T
bb0e95c7ca
On a landing, in this order: --try the agent's body to prove the claim on bytes (seconds), launch the next agent immediately, and only then bank, propagate, harvest the idiom into a generator, gate and commit — all of it while the new agent runs. Still one agent at a time so the methodology is honed at each landing, but the slot is refilled in seconds rather than after an hour of gating. The one real hazard: the scorer's scratch object is keyed by the TU, so two processes scoring the same TU collide. Banking beside an agent is safe (a bank is IDENTICAL on the whole object by construction and cannot move the agent's function's bytes), but a --propagate that reaches the live agent's TU is deferred until that agent lands. Sweeps are not part of this lane: they write candidates across many TUs for hours, which is what emptied the agent slot for six of the eight hours of last night.
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).