v4 fabric to spec: the mesh boot, the one adaptive heartbeat, mechanism A (#189) #197

Merged
rajames merged 160 commits from StarForth-v4.0.0 into master 2026-11-19 11:19:50 +00:00
Showing only changes of commit 1061433791 - Show all commits
@@ -41,9 +41,10 @@ Written 2026-11-18, from the capsules talk with Captain Bob. It records the ruli
## 3. Open, one at a time
1. ~~The `Block <n>` header~~: ruled above.
2. **The collision check across capsules.** If each capsule is loaded, relocated, interpreted and
then freed before the next, two capsules may use the same numbers. Does the check go, or is it
kept for capsules that are resident together?
2. ~~The collision check across capsules~~ **Ruled: "Overwrite. That's it. Deterministic and
final."** A page written to a block number already in use overwrites it; what was there is gone.
Which write wins follows from the load order, which is fixed, so it is deterministic. A shared
number is not an error, so `mkcapsule`'s cross-capsule collision check (`:846-879`) goes.
3. **The knobs:** which ones set the offset (where the VM's RAM ends), for v3 and for v4. v4's node
has its own block window (`V4_BLOCK_SLOTS`).
4. **Where the pages land before relocation:** in the kernel's block store at `n`, or straight into