1 changed files with 23 additions and 0 deletions
@@ -395,6 +395,29 @@ accounts as v3 has them — its Stadium cell by `stadium_words.c`'s rules,
 and the `execution_heat` the ACL reads — taken at the call hook of
 section 1f, which is where a v4 node dispatches a word.

+## 1i. Asking the kernel; Hera as process manager (ruled 2026-10-05)
+
+**v3, as built:** a kernel word is a C function `void f(VM *vm)` registered
+by name (`register_word`); it takes its arguments from the VM's data stack
+and leaves its results there. Some interpret text on the same VM while
+they run (`EXEC`), saving and restoring the interpreter's state around it.
+
+**The v4 design already has the carrier** (`DECOMPOSITION.md` section 6):
+a node's ports are addresses; "a write blocks until the neighbour reads.
+This is the GA144 model. No instruction is added."
+
+**Put to Captain Bob:** a node asks the kernel by a blocking write to a
+port, served between the node's instructions; a kernel word is an ordinary
+dictionary entry whose body stores its request number to the port; kernel
+words are made by handing the node text at boot.
+
+**Ruling:** "Yes, and Hera will be the process manager via compudynamics
+per node."
+
+The second half is recorded as said and is not yet designed. It bears on
+the open question of section 1e — what moves control between nodes, and
+when — which `ENGINE.md` leaves to step 6.
+
 ## 2. Row 3: physics and per-word heat

 ### 2.1 What v3 does