Captain Bob ruled: Block n lands at n-R; the lowest block is
interpreted; chaining is the developer's; together, v4 first.
- v4_blocks_place_capsule copies each Block n into RAM block n - R as 16
lines of 64, space-padded, in any file order. A later block of the
same number overwrites. It refuses a block below R.
- The mesh's load(), its capsule reader (CAPSULE-OPEN/(LINES), so a
child's forth79.4th via BIRTH too), boot.c and test_host_unit's model
each place a capsule, then interpret "<lowest> LOAD".
- mkdictionary.py skips --> when it types capsules at the hosted prompt.
- The v4 capsules are renumbered into R..2R-1, landing at RAM 1900 and
up, away from POST's blocks 0-5. Each is chained with -->, and
centre.4th's gap at 8103 is closed.
Test first:
- test_host_blocks.c gained 6 placement checks; it failed to build
before.
- test_mesh_boot.c checks forth79's lowest block in RAM block 1900; it
failed before.
After: POST is 990/990; all 52 tests at 64 bits, test-32, hosted-check
and ASan/UBSan pass; the amd64 kernel builds; the dictionary has 404
words.
Logs are in logs/20261118-capsule-place.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
Captain Bob ruled "Overwrite. That's it. Deterministic and final", within
a capsule and across capsules, "consistent with VOCABULARY FORGET & FENCE
philosophy, not implementation". Of what only prevented collisions:
"All of it goes".
- The cross-capsule collision gate is gone.
- tools/capsule-reserved.txt and its check are gone.
- The interactive resolver and its claim registry are gone.
- BLOCK_MAP.md says "Blocks used", and marks a shared number "the later
write overwrites". It is a convenience, not a gate.
- An unknown option is refused with the usage. A removed mode was
otherwise taken for the capsules directory, with its next argument as
the output file.
Test first: scripts/test_mkcapsule_overwrite.sh, 9 checks.
- The before-run failed 7. A repeat within one capsule already built,
since there was never a check for it.
- After: all 9 pass.
step 1's test still passes, the amd64 build is clean, all 40 capsules
lint, and the mesh boot passes 109 checks with POST 990/990.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
Captain Bob ruled that the offset is the RAM block count, not a literal
2048.
- v3/include/blk_layout.h defines it, 2048 by default. block_subsystem.h
derives BLK_RAM_BLOCKS (2080) and BLK_DISK_START from it.
- Kconfig.kernel has the symbol. kernel/Makefile passes it to the
kernel's C code and builds mkcapsule and mkartemis with it.
- mkcapsule's two literal 2048s are now the knob.
The default value is unchanged, so the layout and the media are as before.
Test first: scripts/test_capsule_ram_blocks.sh, 8 checks.
- The before-run failed 4: the knob did not exist and mkcapsule ignored
it. Its three Makefile checks also hit a SIGPIPE flaw in the test,
fixed before the after-run.
- After: all 8 pass.
The amd64 build and mkartemis build clean. All 40 capsules lint. The
mesh boot passes 109 checks with POST 990/990. test_host_blocks,
test_host_quit, test_host_unit and test-32 pass.
Logs are in logs/20261118-ram-blocks-knob.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm