accept-aarch64 failed at BIRTH. The new CPU snapshot showed the kernel
looping, not hung. The other stages passed, including riscv64, the
stick, test-32, the proofs and the images. I ran them before reading
aarch64's result, which was the wrong order.
The repro boot (logs/20261119-012050) gave the code at each PC. Matched
in the loader EFI's map, they name bitmap_get inside
stadium_resident_heat_total, then background_decay and isqrt64. That is
the heartbeat's load, which walked all 335,544 Stadium cells every tick.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
CI's Acceptance fails on aarch64 at BIRTH on every head since 58d0e887.
The birth takes more than 300 s there and does not reproduce here: about
11 s, unsigned. The heartbeat spiral was ruled out by an instrumented
scratch kernel.
Captain Bob ruled "Diagnose on CI". On a failed check, the session script
asks QEMU's monitor for the registers three times, a second apart, and
prints the program counters, so CI's next failure shows where the kernel
is and whether it moves. A monitor that does not answer does not stop
the run.
Test first: scripts/test_qemu_session_snapshot.sh, 5 checks; 3 failed
before. The register text was checked on real, paused QEMU for aarch64,
riscv64 and x86.
The evidence and the measurements are in logs/20261119-ci-snapshot. The
local aarch64 timing run is in logs/20261118-235613.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
Every stage passes. POST is 990/990 on all four boots, with one
dict_hash (0x847bd8ef42f53e14). test-32, the proofs, the images and the
docs pass. accept-aarch64 (411 s) and docs ran in the background, each
alone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
Captain Bob ruled: the line for new work is drawn with a merge, then a
tag, v4.0.0-alpha.5. This sets LITHOS_VERSION in kernel/Makefile and
updates README, CHANGELOG and CLAUDE.md to match.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
Every stage passes. POST is 990/990 on all four boots, with one
dict_hash (0x847bd8ef42f53e14). test-32, the proofs, the images and the
docs pass. accept-aarch64 (416 s) and docs ran in the background, each
alone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This covers capsule blocks steps 1-4 for v4. Every stage passes.
- POST is 990/990 on all four boots.
- One dict_hash on the three ISAs: 0x847bd8ef42f53e14 (new, from
loading capsules through blocks).
- test-32, the proofs, the images and the docs pass.
- accept-aarch64 (435 s) and docs ran in the background, each alone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
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
Every stage passes. On all four boots POST is 990/990, with one
dict_hash (0xf4e9fdc94f6bfc77). test-32, the proofs, the images and
the docs pass. accept-aarch64 (397 s) and docs ran in the background,
each alone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
Every stage passes. On all four boots POST is 990/990, with one
dict_hash (0xf4e9fdc94f6bfc77, word_count=404). test-32, the proofs,
the images and the docs pass. accept-aarch64 (401 s) and docs ran in
the background, alone, at Captain Bob's rulings.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
All seven other stages passed: POST 990/990 on all four boots, one
dict_hash (0xf4e9fdc94f6bfc77, word_count=404), test-32, the proofs and
the images.
aarch64 went past 590 s twice in the foreground, killed at the BIRTH
step. One background run, at Captain Bob's ruling, passed in 429 s with
the birth's parity recorded.
The docs stage failed because the dictionary gate found no entry for
STARSHIPOS. The entry comes next, then the protocol again.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
COLD set VOC-LINK to 0, assuming the sealed system has one vocabulary.
With starshipos.4th sealed in, STARSHIPOS fell out of the chain after
COLD. A word defined in it then forgotten, or COLDed away, hung the
node. ACL-INIT-PRIMITIVES would also have skipped its words.
FORGET's loop is now (PRUNE-ALL). It drops the vocabularies above (Q)
and prunes the lists of those that stay. FORGET calls it as before, and
COLD calls it with the sealed DP. No new cell and no new word.
Test first in test_mesh_boot.c: FORGET and COLD of a word in
STARSHIPOS, and STARSHIPOS's own words staying. The before-run hung and
was stopped at 500 s. After: 109 checks pass, POST is 990/990, all 52
64-bit tests and test-32 pass, ASan/UBSan are clean, and the amd64
build is clean.
Found by Captain Bob's "make sure we're not applying incorrect logic".
Ruled: fix first, then the protocol. Logs are in
logs/20261118-cold-vocabularies.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
Every boot passed: POST 990/990 on all four, dict_hash
0x3172c04e863199f4 on the three ISAs. test-32, the proofs and the
images passed.
The docs stage was stopped. The protocol is superseded because a latent
fault was found: COLD drops STARSHIPOS from the vocabulary chain
(VOC-LINK 0). Captain Bob ruled: fix first, then the protocol.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
Captain Bob ruled that MACHINE.md stands. The kernel's system capsules
are now starshipos.4th, centre.4th, hera.4th and physics.4th, after
forth79.4th.
COLD, after POST, leaves FORTH alone in the search order, so the
prompt reaches STARSHIPOS's words by naming the vocabulary. The ruling
is that init.4th will set the search order; the capsule's header now
says so.
Test first in test_mesh_boot.c: its parity line, and `STARSHIPOS S" ok"
DOE`. It failed before the change. 105 checks now pass, POST is
990/990, and ASan/UBSan and the amd64 build are clean.
Logs are in logs/20261118-starshipos.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
Every stage passes. On all four boots POST is 990/990, with one
dict_hash (0x627f392ccbaa96f1). test-32, the proofs, the images and the
docs pass. The docs stage ran in the background at Captain Bob's ruling.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
The kernel boots the fabric with Hera at place 0. Nodes are born and
killed through her. The fabric is lockstep. Each step walks only the
places that hold a node, and every node ticks on the one adaptive
heartbeat.
Ruled by Captain Bob.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
Every stage passes. On all four boots POST is 990/990, with one
dict_hash (0x627f392ccbaa96f1). aarch64 is inside its 570 s; before
mechanism A it stopped in POST. test-32, the proofs, the images and the
docs pass.
The docs stage runs longer than one foreground command; it ran in the
background at Captain Bob's ruling.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
The fabric keeps its occupied places as a list in ascending order, and
the step's nine passes walk that list in the same order as before. A
place removed mid-walk keeps its link, so the walk goes on to the next
node.
Test first: test_fabric_walk.c, 13 checks.
Every existing fabric and mesh test passes with the same checks, and so
do test-32 and ASan/UBSan. The host mesh boot runs POST 990/990. Over
five alternating runs its median falls from 11.695 s to 7.999 s.
Logs are in logs/20261117-mechanism-a.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
The direct loop before 046ce0be was architecturally incorrect. The fabric
wiring removed it and exposed the slowdowns, and the instruments (ASan,
UBSan, perf) locate them.
FABRIC-3 XLVIII.24 and .25 and both 11-17 plans are corrected in place,
and every measurement is kept. Mechanism A is the first speed-up found,
not a fix.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
FABRIC-3 XLVIII.25 covers the day's work:
- the regression found at 046ce0be (the fabric step walking every place);
- the CI directive and its rulings;
- the fault dump, the diagnose stage and the protocol-report fix;
- the one adaptive heartbeat;
- the protocol on cc09a88b (FAIL: aarch64 stopped in POST);
- next, mechanism A.
XLVIII.24 is corrected in place: its "no measurable cost" was measured
against an already-slow baseline.
The Phase 7 plan's Task 3 tick by execution is marked superseded.
ENGINE.md section 6 records the tick as settled.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm