Files
BFM-decomp/phase-ends
Drew T dab6ccb96f docs(phase-20): T6 batch-1 recovery — diagnose the loose-typing call-graph wall (gate cap)
- byte-verified: the 33 wave drafts that match_one-MATCH but fail the whole-binary gate are the
  loose-typing wall in the CALL GRAPH (a callee declared with conflicting types across overlay
  sites -> draft extern hits in-TU 'conflicting types'); match_one over-predicts (standalone +
  masks jal/hi/lo). All recovery levers fail (sig_unify/canon_draft_decls/fix_arity/no-proto/
  strip-externs); the only fix is per-site fn-ptr casts (SS17a) = Phase-21 recovery tooling
- diagnostic lesson: a failed in-TU build leaves a STALE .o (trust the whole-binary SHA, not objdump)
2026-06-21 01:12:18 -06:00
..
2026-06-10 22:02:07 -06:00

phase-ends/ — the living record

  • PhaseEnd_Phase[N].md — written at each phase boundary (format defined in PROJECT_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 every PhaseEnd_*.md in numeric order, then CURRENT_PHASE.md (if present) — in that order, every session.