v4: acceptance asserts the loops -- L1, L3, L2 with L5, L8 -- and WORD_PHYSICS (#189, Phase 7 Task 9)
Build / Image RASPI (push) Successful in 6m16s
Build / Image PC (push) Successful in 6m19s
Build / Image MILKV (push) Successful in 8m30s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 16m7s

The acceptance session's loops(), at every v4 boot's prompt: a word's
heat (L1), its decay from a set heat (L3), INFER-RUN's variance and
width with L8 held on card 18 (L2, L5), and L8's changes. L8-HOLD
( card -- ), request -42, beside L8-CARD@, with its POST case: POST 992.
WORD_PHYSICS (Kconfig.physics, default y) turns the word loops off: a
boot with it off fails acceptance at POST (ruled 3a). Measured on amd64:
heat 6, 1000 cooled to 0 in 40 s, width 455, 66 changes. L8 unheld
settles on card 11, with the window off, so L2/L5 hold a card (ruled).
test_mesh_boot: L8-HOLD failed first, 144 checks now. V3-PARITY.md 2.2
corrected, dated. Gates pass, POST 992/992.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
Claude
2026-11-20 18:06:09 +00:00
parent 43f8687f70
commit a9a8687fa5
31 changed files with 3767 additions and 17 deletions
@@ -253,6 +253,18 @@ The words of Task 4 read them at the prompt, on the real boot, so the session ca
turns the per-call and per-tick word loops off. It is a real revert, as ruling 7's is. The session's
checks are seen to fail on `WORD_PHYSICS=0`, and pass on the boot as built. Step 1 above, the stub, is
replaced by this. Asked: that, or a one-off stub in a diagnostic build.
**3a, ruled 2026-11-20: "POST's failure is enough".** A `WORD_PHYSICS=0` boot fails acceptance at POST
(amd64, `logs/20261120-task9/amd64-nophysics.txt`): its `ENTROPY@` cases need a word's heat. So it
never reaches the prompt, and every loop check fails with it, but not one at a time. The checks are
then measured and passed on the boot as built. Nothing in POST changes. Asked: that, POST's physics
cases skipped under `WORD_PHYSICS=0`, or each loop failed by holding L8 on cards that turn it off.
**The L2/L5 check, measured 2026-11-20** (taken as recommended: Captain Bob, "Yes go on"). On amd64,
as built, `INFER-WINDOW@` was 0. Every loop but L1 is gated by L8's current card, and L5's width is
computed only on ticks whose card has L5 on, so on a real boot it may or may not be set. The check is
instead that `INFER-RUN INFER-VARIANCE@` is not 0 after the workload: the variance is computed whenever
the window holds calls, whatever the card, and stays 0 with no window. That is L2's window with the
engine run on it. The width is printed beside it, not checked; L5's width stays in `test_mesh_boot`,
where L8 is held on a card. The same boot: L1 H=6, L3 1000 cooled to 0 in 40 s, L8 65 changes on card 11.
## Review focus