Files
LithosAnanke/docs/v4.0.0/POST-PARITY.md
T
Claude 41f8c1ec28 docs(v4): Phase 7's plan -- the loops on the word records, and v3's whole POST; the inventory (#189)
Rulings, Captain Bob 2026-11-13: the per-call loops "Every call, as v3"; the loops "Rewrite for v4"; Phase 7
accepted on "v3's whole POST", which brings Phase 3's words and Phase 4's ACL in as tasks of it; Mama's
20 cases as v4 words with v3's names -- "do not compose words in C99, use F18 and StarForth"; the C
modules (ACL, break_me) rewritten for v4.

docs/v4.0.0/POST-PARITY.md (Task 0): v3's POST by module against v4 on e8e7ec8b -- 888 cases in the 17
modules mkpost.py reads (550 Required, 317 for words v4 already has, 21 for words it lacks), 146 in the
nine it does not, 12 C tests; about 1,050 in all, 539 on v4 today.

Not pushed: no protocol run covers it yet (rules: batch docs with the next protocol).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-13 19:53:24 +00:00

74 lines
4.5 KiB
Markdown

# v3's whole POST on v4 -- the inventory
Started 2026-11-13, Task 0 of `plans/2026-11-13-engine-step4-phase7-the-loops-and-parity.md` (#189).
Captain Bob, 2026-11-13: Phase 7 is accepted on **"v3's whole POST"**. This counts every case of v3's
POST against v4 as it is on e8e7ec8b (377 live words), with `v4/tools/mkpost.py`'s own reader of
`v3/src/test_runner/modules/`. It proposes; it decides nothing.
## 1. The 17 modules `mkpost.py` reads today
v4's POST keeps only their cases for the FORTH-79 Required Word Set (550 read, 539 after what
`mkpost.py` leaves out: the keyboard, words that forget or damage the system, lines too long).
| Module | Cases | Required (on v4's POST) | Other words v4 has | Words v4 lacks |
|---|---|---|---|---|
| stack_words_test.c | 55 | 50 | 5 | 0 |
| return_stack_words_test.c | 11 | 11 | 0 | 0 |
| memory_words_test.c | 53 | 38 | 15 | 0 |
| arithmetic_words_test.c | 104 | 92 | 12 | 0 |
| logical_words_test.c | 103 | 64 | 39 | 0 |
| mixed_arithmetic_words_test.c | 40 | 18 | 22 | 0 |
| double_words_test.c | 125 | 21 | 104 | 0 |
| format_words_test.c | 31 | 25 | 6 | 0 |
| string_words_test.c | 49 | 15 | 34 | 0 |
| io_words_test.c | 73 | 61 | 3 | 9 (`BASE_OUTPUT`, `FORMAT_COMBO`: groups, not words) |
| block_words_test.c | 51 | 30 | 21 | 0 |
| dictionary_words_test.c | 49 | 22 | 15 | 12 (`SP!`, `SP@`; `COMPILATION`, `STACK_MGMT`: groups) |
| dictionary_manipulation_words_test.c | 29 | 16 | 13 | 0 |
| vocabulary_words_test.c | 22 | 19 | 3 | 0 |
| system_words_test.c | 7 | 4 | 3 | 0 |
| defining_words_tests.c | 32 | 22 | 10 | 0 |
| control_words_test.c | 54 | 42 | 12 | 0 |
| **Total** | **888** | **550** | **317** | **21** |
The 317 test words v4 already has; they are left out only because `mkpost.py` keeps the Required set.
## 2. The nine modules `mkpost.py` does not read
| Module | Cases | Words v4 lacks | Kind |
|---|---|---|---|
| q48_words_test.c | 28 | none | FORTH lines; every word is on v4 |
| starforth_words_test.c | 29 | `ENTROPY!` `ENTROPY@` `RESET-ENTROPY` `TOP-WORDS` `WORD-ENTROPY` `(-` | FORTH lines; the entropy and top-words words read the physics |
| physics_freeze_words_test.c | 7 | `FREEZE-WORD` `UNFREEZE-WORD` `FROZEN?` `HEAT@` `HEAT!` `DECAY-RATE@` | FORTH lines; the loops' words |
| inference_words_test.c | 9 | `INFER-RUN` `INFER-DECAY-SLOPE` `INFER-DECAY@` `INFER-EARLY-EXIT@` `INFER-FIT@` `INFER-VARIANCE@` `INFER-WINDOW-WIDTH` `INFER-WINDOW@` `Q.VARIANCE` | FORTH lines; the inference engine's words |
| stress_tests.c | 45 | none (14 group names) | FORTH lines |
| integration_tests.c | 8 | none (3 group names) | FORTH lines |
| mama_forth_words_test.c | 20 | `CAPSULE-BIRTH` `CAPSULE-RUN` `CAPSULE-TEST` `CAPSULE-COUNT` `CAPSULE@` `CAPSULE-FLAGS@` `CAPSULE-HASH@` `CAPSULE-LEN@` `MAMA-VM-ID` `VM-COUNT` | FORTH lines about v3's VMs and capsule directory |
| acl_words_test.c | 11 | -- | **C**, against v3's VM's fields (`vm->...`), not FORTH lines |
| break_me_tests.c | 1 | -- | **C**, one routine against v3's VM |
## 3. For ruling
1. **Mama** (20 cases): the words are v3's: a VM ID, a VM count, v3's capsule directory. v4 has nodes,
births (`BIRTH`, `NODE-ME`) and its own capsules. Written as v4 words with v3's names and meaning,
mapped to v4's equivalents, or out of parity?
2. **The C modules** (ACL, break_me): they read v3's VM's fields directly. Rewritten as tests of the
same behaviour against v4 (FORTH lines where they can be, host tests in C where they cannot), or
out?
3. **The group names** (`STACK_BOUNDARY`, `COMPILATION`, ...): v3 files cases under a group, not a word.
They are cases like any other, run as they are; nothing to rule unless a case fails.
**Ruled (Captain Bob, 2026-11-13):**
1. **Mama:** v4 words with v3's names and meaning, mapped to v4's equivalents -- "but do not compose
words in C99, use F18 and StarForth". The words are written in the system's F18 or in StarForth;
where only the kernel can answer (the registry, the capsules it holds), the word asks it by a
request on port 0, as `KERNEL-WORD` words do. The 20 cases run as they are.
2. **The C modules:** rewritten for v4, the same behaviour shown case by case -- as FORTH lines in POST
where they can be, as host tests in C where they need internals.
## 4. What parity needs, in count
About 1,050 cases: 888 in section 1, 146 FORTH-line cases in section 2's modules, and the C modules' 12 tests -- 1,046. v4 has 539 today.
The loops' own words (physics freeze, inference, entropy, top words) are 22 cases; the ACL and Mama
modules wait on section 3.