From 2cc1d27f1919ccb9dd90ab68021fd6f0ad85ce0d Mon Sep 17 00:00:00 2001 From: Robert Allan James Date: Fri, 28 Aug 2026 09:03:50 -0400 Subject: [PATCH] Fix Artemis's own CD-INIT regression, same class as Hermes's Found while auditing messaging capabilities: artemis/init.4th defines its own CD-INIT (block 4141, "Hera calls this at fleet boot") but nothing calls it -- same latent gap as Hermes's CD-INIT (fixed last session), just undiscovered because the earlier check only searched for ART-BOOT-ENTRY, not CD-INIT specifically. ART-BOOT-ENTRY runs unconditionally but never calls CD-INIT internally. Added an unconditional call in the same trailing block that already calls STARTUP-BANNER. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_019ZGkimpfyh63EZyRkNbkPD --- capsules/artemis/init.4th | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/capsules/artemis/init.4th b/capsules/artemis/init.4th index 4fab687..0bcc0b0 100644 --- a/capsules/artemis/init.4th +++ b/capsules/artemis/init.4th @@ -488,6 +488,7 @@ Block 4852 ( workload, for doe-campaign.4th's remote VM-EXEC. ) : LOAD-DOE ( -- ) S" doe.4th" EXEC ; Block 4853 -( D.7: Artemis didn't load lib.4th before; needs it now. ) +( D.7: CD-INIT ran only via the old self-test; birth needs it. ) +CD-INIT S" lib.4th" EXEC STARTUP-BANNER