Files
BFM-decomp/config
Drew T 874f942fed feat(phase-30 S48-T6): wave 5 — 29 exemplars banked (73%)
Wave 5 (wf_7bce6c28-9f4, 78 agents, 11.4M tok across both halves): 40 targets
-> 36 agent-MATCH, 2 refuted, 2 NEAR, 0 FAIL, 0 drafts lost -> 29 BANKED.

RESUMED THROUGH A USAGE-LIMIT OUTAGE. The first run lost 40 agents mid-wave
(18 cracks + 22 verifiers). Resuming with byte-identical args replayed the 22
completed cracks from cache and re-ran only the dead ones — a limit outage
costs the unfinished work only.

⚠ THE INTERRUPTED RESULT WAS MISLEADING AND THAT IS MY BUG: crack_wave.js
classifies anything without verdict_check.confirmed as `refuted`, so 22 drafts
whose VERIFIER DIED read as 22 refutations. A dead oracle must not be
indistinguishable from a negative verdict — split `refuted` from `unverified`.

Two prior-seeded agents did better than asked:
- func_8017F2D4: found the prior draft SURVIVED in .run/wave3/, recovered it,
  then gated it IN SITU — spliced into the real destination TU, full pinned
  triple, masked-diff of the function out of the whole-TU object: 0 mismatched,
  279/279. That closes the §52b gap instead of trusting a standalone match. It
  also byte-confirmed the x5 reach on three symbol-remapped siblings and fixed
  the prior notes' TU pointer (they named a file holding only a caller).
- func_8017FFD0: VALIDATED its predecessor's claim rather than assuming it —
  built a no-barrier variant and reproduced the predicted -7 ins drift exactly,
  proving the __asm__ __volatile__("") cross-jump barrier is a real lever.

Bank rate across five waves: 67% -> 79% -> 69% -> 68% -> 73%.
2026-08-12 16:13:05 -06:00
..