All FORTH-owned message types were cut over to kernel-Hermes in Phase 3 (tasks 3.8-3.10). This removes the now-dead FORTH messaging layer and the Hermes VM itself: capsules/common/messaging.4th, capsules/hermes/init.4th, the slot-3 VM-NAME-REG pairing convention, and every load-site/birth-site reference across capsules/init.4th, artemis/init.4th, hestia/init.4th, doe-campaign.4th (Artemis-only now), capsule_console.c, capsule_mint.c, capsule_wirebind.c, capsule_birth.c, and kernel_main.c. Verified on all three architectures: clean boot, mkcapsule --lint clean (36 files, 0 violations), zero UNKNOWN WORD, identical dict_hash across amd64/aarch64/riscv64 for every VM, and a full mint -> WIREBIND-attach -> USE -> relay round-trip exercising the two highest-risk edits (capsule_console.c/capsule_mint.c). Found, not fixed: deleting messaging.4th removes SEND-ELEVATE-REQUEST, which was the only caller of KH-ELEVATE-SEND and the only path to ELEVATE-GRANT (zuse-eligibility.4th, still loaded at boot) -- Phase 8 PKI's own elevation entrypoint. Needs a decision before Phase 5 close-out. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
26 lines
699 B
Forth
26 lines
699 B
Forth
Block 2057
|
|
( BOOT-BANNER - LithosAnanke REPL greeting )
|
|
: .SEP ." ================================================" CR ;
|
|
: BOOT-BANNER
|
|
CR .SEP
|
|
." LithosAnanke — FORTH-79 bare-metal kernel" CR
|
|
." Stadium step one: Hera alone" CR
|
|
.SEP
|
|
." Hera [live]" CR
|
|
.SEP CR ;
|
|
Block 2049
|
|
( Hera init — Mama VM personality )
|
|
: VM-TREE ( -- ) ." Hera[0]" CR ;
|
|
: VM-PARENT ( -- id ) 0 ;
|
|
: VM-CHILDREN ( -- ) ." (none)" CR ;
|
|
S" ACL.4th" EXEC
|
|
S" block-acl.4th" EXEC
|
|
S" zuse-eligibility.4th" EXEC
|
|
S" lib.4th" EXEC
|
|
( FABRIC-3.6.md Phase 4, Stage E: common:messaging.4th/ )
|
|
( MSG-CD-INIT removed -- no longer exists, no longer needed. )
|
|
Block 2050
|
|
( Hera boot — banner )
|
|
BOOT-BANNER
|
|
STARTUP-BANNER
|