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
+3 -2
View File
@@ -6,7 +6,7 @@ the standard first -- FORTH-79, FORTH-83, ANS 1994 -- then v3's table, not v3's
The cases are `v4/system/post_cases.c`; those of the words `capsules/v4/physics.4th` defines
need the kernel and are not run by the hosted product.
POST runs 991 cases. 783 are v3's, with what the hosted v3 binary did as the
POST runs 992 cases. 783 are v3's, with what the hosted v3 binary did as the
expected result. This file lists every other case, and why.
## 1. Rewritten: the standard's result, or v3's table's (159)
@@ -206,7 +206,7 @@ printed unless an address is printed; the values are not.
| `LIST.basic` | `1 LIST` | values left only |
| `SCR.after_list` | `1 LIST SCR @ . CR` | values left only |
## 3. Written by hand (29)
## 3. Written by hand (30)
For required words v3 has no case for. The expected results are the
standard's; no v3 run stands behind them.
@@ -242,6 +242,7 @@ standard's; no v3 run stands behind them.
| `WORD.count` | `: W3 BL WORD C@ . ; W3 ABC` | stack `empty`, prints `3 ` |
| `WORD.skips_leading` | `: W4 BL WORD COUNT TYPE ; W4 X` | stack `empty`, prints `X` |
| `L8-CARD@.basic` | `L8-CARD@ 0< . 64 U< . CR` | stack `empty`, prints `0 -1 \n` |
| `L8-HOLD.basic` | `18 L8-HOLD L8-CARD@ DROP . -1 L8-HOLD CR` | stack `empty`, prints `18 \n` |
## 4. v3 cases left out (52)
+17
View File
@@ -515,6 +515,23 @@ it.
- There is no decay, rolling window, pipelining, inference, L8, heartbeat
or Stadium wire on the node.
*Corrected 2026-11-20 (#189; ENGINE step 4 Phase 7, `plans/2026-11-13-engine-step4-phase7-the-loops-and-parity.md`).*
Section 2.2 was true of the lone node of 2026-10-07. It no longer is of v4 in its place in the system. The
kernel keeps every word's record (Phase 2) and runs v3's loops on it, at `call` and on the one heartbeat
(Phase 7, Tasks 1 to 4):
- L1: heat;
- L2: the rolling window;
- L3: decay, on touch and in the background;
- L4: pipelining and the hot-words cache, behind `ENABLE_PIPELINING` and `ENABLE_HOTWORDS_CACHE`, off as in v3;
- L5 and L6: inference;
- L7: the adaptive heartbeat, the kernel's one heartbeat (2026-11-17);
- L8: the Jacquard selector.
The loops also run on the 32 opcodes (`OPCODE_PHYSICS`). The words of `physics.4th` read and set them, among
them `L8-CARD@` and `L8-HOLD` (Task 9). Each acceptance boot asserts L1, L3, L2 with L5, and L8 at the
prompt (`scripts/qemu_session.py`, `loops()`), and `WORD_PHYSICS=0`, the revert, fails acceptance at POST.
The call-target count of `heat.c` described above is still there, beside the kernel's records.
### 2.3 What the v4 design documents say
The documents ruled on 2026-10-01 do not say "as v3". They say:
@@ -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