rajamesandClaude Opus 5.5
13335dcc9c
The number-printing words, on pictured output and TYPE, executed on the golden model at both cell widths against a C reference (ten bases, eleven field widths) and six recorded transcripts of the v3 binary. Each plain word is its .R word with a width of 0; all six share one tail. The field width waits in a variable, (W), so the picture runs no deeper than it does on its own: each word leaves its caller 4 data cells and 2 return entries. As v3, the .R words print a trailing space. Unlike v3, D. takes ( lo hi ), prints the whole double, and printing honours BASE. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
v4/
StarForth v4: the 32-instruction F18-derived core. The design lives in
docs/v4.0.0/JUSTIFICATION.md (why) and docs/v4.0.0/DECOMPOSITION.md
(every v3 word mapped to a v4 fate).
The first deliverable is the hosted C99 golden model (JUSTIFICATION.md §10,
step 1). It must pass POST and hold K≡1.0 with 32- and 64-bit cells on all
three host ISAs.
Acceptance (JUSTIFICATION.md §16): v4 must be equivalent to v3 at any point
in time, with the same vocabularies and behaviour, on the F18-derived engine;
and every ISA, hosted and bare metal, must still reach its ok prompt.
make -C v4 test passing is a development check, not acceptance.
What exists so far is the single node: registers, circular stacks, memory, all
32 opcodes, per-opcode and per-call-target heat, and a console capture
register (CONSOLE-TX) standing in for the console node until the mesh exists. make -C v4 test builds
and runs the tests at both cell widths; make -C v4 sanitize repeats them
under ASan and UBSan. There is no compiler capsule, no POST and no K
measurement yet.