From b5a476456713cefa059b5b4f82366944ab988928 Mon Sep 17 00:00:00 2001 From: "Claude (auto-RE)" Date: Wed, 12 Aug 2026 00:00:37 +0000 Subject: [PATCH] re: the XBG7 silent mis-decode is in the per-block anchor, not the grouped-pool one Tried the obvious fix: make anchor_grouped_meshes pick the best-scoring vb0 instead of the first candidate clearing the 0.85 gate. It changed nothing -- still 5480 of 6294 decoded, still 125 inconsistent -- and instrumenting the pivot loop shows why: for e303_wep_01 that function never runs. The resource has a single sub-mesh, so it goes through the per-block adjacency path (anchor_pool_mesh) instead. Recorded because the grouped-pool anchor is the prominent, well-documented one and the natural first suspect; the fault is in the other path. The change is reverted -- untargeted, unproven, and it added a scoring path for no measured benefit. The idea behind it (several vb0 candidates can clear the gate, and first-in-scan-order is an arbitrary tiebreak) still applies to whichever anchor is actually at fault. Co-Authored-By: Claude Opus 5 (1M context) --- docs/re/structures/xbg7-mesh.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/docs/re/structures/xbg7-mesh.md b/docs/re/structures/xbg7-mesh.md index 44e041b..5b12d85 100644 --- a/docs/re/structures/xbg7-mesh.md +++ b/docs/re/structures/xbg7-mesh.md @@ -338,3 +338,21 @@ majority is the turret the render and the runtime capture both support. `_rou_e302_base_break` the majority is the *larger* span (`685×1206×1444`, 8 of 15) and nothing yet says which is right. Use the detector to flag; do not silently rewrite geometry on a vote. + +### Where the mis-decode is *not*: the grouped-pool anchor + +An attempt to fix it by making `anchor_grouped_meshes` choose the **best-scoring** +`vb0` (rather than the first candidate clearing the 0.85 gate) changed **nothing** +— still 5 480 of 6 294 decoded and still 125 inconsistent — and instrumenting the +pivot loop shows why: for `e303_wep_01` it never runs. **The resource has a single +sub-mesh, so it is decoded by the per-block adjacency path +(`anchor_pool_mesh`), not the grouped-pool anchor.** + +So the silent mis-decode lives in the **per-block** anchor. That is worth knowing +before anyone else spends time on the grouped-pool pivot, which is the more +prominent and better-documented of the two and the natural first suspect. + +The change was reverted: it was untargeted, unproven, and added a scoring path +with no demonstrated benefit. (Its one reusable idea — that several `vb0` +candidates can clear the gate and first-in-scan-order is an arbitrary tiebreak — +still applies to whichever anchor turns out to be at fault.)