Files
BFM-decomp/docs/frontier-p30.md
T
Drew T 4f7c3b64a3 docs(phase-33): commit-map + citations resolved to the rewritten history (C4–C7 — the tip commit)
- docs/commit-map.tsv: 4,032 rows (ordinal of the ORIGINAL main -> rewritten hash, author/committer dates, subject);
  1 pruned row of zeros (ordinal 1712, "session archive update"); 0 old hashes asserted; ordinal 1 unchanged by the
  rewrite (byte-identical)
- resolve_tokens: 1,238 commit:NNNN tokens -> shortest-unique new hashes in 98 files (docs, phase-ends, logs, tool
  docstrings, 2 C comments, the A5 evidence logs); residue left as tokens: commit:1712 x4 (the pruned commit),
  commit:orphan-24 x2, commit:orphan-26, commit:orphan-35 (cited commits that exist in no lineage)
- the rewrite (C4): filter-repo 2.47.0 on a bare clone of the C2 tip, 311 s, exactly 1 pruned, main 4,032 -> 4,031;
  the pre-rewrite history is mirrored in the private archive repo and in the local bundle
- the proof (C5): verify_rewrite 4,031 pairs / 0 failures; absent_scan 0 offenders; gate_scan 0 offenders on the clone
- adoption (C6): 100 text files differ at the tip, 0 purge paths, 0 added/deleted; leftover refs dropped; no gc yet
- resolver skips tools/public_rewrite/ (its self-test fixtures are the token grammar, not citations); repo-local
  identity is the GitHub noreply address from here on; CURRENT_PHASE: C4–C7 logged, checkpoint -> NEXT = C8
2026-09-06 23:28:39 -06:00

39 lines
3.8 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# The P30 frontier report (T0(f) — report point #1)
> **Generated 2026-07-30 at HEAD `407ff8f85`**, after the T0 instrument repairs (a–e), from
> same-tree regenerations only: `progress.fleet.md` · `family-hseq.md` (+`.run/family_hseq.json`) ·
> `worklist.md` · `.run/fuel_manifest.json` · `.run/autopsy/residuals.jsonl` · `docs/autopsy.md`.
> Every number below is re-derivable from those artifacts at this HEAD (R33/R35). This file is a
> point-in-time report — it is NOT re-baselined; consume via a fresh regen.
## Standing
**87.5% instr** (11,493,049/13,141,652) · **78.0% distinct** (4,396,900/5,634,875) · **92.00%
fn-count** (325,417/353,720) · **140/140 byte-identical** (R22 re-proven this session after the
21-file include fix) · dedup 1886/0 · 0 NON_MATCHING.
**Open:** overlays 27,248 instances / 17,629 distinct / 1,587,311 ins · main 1,034 stubs (0.7%
game-code) · resident 14.
## The pinned populations (what T0 was for)
| population | pinned value | consequence |
|---|---|---|
| **Stranded byte-correct drafts** (T1 fuel) | **108 match_one-MATCH** + 1,178 near + 63 nobuild (autopsy, 1,349 rows, 0 classifier errors, second-oracle agree) | T1's recovery sweep has 3× the population the S16 sample suggested (36 → 108 fresh MATCHes) |
| **The `-O0` cluster** (T2) | **18 families / 2,192 open members** (2,131 on o0b-bearing overlays / 61 SC07); 15/18 exemplar-matched. **⚠ CORRECTED by the T2 ×1 probe (R14):** o0b-*bearing* ≠ o0b-*adjacent* — T85's `0x801457A4` banked by APPEND only because its address abuts the o0b object's END; the remaining families (`0x8013Bxxx–0x8013Cxxx`, below the whale) mis-place on append (probe: 1/1 gate-reject) and the alternative per-fn isolation IS the re-carve that trips Arm-A | **T2's real substance is the Arm-A `+0x20` defect itself** (first hypothesis: the re-carve lets splat re-GUESS a data-symbol boundary → pin the shifting symbol in the config and re-probe). The generalized driver (`rollout_o0.py`) stands as the sweep harness once placement works, and for any future adjacent case |
| **Zero-crack roster** (Lane A) | **114 families / 3,166 open members / ~204k weighted ins** (28 substantial). The head of the roster IS the `-O0` route set — T2 and Lane A open together | Propagation-only fuel behind already-matched exemplars; the non-o0 tail is ~100 small families for `family_sweep`/`dedup_extend` as classed |
| **Concentration** | **top-20 = 24.0% · top-100 = 44.8%** of open family weight (1,587,311 ins) | Lane B works the head down; flatter than SESSION-13's 53% (the campaign consumed the head — expected) |
| **Core queue** (fresh worklist) | **101 live stubs / 261,789 gain-ins**; GIANTs (`func_801412A8` close=110, `func_80178004` close=91) = 19.1% of it | The stale 160/583k rows are gone; queue is oracle-derived |
| **Instrument repairs shipped** | gate_stage **stage-0** + journal undo (§122) · rtu_match error surfacing · digests scope+HEAD-stamped · backlog scanner deleted (R33; 0 divergence vs corpus across 131 binaries) · 21-file include fix (R22 140/140) · autopsy refreshed | Every number above was produced AFTER the repairs (R35 sequencing) |
## The opening play this frontier implies
1. **T0.5 prefetch batch** (background): tail + main Ghidra-C — fuel for Lanes B/C and P31.
2. **T1 recovery sweep [Ultracode]** over the 108 stranded MATCHes (+ the 10 named S16 drafts) —
cheapest distinct wins, now through the stage-0-safe ladder.
3. **T2 the generalized o0b driver [Max]**: ~9 non-jr route-ready `-O0` families first (~950
members), then the jr+o0 composites (probe ×1 before ×136), then the 3 exemplar cracks; the 61
SC07 members and any re-carve-needed residue go to the wall ledger with evidence.
4. **T3 lanes** as planned — Lane A's non-o0 tail, Lane B down the concentration head, Lane C on
prefetched seeds, Lane D (PINS 19 / W4 / permuter backlog).