Author SHA1 Message Date
Claude 4d64e677f5 v4 text.c: the address record (ADR step 3, task 1)
Build / Image RASPI (push) Successful in 4m13s
Build / Image PC (push) Successful in 3m51s
Build / Image MILKV (push) Successful in 4m30s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 17m32s
Every cell laid down that holds an address of the assembly is recorded,
with its branch slot or 7 for the whole cell, as ARTIFACT.md's
relocations need. Test first: test_text 13 checks failed before.
test_host_rom_nucleus runs with the record on: 1825 branches, 664 whole
cells, the ROM still equal word for word. v4 test, test-32 and
ASan+UBSan pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 17:51:54 +00:00
Claude 29b99f90e6 plans: step 3 §6.6 ruled, mkf18a / .f18a; design ruled
Build / Image RASPI (push) Successful in 4m41s
Build / Image PC (push) Successful in 5m50s
Build / Image MILKV (push) Successful in 6m2s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 15m51s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:33:29 +00:00
Claude 6c639e5d20 plans: step 3 §6.5 ruled, the tool's hash is its source's
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:32:59 +00:00
Claude 3733949c28 ABI.md 2c: a word with no fixed effect stays internal, the build does not fail
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:32:39 +00:00
Claude a6371b1ce3 plans: step 3 §6.4 ruled, every fixed-effect word exported
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:32:21 +00:00
Claude 255dd92deb plans: step 3 §6.3a ruled, the nucleus renamed to name order
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:31:07 +00:00
Claude b5e85392c1 plans: step 3 §6.3 ruled, all it finds, name order
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:30:24 +00:00
Claude 9c8b8dbd8b plans: step 3 §6.2a ruled, the nucleus is not an artifact
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:28:47 +00:00
Claude 4ecdc80197 plans: step 3 §6.2 ruled, both, nucleus first
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:27:31 +00:00
Claude 1961348e15 ARTIFACT.md: relocation slot 7, the whole cell (step 3 §6.1 ruled)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:26:29 +00:00
Claude 16b8fddaef plans: artifacts in the build (ADR step 3), draft for ruling
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:25:39 +00:00
Claude f2174a39a4 ABI.md, ARTIFACT.md: three drafting additions confirmed
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:24:51 +00:00
Claude fe0f709498 ARTIFACT.md: choice 5 ruled, code cells low-first; layout ruled
Build / Image RASPI (push) Successful in 4m17s
Build / Image PC (push) Successful in 5m37s
Build / Image MILKV (push) Successful in 5m40s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 13m56s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:19:58 +00:00
Claude 4a7ca4e288 ARTIFACT.md: choice 4 ruled, port bit plus request list
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:19:00 +00:00
Claude c9cc39f4ec ARTIFACT.md: choice 3 ruled, both stack effects recorded and checked
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:17:11 +00:00
Claude d052af6d53 ARTIFACT.md: choice 2 ruled, SHA-512 for provenance and proofs
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:16:20 +00:00
Claude c4b922d496 ABI.md §4: records in 32-bit units, code in cells, as ARTIFACT.md rules
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:15:13 +00:00
Claude 2b8609e4fc ARTIFACT.md: choice 1 ruled, 32-bit units
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:13:57 +00:00
Claude e43cd63936 ARTIFACT.md: the F18 artifact's layout, draft for ruling (ADR step 2)
Build / Image RASPI (push) Successful in 5m28s
Build / Image PC (push) Successful in 4m15s
Build / Image MILKV (push) Successful in 5m11s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 15m13s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 16:05:50 +00:00
Claude b450c92858 ABI choice 7: safe activation is the first property proved; the ABI v0 contract is ruled
Build / Image RASPI (push) Successful in 5m54s
Build / Image PC (push) Successful in 7m15s
Build / Image MILKV (push) Successful in 6m17s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 14m53s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 15:00:36 +00:00
Claude cb1d6d6790 ABI choice 6: the safe moment is a heartbeat tick at which no P or return stack is inside the old code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:59:24 +00:00
Claude 07f86d94c8 ABI choice 5: callers reach a replacement through a jump written at the old entry
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:58:39 +00:00
Claude 5d9737223b ABI: the rail yard -- the SDK and CI's model for staging trains, recorded as given (Captain Bob)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:57:53 +00:00
Claude bc876f8088 ABI choice 4: imports name the exact build (capsule hash); an update replaces the dependent set together
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:51:53 +00:00
Claude 3b229ba635 ABI choice 3: the engine carries its source by reference (its hash), not as a car
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:51:31 +00:00
Claude 913b74a631 ABI choice 2c: a word with no fixed stack effect cannot be exported; every export has a fixed, derived effect
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:50:48 +00:00
Claude 2957be86e5 ABI: one train per capsule -- an engine of assembled .f18, its named blobs as rolling stock (Captain Bob)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:49:40 +00:00
Claude d46ca3d174 ABI choice 2 reopened: the stack effect is derived by the tool from the compiled code, not declared
Captain Bob withdrew the first answer, the ( -- ) comment, the same day:
it rested on a bad assumption tied to (-, the SDK's marker.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:45:18 +00:00
Claude 1008b442cd ABI choice 2: the stack effect is the ( -- ) comment, read strictly; every export must have one
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:41:53 +00:00
Claude 0c2aab1ab5 ABI choice 1: artifacts come from a host tool, checked cell for cell against the ROM's assembly
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:41:22 +00:00
Claude f8be000b0a ABI.md: the flags cell also has 8, in-line (compile.f18)
Build / Image RASPI (push) Successful in 3m32s
Build / Image PC (push) Successful in 7m23s
Build / Image MILKV (push) Successful in 7m12s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 14m9s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:40:03 +00:00
Claude 5e1dcc197b ABI.md: the F18 ABI, draft contract for ruling (ADR step 1)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:39:53 +00:00
Claude 4f7521290a ADR rulings 4: a word's logical identity is its capsule (content hash) + its name
Build / Image RASPI (push) Successful in 3m42s
Build / Image MILKV (push) Successful in 3m58s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 13m55s
Build / Image PC (push) Successful in 3m57s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:37:55 +00:00
Claude e6addc73b7 ADR rulings 3: Artemis owns persistent memory; run-time memory stays the kernel's
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:37:12 +00:00
Claude 8dd1129ff0 ADR rulings 2: Hermes is the messaging role, not a VM (in v4, the fabric's wires and routing)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:36:24 +00:00
Claude d06a16f869 ADR rulings 1: compiled F18 artifacts allowed beside the ROM ("ADR supersedes"); MACHINE.md 1 and 5 corrected
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:35:47 +00:00
Claude d93e985794 ADR 2026-11-19: F18 binary artifacts, ABI/API and live runtime updates -- recorded as given (Captain Bob)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:34:02 +00:00
Claude 7af88cc704 v4 ACL: the countdown at call, as v3 -- the call hook may redirect
Build / Image PC (push) Successful in 6m13s
Build / Image MILKV (push) Successful in 6m40s
Build / v4 tests (32- and 64-bit cells) (push) Successful in 14m18s
Build / Image RASPI (push) Successful in 3m11s
Captain Bob ruled "As v3: add at call", "Engine: call redirects" and
"Build it".
- The engine's call hook returns where P goes.
- The kernel checks every call from code defined at run time. A TTL is
  counted down at the call. At a TTL of 0, or a denied word, the call is
  sent to (ACL-CALL), with the target on the data stack, which rechecks
  or refuses it by the word's own name, then goes on to it.
- A word being compiled is no longer checked, as in v3.

Two things were added while building, both from v3:
- (ACL-BUSY) turns the check off while the policy rechecks. Without it
  the recheck recursed.
- (ACL-CALL) does its own refusal and leaves WORD's buffer alone. A first
  version broke POST's CONVERT.digits.

Test first: test_mesh_boot's five new checks failed before; now 120 pass
and POST is 990/990. test_exec tests the redirect. test_host_quit's two
v4-only expectations now follow v3: a denied word compiles.

All 52 tests, test-32 and ASan/UBSan pass. An amd64 session passes 18/18.
Five alternating host boots: +1.4% median, inside the noise.
DECOMPOSITION.md 5.20 is updated, and the FPGA's call opcode is recorded
as owing the same redirect.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 14:10:16 +00:00
Claude 666cf39b8b plan: the ACL countdown at call -- design, for ruling (the call hook may redirect)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 13:17:32 +00:00
Claude 9e737b6252 v4 init.4th pins the words that create or end nodes
Captain Bob ruled: "Also pin the kernel words". After the policy loads,
init.4th pins 11 words: BIRTH, BIRTH-AS, UNIT, KILL, UNIT-KILL, PAUSE,
RESUME, NODE-BORN, NODE-KILL, NODE-SLEEP and NODE-WAKE. Their fields
cannot be changed, so no policy can deny them. v4 has no CAPSULE-BIRTH.
The wiring words, NODE-WIRE and NODE-UNWIRE, are not pinned; they
neither create nor end a node.

Test first in test_mesh_boot: each of the 11 is pinned. The before-run
had all 11 unpinned. After: 114 checks pass, POST 990/990.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 12:00:23 +00:00
Claude 04f917f005 logs: the amd64 session with init.4th and the ACL on (18/18), the serial log for logs/20261119-init-acl/amd64-session.txt
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 11:57:54 +00:00
Claude b13d452e66 v4 init.4th, steps 1 and 2: the ACL policy loaded after POST, then the search order
Captain Bob ruled "ACL at boot", loaded "From init.4th", the include
"Compose[d] in FORTH".
- capsules/v4/init.4th, at block 3980: S" v4:ACL.4th" CAPSULE-INCLUDE,
  then STARSHIPOS.
- capsules/v4/ACL.4th is the policy, git mv'ed from v4/capsule/ACL.fth
  and reflowed into chained 64x16 blocks, its text unchanged.
- CAPSULE-INCLUDE in centre.4th places a capsule and LOADs its lowest
  block. It is composed from CAPSULE-OPEN and CAPSULE-LINE, with no new
  C word.
- The mesh loads v4:init.4th after POST and COLD, its one fixed step
  there.

Test first in test_mesh_boot: the parity line, DOE without naming
STARSHIPOS, and ACL-BOOT pinned. The before-run failed.

After: 113 checks pass and POST is 990/990. All 52 tests, test-32 and
ASan/UBSan pass. The dictionary has 405 words. One amd64 session passes
18/18 with "ACL: active".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
2026-11-19 11:57:42 +00:00
64 changed files with 5466 additions and 109 deletions
+60
View File
@@ -0,0 +1,60 @@
Block 3984
\ ACL.4th -- word-level access control: the policy.
\ v3's capsules/ACL.4th, as FORTH source the node compiles.
\ The capsule supplies an entry's fields and the check
\ (acl.f18, compile.f18); what is strict, how long a TTL
\ lasts and what is pinned is decided here. Loading it
\ switches access control on: its last line runs ACL-BOOT.
\ A system that does not load it has none. init.4th loads
\ it after POST (MACHINE.md 1.1: the init turns on security).
\ The xt these words take is what FIND and ['] give.
FORTH DEFINITIONS
1 CONSTANT ACL-STRICT-MODE
0 CONSTANT ACL-TTL-MODE-VAL
\ the TTL of a cold word, tuned 2026-06-15 on v3
256 CONSTANT ACL-BASE-TTL
65535 CONSTANT ACL-MAX-TTL
-->
Block 3985
\ ( xt -- xt ) for symmetry: the xt is the entry
: ACL-ENTRY ;
: ACL-STRICT ( xt -- )
DUP ACL-PINNED? IF DROP EXIT THEN
ACL-STRICT-MODE SWAP ACL-MODE! ;
: ACL-TTL-MODE ( xt -- )
DUP ACL-PINNED? IF DROP EXIT THEN
ACL-TTL-MODE-VAL SWAP ACL-MODE! ;
\ ( xt -- ttl ) a hotter word earns a longer TTL:
\ heat/4 + 256, at most 65535
: ACL-TTL-COMPUTE
ACL-HEAT@ 4 / ACL-BASE-TTL + ACL-MAX-TTL MIN ;
-->
Block 3986
\ ( xt -- ) what the check runs when a word's TTL is 0.
\ STRICT: allow, and leave the TTL 0 so that every use
\ comes back here. TTL: compute a TTL from the word's
\ heat; allow.
: ACL-RECHECK
DUP ACL-PINNED? IF DROP EXIT THEN
DUP ACL-MODE@ ACL-STRICT-MODE = IF
1 OVER ACL-ALLOW! 0 OVER ACL-TTL! DROP EXIT
THEN
DUP ACL-TTL-COMPUTE OVER ACL-TTL! 1 SWAP ACL-ALLOW! ;
\ the system CA's public key; placeholders, as in v3
0 CONSTANT ACL-CA-KEY-LO
0 CONSTANT ACL-CA-KEY-HI
-->
Block 3987
\ ( req-hi req-lo -- allow? ) the fabric asks this word
\ whether a channel may be opened. The default approves
\ every request; a policy edits this.
: HERMES-CHANNEL-OPEN? 2DROP 1 ;
\ ( -- ) default fields on every word; the words that
\ enforce the policy pinned; the recheck switched on
: ACL-BOOT
ACL-INIT-PRIMITIVES
['] ACL-RECHECK ACL-PIN ['] ACL-INIT-PRIMITIVES ACL-PIN
['] ACL-RECHECK ACL-HOOK !
LOG-INFO" ACL: active" ;
' ACL-BOOT ACL-PIN
ACL-BOOT
+5
View File
@@ -38,6 +38,11 @@ Block 3966
: (LINES) ( baddr u -- ) CAPSULE-OPEN 0= IF (FAIL) THEN
BEGIN PAD CAPSULE-LINE DUP 0< 0= WHILE PAD SWAP (TELL) REPEAT
DROP ;
( a capsule of FORTH blocks into this node: its lowest LOADed )
: CAPSULE-INCLUDE ( baddr u -- )
CAPSULE-OPEN 0= IF -1 NODE-ERROR ! EXIT THEN
PAD CAPSULE-LINE 0< IF EXIT THEN
0 0 PAD 1- CONVERT DROP DROP LOAD ;
-->
Block 3967
( Who it is, where its printing goes, which of its ports )
+16
View File
@@ -0,0 +1,16 @@
Block 3980
( init.4th -- the system's init, run after POST and COLD. )
( MACHINE.md 1.1 and 3, step 5: everything after POST is )
( init.4th's. docs/v4.0.0/plans/2026-11-18-v4-init.md. )
( Step 2, security on: the ACL policy, ACL.4th. )
S" v4:ACL.4th" CAPSULE-INCLUDE
( The words that create or end nodes, pinned: their fields )
( cannot be changed, so no policy can deny them. )
' BIRTH ACL-PIN ' BIRTH-AS ACL-PIN ' UNIT ACL-PIN
' KILL ACL-PIN ' UNIT-KILL ACL-PIN
' PAUSE ACL-PIN ' RESUME ACL-PIN
' NODE-BORN ACL-PIN ' NODE-KILL ACL-PIN
' NODE-SLEEP ACL-PIN ' NODE-WAKE ACL-PIN
( Step 1, the search order: STARSHIPOS, then FORTH. Last, )
( since ACL.4th ends in FORTH DEFINITIONS. )
STARSHIPOS
+22
View File
@@ -81,3 +81,25 @@ set HDR-NFA here ", ACL-HEAT@ #id, #, 0 #, HDR-NFA #, HDR-LINK set HDR-LIN
\ ( xt -- n ) a number for the word that never changes: its address
set HDR-NFA here ", ACL-WORD-ID #id, #, 0 #, HDR-NFA #, HDR-LINK set HDR-LINK here
: ACL-WORD-ID (ACL-XT) ;
\ ( xt -- ) a call from code defined at run time that the kernel sent here
\ (v4/system/mesh.c, on_call) because the word's TTL is 0 or it is denied.
\ As v3's inner interpreter, and as (ACL?): the recheck, or the TTL counted
\ down; then a denied word refused with v3's line -- by its own name, from
\ its entry (WORD's buffer is the running code's, not this) -- the stack
\ emptied and the line ended; an allowed word is jumped to, so it returns to
\ the caller as the call would have (docs/v4.0.0/plans/2026-11-19-acl-at-call.md).
: (ACL-CALL)
dup -3 + a! @ \ xt flags
dup $FFFF0000 and if ZERO
drop -65536 + ! jump TEST \ one use fewer
ZERO: drop drop dup (ACL-RECHECK)
TEST: dup -3 + a! @ 32 and if OK
drop
$33335B1B (EMIT4) $6D (EMIT4) $4E524157 (EMIT4) $203A (EMIT4) $6D305B1B (EMIT4) \ v3's line: WARN: in yellow
$3A4C4341 (EMIT4) $6E656420 (EMIT4) $20646569 (EMIT4) $27 (EMIT4)
-2 + a! @ 4* COUNT TYPE 39 EMIT CR \ the word's own name
DSTACK-DEPTH b! a !b \ as v3, the stack is emptied
pop drop jump (ABANDON)
OK: drop push ; \ on to the word
+16 -13
View File
@@ -113,22 +113,25 @@ macro ROT push SWAP pop SWAP endmacro
\ bits 16 .. 31 the TTL, a count of uses left before the next recheck
\ A new entry has all of them zero: allowed, not pinned, TTL mode, TTL 0.
\
\ (ACL?) is run by INTERPRET for every word it is about to execute or
\ compile. As v3: if the TTL is 0 the word is rechecked, otherwise the TTL
\ is counted down; then a denied word is refused. The recheck is the word
\ whose address is in (ACL-HOOK) -- ACL-RECHECK, once ACL.fth has loaded --
\ and with none there the word is allowed and given the longest TTL.
\ (ACL?) is run by INTERPRET for every word it is about to execute. As v3:
\ if the TTL is 0 the word is rechecked, otherwise the TTL is counted down;
\ then a denied word is refused. The recheck is the word whose address is in
\ (ACL-HOOK) -- ACL-RECHECK, once ACL.4th has loaded -- and with none there the
\ word is allowed and given the longest TTL.
\
\ v3 checks every execution, inside definitions too. v4 code is native: a
\ compiled call goes straight to its word. So v4 checks a word when it is
\ compiled as well as when it is interpreted -- a denied word cannot be
\ built into anything new -- but a call compiled while the word was allowed
\ is not checked again.
\ As v3, every execution is checked, inside definitions too (2026-11-19,
\ docs/v4.0.0/plans/2026-11-19-acl-at-call.md): a call from code defined at
\ run time is checked by the kernel at the call -- counted down there, or,
\ at a TTL of 0 or a denied word, sent to (ACL-CALL) (acl.f18), which runs
\ (ACL?). A word being compiled is not checked, as in v3. While the policy
\ rechecks a word, (ACL-BUSY) is 1 and the kernel checks nothing, as v3 runs
\ its policy with the check off.
\ ( xt -- ) recheck
: (ACL-RECHECK)
(ACL-HOOK) a! @ if NONE push ex \ call it with the xt
;
(ACL-HOOK) a! @ if NONE
1 (ACL-BUSY) a! ! push ex \ call it with the xt, the kernel's check off
0 (ACL-BUSY) a! ! ;
NONE: drop -3 + a! @ 65535 and -33 and $FFFF0000 + ! ;
\ ( xt -- xt ) as above; a denied word ends the line
@@ -202,7 +205,7 @@ set HDR-NFA here ", INTERPRET #id, #, 0 #, HDR-NFA #, HDR-LINK set HDR-LIN
STATE a! @ if INTERP
drop 1 and if COMP \ compiling: immediate words still run
drop (ACL?) jump (GO)
COMP: drop (ACL?) (COMPILE,) jump (IL)
COMP: drop (COMPILE,) jump (IL) \ compiled, not checked: the call is, when it runs (as v3)
INTERP: drop 16 and if RUN
drop drop (.WORD) \ ": compile-only"
$6F63203A (EMIT4) $6C69706D (EMIT4) $6E6F2D65 (EMIT4) $796C (EMIT4) CR
+4
View File
@@ -35,5 +35,9 @@ store (IMG) &(IDLE)
store (IMG)+1 &(FAULTS)
store (IMG)+2 &KEY
store (IMG)+3 &CR
\ the ACL's check at call: where the kernel sends a call to be checked; and the
\ policy not running
store (ACL-CALLX) &(ACL-CALL)
store (ACL-BUSY) 0
start (IDLE)
+2
View File
@@ -120,6 +120,8 @@ constant RSTACK-DEPTH 32752
constant HEAT-OP 29216
constant (EXEC) 30047
constant (RUNX) 29954
constant (ACL-CALLX) 29956
constant (ACL-BUSY) 29925
constant ANTICLOCK 29248
constant CFBASE 32672
constant CFEND 32704
+2
View File
@@ -120,6 +120,8 @@ constant RSTACK-DEPTH 32752
constant HEAT-OP 29216
constant (EXEC) 30047
constant (RUNX) 29954
constant (ACL-CALLX) 29956
constant (ACL-BUSY) 29925
constant ANTICLOCK 29248
constant CFBASE 32672
constant CFEND 32704
+1
View File
@@ -389,6 +389,7 @@ BIRTH-AS ( number port childport baddr u -- place ) BIRTH, and given the capsule
CAPSULE-CELL ( -- w flag ) The next cell of the capsule of F18 code this node has open, and true; 0 0 at its end. A kernel request.
CAPSULE-LINE ( baddr -- u | -1 ) The next line of the capsule of FORTH blocks this node has open, copied to baddr: its length, or -1 at its end. A kernel request.
CAPSULE-OPEN ( baddr u -- flag ) Find the named capsule, check its hash and signature, and open it to be read from its start by this node. A kernel request.
CAPSULE-INCLUDE ( baddr u -- ) Load the named capsule of FORTH blocks into this node: CAPSULE-OPEN places its blocks in RAM, block n at n - R, and its lowest block is LOADed; what runs after it is the capsule's own (-->, LOAD, THRU). init.4th loads the ACL policy so. centre.4th.
CENTRE ( n -- ) Hera only: a second centre, node n, from its port 6 to Hera's port 6, given centre.4th; it births its own unit, n+1 to n+4.
KILL ( n -- ) Hera only: node n is removed, whatever it was doing; every node is told it is gone, and Hera forgets the way to it.
NODE-BORN ( number -- place | -1 ) A node is born, empty, and entered in the registry with this node as its parent: its place, or -1 if there is no room. A kernel request.
Can't render this file because it contains an unexpected character in line 11 and column 3.
+203
View File
@@ -0,0 +1,203 @@
# The F18 ABI -- draft contract, for ruling
Written 2026-11-19. Step 1 of `ADR-2026-11-19-F18-ARTIFACTS.md` §7: "Define and document the minimal ABI
contract". It builds on the rulings in `plans/2026-11-19-f18-artifacts.md`:
1. compiled artifacts are allowed beside the ROM;
2. Hermes is the messaging role;
3. Artemis owns persistent memory;
4. a word's identity is its capsule plus its name.
**Nothing here is built.** The choices left open are numbered in §9, and each will be put to Captain Bob on
its own.
## 1. Terms
| Term | Meaning |
|---|---|
| **Word** | The unit of interface and access control (ADR §1). It has a name, an entry point, a stack effect and its ACL fields. |
| **Capsule: a train** | The unit of packaging, distribution and deployment (ADR §1). It is content-addressed, so its ID is its hash, and it is signed, as now (`kernel/include/starkernel/capsule.h`). **Ruled 2026-11-19, "One train per capsule":** each capsule is a train. Its *engine* is its `.f18` code, assembled by the host tool into one artifact. Its *rolling stock* is the named blobs coupled behind the engine: `.4th` source, data, and whatever else it carries, each with its own identity and provenance. A system is many trains; the nucleus is one of them. |
| **Artifact: the engine** | A train's compiled F18 unit: code cells, and the records of §4 that make them placeable and checkable. It is assembled from all of that capsule's `.f18` files. |
| **Rolling stock** | The named blobs behind an engine (MACHINE.md §1's trailer). The engine's code is what acts on them: the ROM's types, `.f18` assembled and `.4th` handed a line at a time, now carried by each train. |
| **Identity** | Ruling 4: a word's identity is (the hash of the capsule that defines it, the word's name). Addresses, word IDs and places are local resolution only. |
| **Loader** | Whoever places an artifact in a node. As today, that is the node itself, through words like `CAPSULE-INCLUDE`, or the kernel at boot. No central linker (ADR §6). |
## 2. The hardware contract (unchanged; kept apart, ADR §3.2)
The engine's contract is what it is today, and the ABI does not change it:
- **Instruction words** of six slots (`v4/include/v4/iword.h`). A branch (`jump`, `call`, `next`, `if`,
`-if`) carries its target in the bits to the right of its slot, page-relative, with a reach of 27, 22, 17
or 12 bits.
- **The return stack and the data stack** are rings, with their depths set by the build (`V4_DATA_RING`,
`V4_RET_RING`). A call pushes its return address.
- **Ports and messages** between nodes, as MESH.md has them. The ABI adds nothing between nodes: "inter-core
communication shall continue to use the established message architecture" (ADR §3.2).
- **The call hook** (2026-11-19, `exec.h`) may redirect a call. The ACL uses it now; §6 may use it.
**What this means for artifacts:** compiled code holds addresses in its branch fields. An artifact placed
anywhere but where it was compiled needs those fields fixed (§5).
## 3. The word contract
**The entry** is as `dict.f18` has it today:
| Cell | Holds |
|---|---|
| `xt - 4` | the word ID, local |
| `xt - 3` | the flags: 1 immediate, 2 hidden, 4 data, 8 in-line, 16 compile-only, 128 deferred, plus the ACL fields (bit 5 denied, bit 6 pinned, bits 8–15 the mode, bits 16–31 the TTL) |
| `xt - 2` | the name |
| `xt - 1` | the link |
| `xt` | the code |
**What the ABI adds is recorded, not run.** Each exported word has:
- **its stack effect:** how many cells it takes and leaves on each stack. This is the "stack effects" of
ADR §3.2. It is derived by the host tool from the compiled code (choice 2), checked when the artifact is
placed and in the proofs, never at run time.
- **its capabilities:** the kernel requests it may make (`KERNEL-WORD` numbers) and whether it touches ports.
- **its ACL defaults:** pinned or not, and its mode. They are applied at placement, through the same fields.
**The calling convention:** a call with a return address on the return stack, as now. A word returns with
`;`. Arguments and results travel on the data stack only, in the declared counts. There is nothing else.
## 4. The artifact
**The records are in 32-bit units, low byte first, and the code is in the build's cells** (`ARTIFACT.md`
§1, ruled 2026-11-19, "32-bit units"). A node reads the records as it reads a block, four bytes to a
cell. *Corrected 2026-11-19: this line said "All of it is in cells, so an F18 node can read it".*
| Record | Holds |
|---|---|
| **Header** | a magic number; the ABI version; the cell width (32 or 64); the record counts |
| **Provenance** (ADR §3.1) | the source capsule's hash; the compiler's identity (the host tool's hash, choice 1); the build configuration's hash (the knobs, `V4_NODE_WORDS`, the rings); the target |
| **Exports** | for each word: its name, its entry's offset in the code, its flags, its declared stack effect, its capabilities |
| **Imports** | for each word used from another capsule: (that capsule's hash, the name), and the stack effect it is expected to have |
| **Relocations** | every cell of the code whose branch field holds an address, with how to fix it: internal (add the base), or import *k* |
| **Code** | the compiled cells, as if placed at address 0 |
| **Verification** | the identity of the proof that covers this exact artifact, and the assumptions it holds under (ADR §5), or none |
**Integrity and authorship** are the capsule's: its content hash and its Ed25519 signature, as now. The
artifact repeats neither, and, as ADR §5 says, a hash is not correctness.
## 5. Placement: resolution without a linker
A loader places an artifact in one pass, in order:
1. **Check:**
- the header is one this ABI version and cell width take;
- the capsule's hash and signature check, as `CAPSULE-OPEN` already does;
- every import's capsule is present in this node, and the imported word is exported by it with the
stack effect expected. **Fail closed:** if any check fails, nothing is placed.
2. **Place:** the code cells are copied to the node's dictionary space at its `HERE`, the base.
3. **Fix:** each relocation's branch field is patched, adding the base, or putting in the import's
resolved address. A field whose patched address does not fit its slot's reach is refused (fail
closed). Patching happens at placement only, once, with no lazy binding and no later resolution.
4. **Enter:** an entry is made for each export, as `(HEADER)` makes one, and the kernel is told
(`(WORD-DEFINED)`). The word accounts, the ACL fields and the defaults of §3 apply from here.
This is the work FORTH's compiler already does when it compiles a reference to a word. It is done here
from records, not from source. It is not dynamic linking in the ADR's sense: there are no shared libraries,
no lazy binding, no global address space and no linker running beside the program.
## 6. Activation and retirement (ADR §4)
**A replacement** is a newer capsule exporting a word of the same name. Its identity differs, because its
capsule hash differs. Activation must make the code that calls the old word reach the new one. The call
sites compiled into other definitions hold the old address (§2). Choice 5 is how they reach it.
**A safe boundary** is a heartbeat at which no node is inside the old word: no return address into it is
on any return stack, and no message for it is waiting. Choice 6 is how that is known.
**Retirement:** the old code is freed only when nothing can reach it. Until then both versions coexist
(ADR §4).
**Rollback** is activating the old one again, as long as it is not retired. Artemis keeps the staged and
recovery copies (ruling 3).
## 7. Compatibility
**A replacement is compatible** when, for every word the old artifact exported:
- the new one exports a word of the same name;
- with the same stack effect;
- needing no capability the old did not.
Anything else is incompatible, and activation is refused. A verified artifact is not compatible because it
is verified (ADR §5); compatibility is checked against the old artifact's records.
## 8. What stays as it is
- POST, the protocol, and CI's gates (ADR §7).
- Source capsules and the boot as it is: the ROM still assembles the system at boot (ruling 1).
- The ACL's check at call, and the word accounts: an artifact's words are words like any other.
- Messages between nodes.
**Captain Bob's image, 2026-11-19:** "the .f18 assembler assembles all .f18 files it finds. Now here's a
thought. That 'assembled' code can be the 'engine' for a train of named blobs as metaphorically rolling
stock." Ruled "One train per capsule" (§1).
**The rail yard: the SDK and CI's model** (Captain Bob, 2026-11-19, recorded as given; nothing built):
> "When we build the SDK, we can naturally think of a railroad yard for staging outgoing artifact capsule
> 'trains' from first order preexisting 'cars' prior to writing new ones.. That would be the model and on
> the CI side we can use messaging as semaphores in our staging yard with inbound and outbound trains and
> the artifacts are the persistent part. Signed, sealed and versioned."
Read here as:
- **The yard stages trains.** An outgoing train is made up first from cars that already exist, which are
first-order and already built. New cars are written only for what is missing.
- **In CI, messages are the semaphores.** They signal inbound and outbound trains through the yard: what
may move, and when.
- **What persists is the artifacts:** signed, sealed and versioned. The yard's moves are transient.
It ties in `(-`, the build marker that asks CI to clear a block for the next image (`plans/2026-11-18-
capsule-blocks.md` §5), and Artemis keeping what is kept (ruling 3).
## 9. Open, for ruling one at a time
1. ~~Where artifacts come from~~ **Ruled 2026-11-19: "A host tool".** A C tool beside `mkcapsule` compiles
`.f18` to artifacts on the build machine. It is a second assembler beside the ROM's, so the two must
agree: the tool's output is checked against what the ROM assembles from the same source, cell for cell,
in the build and in CI. The compiler's identity in the provenance record is the tool's own hash.
The cell-for-cell check was added in drafting; confirmed by Captain Bob, 2026-11-19 ("Yes").
2. ~~The stack-effect declaration~~ **Ruled 2026-11-19: "Derived by the tool".**
- A first answer, "the ( -- ) comment, strict", was withdrawn the same day. Captain Bob: "I think I may
have made a bad assumption. I had the idea of that after (- was aliased to ( is for SDK special. We're
working on something more fundamental."
- **There is no declaration in the source.** The host tool computes each exported word's stack effect
from its compiled code, by static analysis of the F18 opcodes, and records it in the artifact. The
proofs check it. Comments stay comments.
- **2c, ruled 2026-11-19: "Refused as an export".** A word whose effect depends on its data (a loop
leaving a count of values, branches that leave different depths, `EXECUTE`, a `DEFER`red word) has no
fixed count. It cannot be exported by an engine: it stays internal to its train, or is restructured.
Every export has a fixed effect, derived by the tool; a word with none stays internal, and the build
does not fail for it (`plans/2026-11-19-f18-artifact-build.md` §6.4). *Corrected 2026-11-19: this
said "which the tool derives and the build fails without".*
3. ~~What a capsule carries~~ **Ruled 2026-11-19: "No, by reference".** A train's engine carries only the
hash of the `.f18` source it was assembled from, in its provenance record. The source stays in the
repository and in its own capsule. To check an engine against its source, the source is fetched by
that hash.
4. ~~Imports by capsule hash~~ **Ruled 2026-11-19: "Exact hash".** An import names the exact build of
the train it imports from: (its capsule hash, the word's name). If that train is rebuilt or updated,
its hash changes, so its importers are rebuilt too, and a live update replaces the whole dependent set
of trains together. Placement refuses an import whose hash is not present.
5. ~~How callers reach a replacement~~ **Ruled 2026-11-19: "Jump at the old entry".** At activation, each
replaced word's first code cell, at its xt, is overwritten with a `jump` to the new word: one cell per
word, and every caller, compiled at run time or not, follows at once. The old code stays in place,
unreachable but for that cell, until it is retired. The new word must be within the jump's reach from
the old entry (27 bits in slot 0, which covers a node's memory), or activation is refused.
6. ~~The safe boundary~~ **Ruled 2026-11-19: "Scan at a heartbeat".** At a heartbeat tick the kernel
scans every node's P and return stack for an address inside the old words' code. When none is there, it
writes all of a set's jumps in that one tick. While some are there, it tries again on later ticks. A
message waiting for an old word is not code on a stack and does not hold the set back: the word it
reaches is the new one. That last point was added in drafting; confirmed by Captain Bob, 2026-11-19
("Yes").
7. ~~Proofs first~~ **Ruled 2026-11-19: "Safe activation first".** The first Isabelle/HOL property:
- the jump at each old entry is written only at a tick when no node's P or return stack holds an address
inside the old code (choice 6);
- after it, every call to an old word, from any caller, reaches the new word.
Placement's checks, compatibility and the soundness of the derived stack effects come after.
## 10. Status
All seven choices are ruled, plus 2c (no fixed effect means no export). This draft is the minimal ABI
contract, the ADR's step 1, as ruled.
The next step is the ADR's step 2, the artifact representation in detail: the exact cell layout of §4's
records, a design for ruling before any code.
+181
View File
@@ -0,0 +1,181 @@
# StarshipOS Architectural Design Decision
<!-- Recorded verbatim as given by Captain Bob, 2026-11-19. The conflicts it raises with the existing record
are put to him one at a time, and ruled in docs/v4.0.0/plans/2026-11-19-f18-artifacts.md. -->
## F18 Binary Artifacts, ABI/API, and Live Runtime Updates
Status: ACCEPTED — Immediate Design Decision
Date: 2026-11-19
Scope: F18 build system, LithosAnanke, StarshipOS runtime
Priority: Architectural foundation
---
### 1. Decision
StarshipOS shall establish a canonical binary artifact format for compiled F18 code, supported by a minimal, formally specified Application Binary Interface (ABI) and Application Programming Interface (API).
The ABI shall operate at the word and capsule levels:
- Words are the units of interface and access control.
- Capsules are the units of packaging, distribution, and deployment.
The implementation shall preserve the existing StarshipOS architecture without introducing conventional dynamic linking, shared-library infrastructure, or unnecessary runtime machinery.
### 2. Motivation
This decision supports four primary objectives:
1. Performance: Eliminate redundant compilation, dependency resolution, and other avoidable work from build and startup paths.
2. Verification: Provide immutable binary artifacts suitable for Isabelle/HOL verification and reproducible-build validation.
3. Authenticity and provenance: Establish traceability between source, build configuration, compiler, binary artifact, and formal verification evidence.
4. Live updates: Permit verified binary components to be staged and activated within a running StarshipOS instance without requiring a complete system restart.
Performance improvements must be measured. Binary artifact creation alone does not guarantee reduced startup latency.
### 3. Architectural Contract
#### 3.1 F18 Binary Artifacts
The build system shall compile F18 source into a canonical, versioned binary artifact representation.
An artifact shall provide sufficient information to establish:
- Artifact identity and integrity.
- Source and build provenance.
- Target architecture and compatibility constraints.
- Exported and imported word identities.
- Word-level interface contracts.
- Dependencies and required capabilities.
- Verification status and associated proof identity.
The format may contain individually addressable compiled units.
Artifacts shall remain independent of final deployment decisions. A compiled unit may be incorporated into kernel ROM or distributed as a runtime-consumable capsule.
Source files, compiled binaries, and supporting documentation shall retain their individual provenance.
#### 3.2 Application Binary Interface (ABI)
The ABI shall define the minimum binary-level contract necessary for independently compiled components to interoperate.
It shall address:
- Word identity and resolution.
- Calling conventions and stack effects.
- Memory ownership and access constraints.
- Entry points and dependencies.
- Capability and ACL requirements.
- Binary compatibility.
- Activation and retirement semantics.
The F18 hardware execution contract and the StarshipOS artifact interoperability contract shall remain conceptually distinct.
Logical word identity shall not depend on physical memory addresses or processor placement.
Local execution may resolve to physical addresses. Inter-core communication shall continue to use the established message architecture.
#### 3.3 Application Programming Interface (API)
The API shall expose the minimum operations necessary for artifact discovery, verification, staging, activation, retirement, and recovery.
These operations should be implemented through existing StarshipOS facilities wherever practical.
They shall not automatically require new kernel primitives.
The API shall preserve the existing responsibilities of:
- Hera: System ownership, component creation, and coordination.
- Hermes: Messaging, routing, and communication.
<!-- Ruled 2026-11-19 ("The messaging role"): Hermes names the role, not a VM. In v4 it is the fabric's wires
and routing (MESH.md), and kernel-Hermes on v3; no Hermes node is brought back. -->
- Artemis: Memory, persistence, and recovery.
<!-- Ruled 2026-11-19 ("Persistent memory"): Artemis owns what is kept -- persistent storage, staged artifacts,
recovery copies (FABRIC-3.5 XIV.3). Run-time memory stays the kernel's: the Stadium allocates it, and the
kernel serves blocks. -->
Specific API word names and signatures remain implementation decisions.
### 4. Live Runtime Updates
StarshipOS shall support the architectural capability to introduce verified replacement artifacts into a running system.
The intended lifecycle is:
1. Build the replacement artifact.
2. Verify integrity, compatibility, and applicable formal properties.
3. Distribute and stage the artifact.
4. Establish a safe activation boundary.
5. Activate the replacement.
6. Retire the previous implementation when safe.
7. Preserve recovery or rollback capability where applicable.
Heartbeat boundaries may provide logical activation points, but safe replacement must account for outstanding execution, messages, dependencies, and persistent state.
Multiple artifact versions may coexist during transitions.
Live replacement shall not violate existing runtime invariants or word-level ACL guarantees.
### 5. Formal Verification
The ABI and artifact format shall be suitable for specification in Isabelle/HOL.
Verification objectives include:
- Artifact structural validity.
- Interface and stack-effect compatibility.
- Dependency satisfaction.
- Memory and capability constraints.
- Safe activation and retirement.
- Preservation of established invariants across compatible replacements.
Proof evidence shall be associated with the exact artifact and its applicable assumptions.
Cryptographic integrity and authenticity shall be distinguished from functional correctness. Hashes alone do not establish correctness or authorship.
A verified replacement shall not be considered universally compatible merely because its individual components have been verified.
### 6. Explicit Non-Goals
This decision does not authorize introducing:
- ELF-style dynamic linking or shared libraries.
- A conventional process loader.
- A centralized runtime linker.
- A global executable address space.
- A conventional scheduler or memory manager.
- A new execution model.
- Mandatory inclusion of all compiled artifacts in kernel ROM.
- Unnecessary kernel primitives or additional abstraction layers.
The existing asynchronous, message-driven architecture remains authoritative.
### 7. Implementation Direction
Implementation shall proceed incrementally:
1. Define and document the minimal ABI contract.
2. Establish the canonical binary artifact representation.
3. Integrate artifact production into the existing build system.
4. Add integrity, provenance, and reproducibility checks.
5. Formalize applicable ABI properties in Isabelle/HOL.
6. Implement minimal artifact API operations.
7. Validate staged and live replacement using controlled experiments.
8. Measure build time, startup latency, runtime overhead, and replacement correctness.
Existing build, POST, CI, and verification gates shall remain in force unless explicitly superseded by independently validated equivalents.
### 8. Governing Principle
Words define interfaces. Capsules define deployment. Artifacts establish identity and provenance. The ABI guarantees interoperability. The API exposes operations. Isabelle/HOL verifies the applicable contracts.
No additional machinery shall be introduced without demonstrated necessity.
The machine remains the machine.
---
Decision: ACCEPTED
Implementation: Pending incremental design and experimental validation
Architectural impact: Foundational — F18 toolchain, capsule infrastructure, formal verification, and live deployment.
+155
View File
@@ -0,0 +1,155 @@
# The F18 artifact -- its layout, draft for ruling
Written 2026-11-19. Step 2 of `ADR-2026-11-19-F18-ARTIFACTS.md` §7, "Establish the canonical binary
artifact representation". It gives the exact layout of the records `ABI.md` §4 lists, under ABI v0 as
ruled:
- one train per capsule;
- a host tool assembles all of a capsule's `.f18` into its engine;
- each export's stack effect is derived, and a word with none fixed is not exported;
- imports name the exact build;
- the source travels by reference.
**Nothing here is built.** The choices in §8 are ruled (2026-11-19).
## 1. Units, order, width
- **The unit is a 32-bit word**, stored little-endian, low byte first, as v4's blocks are (`blocks.h`:
"four bytes to a cell, the first lowest"). Every record is a whole number of units, so the records read
the same at either cell width.
- **The code is cells of the build's width**, each stored low byte first (choice 5). A 32-bit engine and a 64-bit engine are two artifacts: the
header says which, and placement refuses the wrong one.
- **A 64-bit value**, such as a capsule's hash, is two units, low unit first.
- **A SHA-512 hash** (choice 2) is 16 units: its 64 bytes in their order, packed four to a unit, low byte
first.
- **A name** is a counted string, its length byte then its characters, packed four to a unit, low byte
first, as the dictionary packs names (`dict.f18`). It sits in the string pool and is referred to by its
unit offset.
## 2. The whole
```
header 16 units
provenance 64 units
exports E x 8 units
imports I x 6 units
relocations R x 2 units
verification 18 units
string pool S units
code C cells
```
The offsets of each part are in the header, so a reader skips what it does not need. The artifact is the
engine of a train: the capsule's payload. The capsule's content hash and Ed25519 signature, already
`mkcapsule`'s, cover it whole. The artifact repeats neither.
## 3. Header (16 units)
| Unit | Field |
|---|---|
| 0 | magic `F18A` (`0x41383146`) |
| 1 | ABI version: 0 |
| 2 | cell width in bits: 32 or 64 |
| 3 | the node words it was built for (`V4_NODE_WORDS`) |
| 4–5 | E, the export count; I, the import count |
| 6–7 | R, the relocation count; S, the string pool's units |
| 8 | C, the code's cells |
| 9 | the unit offset of the exports (the others follow, in §2's order) |
| 10–15 | reserved, 0 |
## 4. Provenance (64 units, ADR §3.1)
Each hash is SHA-512 (choice 2).
| Units | Field |
|---|---|
| 0–15 | the hash of the `.f18` source the engine was assembled from (ABI choice 3: by reference) |
| 16–31 | the host tool's hash, the compiler's identity (ABI choice 1) |
| 32–47 | the build configuration's hash: the knobs that change code, the cell width, `V4_NODE_WORDS`, the rings |
| 48–63 | the ROM's hash it must agree with: the tool's output is checked against the ROM's assembly |
## 5. Exports, imports, relocations
**An export (8 units):**
| Unit | Field |
|---|---|
| 0 | the name, as a string pool offset |
| 1 | the entry's offset in the code, in cells: the xt, relative to the base |
| 2 | the flags, as the entry's: immediate, compile-only, in-line, and the ACL defaults (pinned, mode) |
| 3 | the data stack effect: cells taken in the low 16 bits, cells left in the high 16, derived (choice 2) |
| 4 | the return stack effect, the same way, derived |
| 5 | the capabilities: bit 31 set if it touches ports; bits 0–30 the string pool offset of its list of kernel requests, or 0 for none |
| 6–7 | reserved, 0 |
**An import (6 units):**
| Units | Field |
|---|---|
| 0–1 | the exporting train's capsule hash, the exact build (choice 4) |
| 2 | the word's name, as a string pool offset |
| 3 | the data stack effect it is expected to have |
| 4 | the return stack effect it is expected to have |
| 5 | reserved, 0 |
**A relocation (2 units):**
| Unit | Field |
|---|---|
| 0 | the code cell, as an offset, and in the top 3 bits the slot whose branch field holds the address (0–3), or 7 for the whole cell |
| 1 | what it points to: `0xFFFFFFFF` for internal, so the base is added; otherwise the import's index |
Placement (`ABI.md` §5) patches each relocation's branch field. It refuses a patched address beyond that
slot's reach: 27, 22, 17 or 12 bits (`iword.h`).
**Slot 7, the whole cell** (ruled 2026-11-19, "Slot 7 = whole cell", step 3's design §6.1). The cell holds
an address as a value: an `&NAME` literal, or a dictionary link. Placement adds the base, or puts in the
import's address, to the whole cell, which reaches all of a node. Slots 4–6 are unused.
## 6. Verification (18 units, ADR §5)
| Units | Field |
|---|---|
| 0–15 | the SHA-512 hash of the proof that covers this exact artifact: its theory and its build; all 0 means none |
| 16 | the assumptions it holds under, as a string pool offset, or 0 |
| 17 | reserved, 0 |
## 7. What makes a valid artifact
The tool writes these properties and placement checks them. They are also the first things Isabelle states
about the format:
- the magic and the version;
- every count and offset within the payload;
- every string pool offset on a counted string, or, for a capabilities list, on a unit holding its count
*n* followed by *n* units, each a `KERNEL-WORD` number;
- every export's entry inside the code;
- every relocation's cell inside the code, its slot 0–3 one that holds a branch or 7, its import index
below I;
- every reserved unit 0.
## 8. Open, for ruling one at a time
1. ~~The unit~~ **Ruled 2026-11-19: "32-bit units".** Every record is in 32-bit units, low byte first,
as v4's blocks are, so the records read the same at either cell width (§1). Only the code is in the
build's cells.
2. ~~The hashes~~ **Ruled 2026-11-19: "SHA-512 for provenance".** The provenance hashes (source, tool,
configuration, ROM) and the proof's hash are SHA-512, the one already in the tree for Ed25519, 16
units each (§4, §6). An import's capsule hash stays the capsule's ID, XXHash64, 2 units (§5), and
signing stays Ed25519. The provenance record grows from 12 units to 64, with no reserved units, and
verification from 4 to 18.
3. ~~The return-stack effect~~ **Ruled 2026-11-19: "Record and check both".** The tool derives the
return-stack effect as it derives the data-stack effect, and records it in unit 4 of each export and
import (§5). Placement, compatibility (`ABI.md` §7, "the same stack effect") and the proofs check
both.
4. ~~Capabilities~~ **Ruled 2026-11-19: "Port bit + request list".** As drafted (§5, unit 5). The tool
derives it from the code: a port opcode sets the bit, and each kernel request the word reaches goes in
its list. Compatibility refuses a replacement that needs one the old did not (`ABI.md` §7). The list
is a count unit then that many request numbers (§7). The bit layout and the list's form were chosen in
drafting; confirmed by Captain Bob, 2026-11-19 ("Yes").
5. ~~Endianness for the code cells~~ **Ruled 2026-11-19: "Low-first, like the records".** Every byte of
the artifact has one order, low byte first, so its hashes and signature are the same whichever host
built it. A big-endian host swaps the bytes when it places the code.
## 9. Status
All five choices are ruled. This is the artifact layout, the ADR's step 2, as ruled. The next step is the
ADR's step 3: artifact production in the build (the host tool), designed for ruling before any code.
+14 -5
View File
@@ -892,11 +892,20 @@ is rechecked, otherwise the TTL is counted down; then a denied word is refused w
is in the variable `ACL-HOOK`; with none there, the word is allowed and given the longest TTL. `ACL.fth` puts
its `ACL-RECHECK` there (v3 finds it by name each time).
**Where this is weaker than v3.** v3's inner interpreter checks every execution, inside definitions too. v4
code is native: a compiled call goes straight to its word, and no opcode asks permission. So v4 checks a
word when it is *compiled* as well as when it is interpreted — a denied word cannot be built into anything
new — but a call compiled while the word was allowed is not checked again when it runs. Closing that needs
the check in the node itself (the `call` opcode), which is a hardware decision and is not taken here.
**Where this was weaker than v3, and is not now** (2026-11-19, Captain Bob: "As v3: add at call"; "Engine: call
redirects"; `docs/v4.0.0/plans/2026-11-19-acl-at-call.md`).
- **The old gap:** v3's inner interpreter checks every execution, inside definitions too. v4 checked a word
when it was compiled and when it was interpreted, and a compiled call was never checked again.
- **Now, at the call:** the engine's call hook may send a call elsewhere. The kernel checks every call from
code defined at run time. A word with TTL left is counted down at the call. At a TTL of 0, or for a denied
word, the call goes to `(ACL-CALL)` (`acl.f18`), which rechecks or refuses it by the word's name and goes on
to it.
- **No compile-time check:** a word being compiled is not checked, as in v3.
- **The policy runs unchecked:** while the policy rechecks a word, `(ACL-BUSY)` is 1 and nothing is checked,
as v3 runs its policy with the check off.
- **A node with no kernel has no check at call:** the hosted node is one. Its compiled calls are not checked.
- **On the FPGA,** the `call` opcode must offer its kernel the same redirect. That is to be designed with the
FPGA.
| Word | Fate | Notes |
| --- | --- | --- |
+5 -2
View File
@@ -26,7 +26,10 @@ machine and a ROM.
| **Trailer** | Source, as named blobs. `.f18` is F18 assembler. `.4th` is FORTH. The blob's name gives its type. | The capsule directory (`capsules/`) |
The ROM is the only binary. It runs the same on the C engine and on the FPGA: one binary, the
same behaviour. Assemble FORTH from the trailer and the node is a FORTH machine. Assemble Lisp
same behaviour. **Superseded in part, 2026-11-19** (Captain Bob, "ADR supersedes";
`ADR-2026-11-19-F18-ARTIFACTS.md`): the build may also compile F18 into binary artifacts, with their
identity, provenance and interface. An artifact is a choice, not a requirement: the ROM still
assembles source at boot. Assemble FORTH from the trailer and the node is a FORTH machine. Assemble Lisp
and it would be a Lisp machine. The engine and the ROM do not change.
### 1.1 What it is for
@@ -204,7 +207,7 @@ streams the ROM instead.
| Today | Becomes |
|---|---|
| `v4/capsule/*.v4`, 14 files, 311 words, assembled on the build machine | `.f18` blobs under `capsules/v4/`, assembled by the ROM at boot |
| `v4/tools/mkimage.c` → `nucleus-64.f18`, a prebuilt dictionary | Builds the ROM only. The nucleus binary is gone. |
| `v4/tools/mkimage.c` → `nucleus-64.f18`, a prebuilt dictionary | Builds the ROM only. The nucleus binary is gone. (2026-11-19: compiled F18 artifacts are allowed beside the ROM, `ADR-2026-11-19-F18-ARTIFACTS.md`.) |
| `v4/src/text.c`, the assembler in C | The ROM's assembler is F18 code. `text.c` builds the ROM, as the first assembler builds the next. |
| `forth79.4th`: `U*`, `U/MOD` only | Every FORTH-79 word that is not an opcode, a register or the FORTH machinery (`NUCLEUS.md` 4, rule 1). It moves group by group, with POST after each (`NUCLEUS.md` 8, step 3). |
| `boot_capsules[]` in `v4/system/boot.c` | The system list (step 2, then step 3) is the loader's. Everything after POST is `init.4th`'s. |
+34
View File
@@ -88,3 +88,37 @@ the system capsules. It is the only boot policy, so the loader's one fixed step
It may also change what `init.4th` is: a capsule, or not. **Nothing of this design is built until
that conversation.**
## 7. Steps 1 and 2 built (2026-11-19)
**Ruled:** "ACL at boot", first of the new work after `v4.0.0-alpha.5`. The policy loads "From
init.4th", so `init.4th` comes off hold. The include is to be "Compose[d] in FORTH". Capsules are
ephemeral and placed by block (`2026-11-18-capsule-blocks.md`), which settles the hold.
**What is built:**
- **`capsules/v4/init.4th`**, at block 3980, so it lands at RAM 1932. It runs
`S" v4:ACL.4th" CAPSULE-INCLUDE` (security on), then `STARSHIPOS` (the search order). The order is
last-first because `ACL.4th` ends in `FORTH DEFINITIONS`.
- **`capsules/v4/ACL.4th`**: the policy, `git mv`ed from `v4/capsule/ACL.fth`. It is reflowed into
four 64×16 blocks chained with `-->` (3984–3987, landing at 1936), and its text is unchanged.
- **`CAPSULE-INCLUDE ( baddr u -- )`** in `centre.4th`, composed from `CAPSULE-OPEN` and
`CAPSULE-LINE`: the capsule is placed, and its lowest block is `LOAD`ed. It has a dictionary entry.
- **The mesh loads `v4:init.4th` after POST and `COLD`,** after the `PARITY:V4_SYSTEM` line, so that
line's `dict_hash` stays the sealed system's. This is the loader's one fixed step there.
- **`test_host_quit`** types `ACL.4th` as it types any capsule, skipping its `Block` and `-->` lines.
**Test first** (`logs/20261119-init-acl/`):
- `test_mesh_boot`: `init.4th`'s parity line; `DOE` found without naming `STARSHIPOS`; `ACL-BOOT`
and `ACL-RECHECK` pinned. The before-run failed.
- One false pass was found and corrected on the way. The two checks had first been placed after the
test's own `COLD`, where the search-order check passed only because the line before it named
`STARSHIPOS`. They now run straight after the boot.
**Results:**
- 113 checks pass, with POST 990/990.
- All 52 tests at 64 bits, test-32 and ASan/UBSan pass.
- The dictionary gate passes with 405 words.
- One amd64 kernel session passes 18/18, with "ACL: active" at boot.
**Still open, one at a time:** `BIRTH` pinned; the countdown "at call"; `CAPSULE-BIRTH`; births by
`init.4th`; the identity gate and the prompt moving from C into `init.4th`.
+127
View File
@@ -0,0 +1,127 @@
# The ACL countdown at `call` -- design, for ruling
Written 2026-11-19. Captain Bob ruled "As v3: add at call", then "Engine: call redirects". That takes the
decision DECOMPOSITION.md §5.20 left open: "Closing that needs the check in the node itself (the `call`
opcode), which is a hardware decision and is not taken here."
**Built 2026-11-19, ruled "Build it"; section 6 is as built.**
## 1. v3, and v4 today
**v3** (`v3/src/vm.c`) checks a word in two places:
- in the inner interpreter (:600–620), at every execution inside a colon definition: the TTL is counted
down, or the word is rechecked when it is 0, and refused if it is denied;
- in the outer interpreter (:725–742), for a word executed at the prompt.
v3 does not check when it compiles a word. Its system words are C, so their calls among themselves are not
checked.
**v4** (`compile.f18`, `(ACL?)`) checks in `INTERPRET`, for every word it is about to execute **or
compile**. A call compiled into a definition is never checked again when it runs.
## 2. The design
### 2.1 The engine: the call hook may redirect
`v4_call_hook` now returns the address to go to. The engine (`v4/src/exec.c`) sets P to what the hook
returns rather than to the target. With no hook, or a hook that returns the target, nothing changes.
This is the engine change §5.20 called a hardware decision. On the FPGA, the `call` opcode would have to
offer the same to its kernel, so this needs a design of its own when the FPGA is built. In the golden model
the hook is the kernel watching its node's calls, as it already does for the word accounts.
### 2.2 The kernel's hook (`v4/system/mesh.c`, `on_call`)
The hook already picks the calls v3 would count: calls from code defined at run time, a word known to the
kernel's table. For those only (not `INTERPRET`'s dispatch, which `(ACL?)` checks already), it reads the
target's flags cell, `target - 3`:
- **Fast path**, TTL above 0 and not denied: the TTL is counted down (one cell written) and the call goes
on to the target. No FORTH runs.
- **Slow path**, TTL 0, or denied: the target is kept in a node variable, `(ACL-TARGET)`, and the call is
redirected to `(ACL-CALL)`.
### 2.3 `(ACL-CALL)`, F18 source beside `(ACL?)` in `compile.f18`
`(ACL-CALL)` fetches `(ACL-TARGET)` and runs `(ACL?)` on it, which is v3's check:
- a TTL of 0 is rechecked through `(ACL-HOOK)`, the policy's `ACL-RECHECK`;
- otherwise the TTL is counted down;
- a denied word is refused with v3's line, `WARN: ACL: denied 'xxx'`, the stack emptied and the line ended.
An allowed word is then jumped to. The return address the `call` pushed is still on the return stack, so
the word returns to the original caller, as if it had been called directly.
### 2.4 The compile-time check goes
As ruled ("drop its compile-time check so both match v3"), `INTERPRET` checks only the words it executes,
and a word being compiled is not checked. A denied word can be compiled into a definition; the definition is
refused when it runs and reaches the call.
## 3. Cost
- **Fast path:** one memory read and one write, for calls the hook already examines. The hook already reads
`target - 4` (the word ID), next to it.
- **Slow path:** only at a recheck, every TTL-worth of uses (256 to 65535), or for a denied word.
- **Measured as before:** the host mesh boot, five alternating runs, old and new. Then the protocol.
## 4. Tests, first
In `test_mesh_boot`, with the policy loaded by `init.4th`:
1. A word called from inside a definition counts down: `: F 65 EMIT ; : G F ; G`, then `' F ACL-TTL@`, is
one less than after the first use.
2. A denied word called from inside a definition is refused when the definition runs: `0 ' F ACL-ALLOW!`,
then `G`, gives `WARN: ACL: denied 'F'`.
3. A word whose TTL is 0, reached from a definition, is rechecked by the policy and given its TTL.
4. A denied word can be compiled into a definition. The compile is not refused; the refusal comes at run.
5. A word at the prompt is counted once, not twice: `INTERPRET`'s check, and no second one from the hook.
6. POST is 990/990 unchanged: POST runs before `init.4th`, with no policy.
Each is seen to fail before the change.
## 5. For ruling
1. The design above, 2.1 to 2.4?
2. The FPGA: record the redirect as the call opcode's requirement, to be designed with the FPGA?
## 6. As built (2026-11-19)
**Two things changed from the design, both found while building.** Both are needed to match v3, so
neither is a new ruling:
1. **`(ACL-BUSY)`, a recursion guard.** The policy's `ACL-RECHECK` is code defined at run time. Its own
calls would be checked, and at a TTL of 0 they would recheck themselves without end. v3 runs its policy
with the check off (`emergency_console`). `(ACL-RECHECK)` now sets `(ACL-BUSY)` around the policy, and
the kernel checks nothing while it is set.
2. **`(ACL-CALL)` has its own check and refusal.** It prints the word's name from its entry, not from
`WORD`'s buffer. A first version copied the name into that buffer and broke POST's
`CONVERT.digits`, which reads that buffer after `WORD`.
**The target goes on the data stack** for `(ACL-CALL)`, so it needs no variable. Two map cells were added
from free memory:
- `(ACL-CALLX)`, at `BUF0_W - 113`: `(ACL-CALL)`'s address, stored by `end.f18`;
- `(ACL-BUSY)`, at `BUF0_W - 144`.
**What changed:**
- `exec.h` and `exec.c`: the hook returns where P goes.
- `mesh.c`: `acl_at_call()`, applied to calls from code; `INTERPRET`'s dispatch is left to `(ACL?)`.
- `compile.f18`: `INTERPRET`'s compile path no longer checks, and `(ACL-RECHECK)` sets `(ACL-BUSY)`.
- `acl.f18`: `(ACL-CALL)`.
- `end.f18`, `host_map.h`, `mkmap.c`, `image.h`: the two cells.
**Test first** (`logs/20261119-acl-at-call/`):
- `test_mesh_boot`, with the policy on. Five checks failed before:
- a call from a definition is counted down;
- a denied word called from a definition is refused by its own name, and does not run;
- a denied word compiles;
- it is refused when the definition runs.
The sixth, that a word at the prompt is counted once, passed before and after.
- `test_exec`: a hook that returns another address redirects the call, which returns to the caller.
- `test_host_quit`'s two v4-only expectations changed to v3's: a denied word compiles. That host node has
no kernel, so its compiled calls are not checked there.
**Verified:**
- `test_mesh_boot` passes 120 checks, with POST 990/990.
- All 52 tests at 64 bits, test-32, and ASan/UBSan pass.
- The amd64 kernel builds, and one amd64 session passes 18/18.
- **The cost** (`timing.txt`, five alternating host mesh boots): median 15.227 s old against 15.439 s new,
+1.4%. That is inside the old runs' own spread, 15.06 to 15.99 s, so no measurable cost.
@@ -0,0 +1,180 @@
# Artifacts in the build -- design, for ruling
Written 2026-11-19. Step 3 of `ADR-2026-11-19-F18-ARTIFACTS.md` §7, "Integrate artifact production into the
existing build system". It builds on:
- `ABI.md`, ABI v0 as ruled, in particular choice 1, "A host tool";
- `ARTIFACT.md`, the layout as ruled.
**Nothing here is built.** The questions in §6 are ruled (2026-11-19).
## 1. What is there already
- **The host assembler exists.** `v4/src/text.c` assembles `.f18` text onto a node. `v4/tools/mkrom.c`
uses it on the build machine to build the ROM, "as a bitstream is built". The tests use it to build the
system.
- **The ROM and `text.c` are proved to agree.** `test_host_rom_nucleus` assembles the system's source
twice:
- once off the node with `text.c`, the oracle;
- once on the machine, by the ROM fed through the console.
Every word of RAM must be the same, apart from the ROM's own state. This is ABI choice 1's cell-for-cell
check already, for the one train that has `.f18` today.
- **Only one train has `.f18` today: the nucleus.** Its source is `capsules/v4/sys`. The map comes first,
then the fourteen files in `sys_files.h`'s order, then `end.f18`. The boot feeds them to the ROM as the
blobs `v4:sys:*.f18` (`boot.c`).
- **The nucleus is not relocatable.** It is assembled at a fixed origin against the map's fixed addresses.
`end.f18` `store`s addresses into the map's variables, and its dictionary holds absolute links. Ruling 1
keeps it as it is: the ROM still assembles the system at boot (`ABI.md` §8).
## 2. The tool: `v4/tools/mkf18a.c`
A C tool beside `mkrom.c`, built the same way, one per cell width:
mkf18a OUT.f18a MAP.f18 DIR
1. It assembles every `.f18` in DIR with `text.c`, at origin 0, in name order (ruled §6.3), after MAP.
2. It writes the artifact, laid out as `ARTIFACT.md` gives:
- the header;
- the provenance, with its four SHA-512 hashes;
- the exports, the imports and the relocations;
- an empty verification record;
- the string pool and the code, low byte first.
3. It fails the build if anything cannot be written as the ABI requires:
- a relocation whose patched address is beyond its slot's reach;
- a capability it cannot derive.
**The relocations come from `text.c`.** `text.c` gains a record of each cell it lays down that holds an
address: every branch it resolves to a word or a label, and every `&NAME`. That is one hook, and test-first:
`test_text` checks the record against the cells.
**The stack effects come from a new analysis**, `v4/src/effect.c`. It walks each word's instruction words
from its entry to every `;` and counts what each opcode takes and leaves on both stacks:
- the opcode table is `iword.h`'s;
- a call takes the effect of the word it calls, derived first;
- a branch that joins two paths with different depths is "no fixed effect";
- so are a loop whose count is data, `EXECUTE` and a `DEFER`red word.
It is a module of its own, so the proofs can state it on its own (ADR step 5).
## 3. Where it runs
- **`v4/Makefile`:** `make -C v4 artifacts` builds the artifacts of each width into `v4/build/`. `make -C v4
test` runs it, so a `.f18` the tool refuses fails the test gate.
- **The check against the ROM:** the nucleus is not an artifact (ruled §6.2a), so no file is written for it.
`test_host_rom_nucleus` assembles it with the tool's assembler, the address record turned on, and the ROM
must still lay down every word the same. That proves the record changes no cell. The records themselves
are proved by the small train (§4, test 5).
- **The kernel build:** nothing changes in step 3. The boot still feeds the ROM the source. Carrying the
artifact in the capsule, and placing it, is steps 4 and 6.
- **CI:** `build.yml`'s `v4-tests` job runs `make -C v4 test` already, so it gains the gate with no change.
## 4. Test first, seen to fail
1. `test_text`: the address record for a branch, a forward branch, a label, and an `&NAME`.
2. `test_effect`, new: words of known effect, written in `test_text`'s notation:
- `dup` (1 → 2);
- `drop` (1 → 0);
- a call;
- a `for`/`next` loop of fixed count;
- two branches that agree;
- two branches that disagree (no fixed effect).
3. `test_mkf18a`, new: a small text's artifact read back unit by unit against `ARTIFACT.md`. It checks the
magic, the counts, each record, every reserved unit 0, and the code low byte first.
4. `test_host_rom_nucleus`, with the address record on: the ROM's assembly equal to the tool's, word for
word (ruled §6.2a: no artifact file for the nucleus).
5. Then a small train, a few words of `.f18` with one import from the nucleus, is placed from its artifact
at a base other than 0. Its words run, and its calls into the nucleus reach the nucleus (ruled §6.2).
POST, the protocol and the dictionary gate are unchanged, since the boot is unchanged.
## 5. Cost
The build gains one assembly of the nucleus per width, which takes a second or less on the host
(`test_host_rom_nucleus` reports its time today), plus the analysis. That is measured when it is built, as
ADR step 8 asks. The boot gains nothing.
## 6. For ruling, one at a time
1. ~~Address literals~~ **Ruled 2026-11-19: "Slot 7 = whole cell"**, recorded in `ARTIFACT.md` §5 and §7.
As asked: `ARTIFACT.md` §5's relocation covers branch fields only (a slot, 0–3). The
system's source also holds addresses in whole cells: the `&NAME` literals (31 in `capsules/v4/sys`),
and the dictionary's links. One fix is a slot value of 7 meaning "the whole cell". The top 3 bits allow
0–7, so the record keeps its size.
2. ~~Which train first~~ **Ruled 2026-11-19: "Both, nucleus first".** The nucleus is built and checked
against the ROM; then a small train is placed at a base other than 0, to prove the relocations (§4,
test 5). As asked: The nucleus is the only `.f18` train, but it is not relocatable, and the ROM keeps
assembling it (§1). Its artifact can be built and checked (§3), but it is never placed by the loader.
**2a, ruled 2026-11-19: "Nucleus not an artifact".** Asked how an artifact would say it is fixed at an
origin, since `ABI.md` §4 has its code "as if placed at address 0": only relocatable trains are
artifacts. The nucleus is checked as the tool's assembly against the ROM's, and no artifact file is
written for it. `ABI.md` §4 stands.
Is the nucleus the first artifact, or is a small relocatable train written first?
3. ~~The order of the sources~~ **Ruled 2026-11-19: "All it finds, name order".** The tool takes every
`.f18` in a train's directory, sorted by name, so the file names set the order (`00-core.f18`, ...) and
there is no list to keep. As asked: Captain Bob's image is "the .f18 assembler assembles all .f18 files it
finds", but the order matters: the map first, `sys_files.h`'s list, `end.f18` last. Does each train
name its order in a list, as `sys_files.h` does, or does the tool take the files in name order?
**3a, ruled 2026-11-19: "Nucleus too: rename".** Asked whether name order applies to the nucleus,
which is read in `sys_files.h`'s order: it does. `capsules/v4/sys` is renamed so that its name order is
today's order, the map first and `end.f18` last (`00-map`, `01-core`, ... `99-end`), and `sys_files.h`
goes. The boot, the tests and the ROM's feed read the directory in name order. The blob names and the
capsule hashes change, so the protocol runs again. This is a task of its own, designed and tested
first. One point for its design: the directory holds both widths' maps, `map-32.f18` and `map-64.f18`,
and name order would take both.
4. ~~Which words are exports~~ **Ruled 2026-11-19: "Every fixed-effect word".** Every word the tool
derives a fixed effect for is exported; the rest stay internal, and the build does not fail for them.
As asked: The nucleus defines hundreds of words, and some have no fixed effect, which
2c refuses as exports. Is every word with a fixed effect exported, or only those a list names? With a
list, the words outside it stay internal.
5. ~~The tool's identity~~ **Ruled 2026-11-19: "Its source".** The provenance's tool hash is the SHA-512 of
the tool's source: `mkf18a.c`, `text.c`, `effect.c` and the v4 headers they include, in a fixed order.
The same source gives the same hash on every host. As asked: The provenance holds "the host tool's hash". The hash of the binary differs
with the host's compiler. Should it be the hash of the tool's source (`mkf18a.c`, `text.c`, `effect.c`
and their headers), or of the binary?
6. ~~The name~~ **Ruled 2026-11-19: "mkf18a / .f18a"**, after the magic: `v4/tools/mkf18a.c`, and each
train's artifact `<train>.f18a`. As asked: `mkf18a` and `.f18a`, after the magic, or something else?
## 7. Status, and the order of the work
All six questions are ruled, plus 2a and 3a. Each task below is built test-first, seen to fail, and
accepted before the next:
1. `text.c`'s address record (§4, test 1), with `test_host_rom_nucleus` unchanged (test 4).
2. `effect.c`, the stack-effect analysis (test 2).
3. `mkf18a` and `make -C v4 artifacts` (test 3).
4. The small train, placed at a base other than 0 (test 5).
5. The nucleus renamed to name order (3a), designed first: it changes the boot, so the protocol runs.
## 8. Task 1 built (2026-11-19): `text.c`'s address record
**What changed:**
- `text.h` and `text.c`: `v4_text_record(t, buf, cap)` turns the record on, and `v4_text_addresses(t)` says
how many were recorded. Each entry is a cell and its slot, 0–3 for a branch field or 7
(`V4_TEXT_WHOLE_CELL`) for the whole cell. What is recorded:
- every branch, to a word or a label, back or forward, including `NEXT`'s;
- an `&NAME` literal in code, and `#, &NAME`;
- `here`, and a `set` variable that holds an address, wherever it is laid down (code, `#,`, `store`);
- a header's name cell, and its link when there is an entry before it.
The map's constants and plain numbers are not recorded. A full record is an error. With the record off,
nothing changes.
- **Found while building:** the nucleus lays its headers down with `set HDR-NFA here ... #, HDR-LINK`, not
with `header`. So a `set` variable carries whether it holds an address, or those links would be missed.
**Test first** (`logs/20261119-text-record/`):
- `test_text`: 15 new checks. Before the change, 13 failed: every one that expects an address recorded.
The two that expect nothing passed, as they should. Two errors in the tests themselves were fixed before
the change: `source` needs its `N-1` constant, and the notation is `FOR ... NEXT`, upper case.
- `test_host_rom_nucleus`, with the record on (test 4). On the system's source it records 1825 branches
and 664 whole cells. Every whole cell holds an address of the assembly, and the ROM's assembly is still
equal to it word for word, at both widths. This check could not be seen to fail before: the record did
not exist. It guards that the record changes no cell.
**Verified:**
- `make -C v4 test` passes: all tests at both widths, and the three mesh boots with POST 990/990.
- `make -C v4 test-32` passes.
- ASan+UBSan passes for every test at both widths, and for the mesh boot (POST 990/990). The run hit my
one-hour background limit at the 64-bit `test_host_mesh`, so the rest was run again from there.
`v4-gates.txt` and `v4-sanitize-rest.txt` hold the two parts.
- The boot does not use the record, so the kernel and the protocol are unchanged.
@@ -0,0 +1,26 @@
# F18 binary artifacts, ABI/API, live updates -- the rulings
The decision is `docs/v4.0.0/ADR-2026-11-19-F18-ARTIFACTS.md`, recorded as given. This file records each
conflict between it and the existing record, put to Captain Bob one at a time, and his ruling.
**Nothing is built.** The ADR's §7 order is followed; step 1 is the minimal ABI contract.
## The conflicts, one at a time
1. **"The ROM is the only binary"** (MACHINE.md §1, §5, ruled 2026-10-15) against compiled F18 artifacts.
**Ruled: "ADR supersedes".** MACHINE.md §1 and §5 now say that compiled artifacts are allowed beside the
ROM. An artifact is a choice, not a requirement: the ROM still assembles source at boot.
2. **"Hermes: Messaging, routing, and communication"** (ADR §3.3) against the record. The Hermes VM was
removed (FABRIC-3.5/3.6, 2026-09-22), and v4's messages travel on the fabric's wires and routes.
**Ruled: "The messaging role".** Hermes names the role, not a VM: in v4 the fabric's wires and routing,
and on v3 kernel-Hermes. No Hermes node is brought back. The ADR carries a note saying so.
3. **"Artemis: Memory, persistence, and recovery"** (ADR §3.3) against the record. Artemis is the persistence
path (FABRIC-3.5 XIV.3), and memory is the kernel's. **Ruled: "Persistent memory".** Artemis owns what is
kept: persistent storage, staged artifacts and recovery copies. Run-time memory stays the kernel's: the
Stadium allocates it, and the kernel serves blocks. The ADR carries a note saying so.
4. **A word's logical identity** (ADR §3.2: not addresses or placement). Today v4 has three identities: the
word ID (assigned in order, given back by FORGET), `ACL-WORD-ID` (its address) and the kernel's table of
entries (addresses). **Ruled: "Capsule + name".** A word's identity is its defining artifact's identity,
the content hash, plus the word's name. It is stable across builds of the same source and independent of
where the word loads. Addresses and word IDs stay as local resolution only.
@@ -0,0 +1,213 @@
[=3h[=3h[=3hBdsDxe: loading Boot0001 "UEFI QEMU DVD-ROM QM00005 " from PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x2,0xFFFF,0x0)
BdsDxe: starting Boot0001 "UEFI QEMU DVD-ROM QM00005 " from PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x2,0xFFFF,0x0)
[=3hStarKernel UEFI Loader
Loading kernel from ESP...
[CKPT 001] Entered efi_main - ConOut live
RAW SERIAL UP
[CKPT 002] Serial (COM1) initialized
Monolithic build - kernel linked directly
Collecting boot information...
CmdLine: parsed OK
[CKPT 004] Command line parsed
[CKPT 005] Kernel stack allocation decided
[CKPT 006] Boot info collected (ACPI table located)
GOP: linear framebuffer found
[CKPT 007] GOP: linear framebuffer found
[CKPT 008] About to enter ExitBootServices retry loop
EBS...
EBS OK
Calling kernel_main (monolithic)...
_____ _ _ __ _
/ ____| | | |/ / | |
| (___ | |_ __ _ _ __| ' / ___ _ __ _ __ ___| |
\___ \| __/ _` | '__| < / _ \ '__| '_ \ / _ \ |
____) | || (_| | | | . \ __/ | | | | | __/ |
|_____/ \__\__,_|_| |_|\_\___|_| |_| |_|\___|_|
LithosAnanke v4.0.0-alpha.5 amd64
Architecture: amd64
Build: Nov 19 2026 11:52:46
UEFI BootServices: EXITED
Console: serial line is a 16550 at port 0x00000000000003f8 (COM1, probed)
=== StarKernel Boot Information ===
Memory map entries: 130
Total memory: 1023 MB
Usable memory: 964 MB
===================================
PMM initialized.
PMM statistics:
Total pages: 248349
Free pages : 246822
Used pages : 1527
Total MB : 970
Free MB : 964
Used MB : 5
VMM initialized (mapped RAM, CR3 switched)
VMM initialized (mapped RAM, CR3 switched)
VMM self-test: mapped OK at 0xffff800000000000
VMM self-test complete.
IDT installed.
APIC: init...
APIC: IA32_APIC_BASE MSR=0x00000000fee00900
APIC: stale-ISR drain: 0 EOI(s) issued
APIC: initialized (xAPIC MMIO, TPR=0, SIVR=0x1FF, EOI-clear)
APIC: init done
I/O APIC: init...
I/O APIC: base=0xfec00000, gsi_base=0, overrides=5
override: source=00 gsi=2 flags=0x0000
override: source=05 gsi=5 flags=0x000d
override: source=09 gsi=9 flags=0x000d
override: source=0a gsi=10 flags=0x000d
override: source=0b gsi=11 flags=0x000d
i8042: keyboard ACKed enable-scanning
i8042: IRQ1 enabled in controller config byte
I/O APIC: keyboard IRQ1 routed (masked)
Timer: init...
Timer: init start
Timer: PM_TMR_BLK discovered from FADT at port 1544
Timer: VM mode detected (hypervisor present).
Timer: HPET calibration disabled (VM-exit MMIO would poison timing).
Timer: WARNING: invariant TSC not present under hypervisor.
Timer: continuing in RELATIVE mode (no determinism guarantees).
Timer: RDTSCP not present; using RDTSC (less serialized).
Timer: CPUID frequency unavailable; trying PM Timer...
Timer: trust=1 (0=NONE,1=REL,2=ABS), TSC=2092874912 Hz
Timer: init done
Kernel heap initialized.
Heap statistics:
Total bytes: 536870872
Free bytes: 536870872
Used bytes: 0
Peak bytes: 0
Heap base addr: 24641536
Heap end addr: 561512448
Heartbeat: init...
APIC Timer: calibrating...
APIC Timer: apic_hz=1004918605, tick_hz=100, initial_count=10049186
APIC Timer: configured (masked, ready to start)
Heartbeat: init done
Kernel initialization complete.
Boot successful!
Boot disk: not a StarshipOS stick
System: StarForth v4 (this build's default)
Stadium: 83886 cells (5242 KB), 50 VM slots
Switch-signal: 50 slots
Kernel-Hermes: 50 channel slots
Kernel-Hermes: 50 pending-queue slots
StarForth v4: Hera, born in the kernel's fabric
V4: capsule v4:sys:map-64.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:map-64.f18 capsule_hash=0x06cb44832df2b8fd
V4: capsule v4:sys:core.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:core.f18 capsule_hash=0x0f415502fccc3fba
V4: capsule v4:sys:input.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:input.f18 capsule_hash=0x0f13c3f9d5fd07fc
V4: capsule v4:sys:dict.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:dict.f18 capsule_hash=0xe3453808afd5a0af
V4: capsule v4:sys:codegen.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:codegen.f18 capsule_hash=0x36d2ae84d2911b90
V4: capsule v4:sys:compile.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:compile.f18 capsule_hash=0xb46bf77ceee7245a
V4: capsule v4:sys:quit.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:quit.f18 capsule_hash=0x7fa7a7668b6bf1ed
V4: capsule v4:sys:forth.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:forth.f18 capsule_hash=0xc4c0ad315c95eda4
V4: capsule v4:sys:numout.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:numout.f18 capsule_hash=0xca0fb0f9c1589e20
V4: capsule v4:sys:words.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:words.f18 capsule_hash=0x2f4e5f7f3e7f736f
V4: capsule v4:sys:system.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:system.f18 capsule_hash=0xfe257eb084c43a5d
V4: capsule v4:sys:qmath.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:qmath.f18 capsule_hash=0xa93783c2c8f9b7db
V4: capsule v4:sys:blocks.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:blocks.f18 capsule_hash=0x09d361dbe6174236
V4: capsule v4:sys:log.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:log.f18 capsule_hash=0x544cd004233dff62
V4: capsule v4:sys:acl.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:acl.f18 capsule_hash=0x76e7e746befa2733
V4: capsule v4:sys:end.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:end.f18 capsule_hash=0x98fd33b1c431cfe7
PARITY:V4_ROM words=2383 rom_hash=0xd858ef412d684f92 instructions=63411003
V4: capsule v4:forth79.4th signature: missing (unsigned)
PARITY:V4_CAPSULE name=v4:forth79.4th capsule_id=0x4609d6ef54166ef8 capsule_hash=0x4609d6ef54166ef8 dict_hash=0x71be72a2ab8daaad
V4: capsule v4:starshipos.4th signature: missing (unsigned)
PARITY:V4_CAPSULE name=v4:starshipos.4th capsule_id=0x1734a8f4fe7483a5 capsule_hash=0x1734a8f4fe7483a5 dict_hash=0xa461a1e1146cda29
V4: capsule v4:centre.4th signature: missing (unsigned)
PARITY:V4_CAPSULE name=v4:centre.4th capsule_id=0x53b1e3df644e8e25 capsule_hash=0x53b1e3df644e8e25 dict_hash=0xa707233375381650
V4: capsule v4:hera.4th signature: missing (unsigned)
PARITY:V4_CAPSULE name=v4:hera.4th capsule_id=0x78730b1d6effe892 capsule_hash=0x78730b1d6effe892 dict_hash=0xe99e0b3dc3299404
V4: capsule v4:physics.4th signature: missing (unsigned)
PARITY:V4_CAPSULE name=v4:physics.4th capsule_id=0x5b0195fc30828bde capsule_hash=0x5b0195fc30828bde dict_hash=0xcf809ad125d53a6b
PARITY:V4_POST tests=990 pass=990 fail=0
PARITY:V4_SYSTEM word_count=405 dict_hash=0x370824d256c98583
V4: capsule v4:init.4th signature: missing (unsigned)
V4: capsule v4:ACL.4th signature: missing (unsigned)
INFO: ACL: active
PARITY:V4_CAPSULE name=v4:init.4th capsule_id=0x24af6802c576c1c1 capsule_hash=0x24af6802c576c1c1 dict_hash=0x5174b8e4060018cd
PARITY:OK
POST: PASSED
PCI: init...
PCI: ECAM mapped (amd64)
virtio-rng: no device on PCI bus 0
rng: backend = rdrand
entropy: ready
virtio-input: no device on PCI bus 0
Starting heartbeat...
APIC Timer: started (LVT=0x00020020 ICR=10049186)
I/O APIC: keyboard IRQ1 unmasked
Heartbeat running.
Stadium opcodes: 31 resident, hottest opcode 8
Stadium words: promotions=269 evictions=0
Stadium conservation: resident_sum=43680 reservoir=21856 sum=65536 (Q48_ONE=65536)
Stadium conservation: CONSERVED
Stadium quota grant self-test: OK
Hera reservoir=21856
test-vm reservoir=65536
Heartbeat: 4 ticks, trust=0x00010000, variance=0x00000000
blkio_usb: MSC device ready
Artemis: the stick's partition attached
[Hera] Zuse: genesis minted onto attached thumbdrive
[zuse@Hera] ok> 3 4 + .
[zuse@Hera] 7 ok
[zuse@Hera] ok> NODE-ME .
[zuse@Hera] 0 ok
[zuse@Hera] ok> 11 2 2 BIRTH .
[zuse@Hera] V4: capsule v4:forth79.4th signature: missing (unsigned)
[zuse@Hera] PARITY:V4_BIRTH node=11 dict_hash=0x74781d08f32ff33a
[zuse@Hera] 1 ok
[zuse@Hera] ok> S" 6 7 * ." 11 SEND 11 AWAIT .
[zuse@Hera] 42 1 ok
[zuse@Hera] ok> 11 KILL
[zuse@Hera] Stadium words: promotions=301 evictions=0
[zuse@Hera] Stadium conservation: resident_sum=136 reservoir=65400 sum=65536 (Q48_ONE=65536)
[zuse@Hera] Stadium conservation: CONSERVED
[zuse@Hera] ok
[zuse@Hera] ok> 11 2 2 BIRTH .
[zuse@Hera] V4: capsule v4:forth79.4th signature: missing (unsigned)
[zuse@Hera] PARITY:V4_BIRTH node=11 dict_hash=0x74781d08f32ff33a
[zuse@Hera] 1 ok
[zuse@Hera] ok> S" VARIABLE N1 : SPIN BEGIN 1 N1 +! AGAIN ;" 11 SEND 11 AWAIT .
[zuse@Hera] 1 ok
[zuse@Hera] ok> S" SPIN" 11 SEND
[zuse@Hera] ok
[zuse@Hera] ok> 3 4 + .
[zuse@Hera] 7 ok
[zuse@Hera] ok> 11 KILL
[zuse@Hera] Stadium words: promotions=306 evictions=0
[zuse@Hera] Stadium conservation: resident_sum=196 reservoir=65340 sum=65536 (Q48_ONE=65536)
[zuse@Hera] Stadium conservation: CONSERVED
[zuse@Hera] ok
[zuse@Hera] ok> 
@@ -0,0 +1,213 @@
[=3h[=3h[=3hBdsDxe: loading Boot0001 "UEFI QEMU DVD-ROM QM00005 " from PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x2,0xFFFF,0x0)
BdsDxe: starting Boot0001 "UEFI QEMU DVD-ROM QM00005 " from PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x2,0xFFFF,0x0)
[=3hStarKernel UEFI Loader
Loading kernel from ESP...
[CKPT 001] Entered efi_main - ConOut live
RAW SERIAL UP
[CKPT 002] Serial (COM1) initialized
Monolithic build - kernel linked directly
Collecting boot information...
CmdLine: parsed OK
[CKPT 004] Command line parsed
[CKPT 005] Kernel stack allocation decided
[CKPT 006] Boot info collected (ACPI table located)
GOP: linear framebuffer found
[CKPT 007] GOP: linear framebuffer found
[CKPT 008] About to enter ExitBootServices retry loop
EBS...
EBS OK
Calling kernel_main (monolithic)...
_____ _ _ __ _
/ ____| | | |/ / | |
| (___ | |_ __ _ _ __| ' / ___ _ __ _ __ ___| |
\___ \| __/ _` | '__| < / _ \ '__| '_ \ / _ \ |
____) | || (_| | | | . \ __/ | | | | | __/ |
|_____/ \__\__,_|_| |_|\_\___|_| |_| |_|\___|_|
LithosAnanke v4.0.0-alpha.5 amd64
Architecture: amd64
Build: Nov 19 2026 14:03:55
UEFI BootServices: EXITED
Console: serial line is a 16550 at port 0x00000000000003f8 (COM1, probed)
=== StarKernel Boot Information ===
Memory map entries: 126
Total memory: 1023 MB
Usable memory: 964 MB
===================================
PMM initialized.
PMM statistics:
Total pages: 248348
Free pages : 246821
Used pages : 1527
Total MB : 970
Free MB : 964
Used MB : 5
VMM initialized (mapped RAM, CR3 switched)
VMM initialized (mapped RAM, CR3 switched)
VMM self-test: mapped OK at 0xffff800000000000
VMM self-test complete.
IDT installed.
APIC: init...
APIC: IA32_APIC_BASE MSR=0x00000000fee00900
APIC: stale-ISR drain: 0 EOI(s) issued
APIC: initialized (xAPIC MMIO, TPR=0, SIVR=0x1FF, EOI-clear)
APIC: init done
I/O APIC: init...
I/O APIC: base=0xfec00000, gsi_base=0, overrides=5
override: source=00 gsi=2 flags=0x0000
override: source=05 gsi=5 flags=0x000d
override: source=09 gsi=9 flags=0x000d
override: source=0a gsi=10 flags=0x000d
override: source=0b gsi=11 flags=0x000d
i8042: keyboard ACKed enable-scanning
i8042: IRQ1 enabled in controller config byte
I/O APIC: keyboard IRQ1 routed (masked)
Timer: init...
Timer: init start
Timer: PM_TMR_BLK discovered from FADT at port 1544
Timer: VM mode detected (hypervisor present).
Timer: HPET calibration disabled (VM-exit MMIO would poison timing).
Timer: WARNING: invariant TSC not present under hypervisor.
Timer: continuing in RELATIVE mode (no determinism guarantees).
Timer: RDTSCP not present; using RDTSC (less serialized).
Timer: CPUID frequency unavailable; trying PM Timer...
Timer: trust=1 (0=NONE,1=REL,2=ABS), TSC=2097506845 Hz
Timer: init done
Kernel heap initialized.
Heap statistics:
Total bytes: 536870872
Free bytes: 536870872
Used bytes: 0
Peak bytes: 0
Heap base addr: 24641536
Heap end addr: 561512448
Heartbeat: init...
APIC Timer: calibrating...
APIC Timer: apic_hz=1009032821, tick_hz=100, initial_count=10090328
APIC Timer: configured (masked, ready to start)
Heartbeat: init done
Kernel initialization complete.
Boot successful!
Boot disk: not a StarshipOS stick
System: StarForth v4 (this build's default)
Stadium: 83886 cells (5242 KB), 50 VM slots
Switch-signal: 50 slots
Kernel-Hermes: 50 channel slots
Kernel-Hermes: 50 pending-queue slots
StarForth v4: Hera, born in the kernel's fabric
V4: capsule v4:sys:map-64.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:map-64.f18 capsule_hash=0x81bda2bfcf496f6a
V4: capsule v4:sys:core.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:core.f18 capsule_hash=0x0f415502fccc3fba
V4: capsule v4:sys:input.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:input.f18 capsule_hash=0x0f13c3f9d5fd07fc
V4: capsule v4:sys:dict.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:dict.f18 capsule_hash=0xe3453808afd5a0af
V4: capsule v4:sys:codegen.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:codegen.f18 capsule_hash=0x36d2ae84d2911b90
V4: capsule v4:sys:compile.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:compile.f18 capsule_hash=0xbef95acf00cb404a
V4: capsule v4:sys:quit.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:quit.f18 capsule_hash=0x7fa7a7668b6bf1ed
V4: capsule v4:sys:forth.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:forth.f18 capsule_hash=0xc4c0ad315c95eda4
V4: capsule v4:sys:numout.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:numout.f18 capsule_hash=0xca0fb0f9c1589e20
V4: capsule v4:sys:words.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:words.f18 capsule_hash=0x2f4e5f7f3e7f736f
V4: capsule v4:sys:system.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:system.f18 capsule_hash=0xfe257eb084c43a5d
V4: capsule v4:sys:qmath.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:qmath.f18 capsule_hash=0xa93783c2c8f9b7db
V4: capsule v4:sys:blocks.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:blocks.f18 capsule_hash=0x09d361dbe6174236
V4: capsule v4:sys:log.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:log.f18 capsule_hash=0x544cd004233dff62
V4: capsule v4:sys:acl.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:acl.f18 capsule_hash=0x5ceb5b43b0c5fbb1
V4: capsule v4:sys:end.f18 signature: missing (unsigned)
PARITY:V4_F18 name=v4:sys:end.f18 capsule_hash=0x22eea18b132f8faf
PARITY:V4_ROM words=2383 rom_hash=0xd858ef412d684f92 instructions=63864013
V4: capsule v4:forth79.4th signature: missing (unsigned)
PARITY:V4_CAPSULE name=v4:forth79.4th capsule_id=0x4609d6ef54166ef8 capsule_hash=0x4609d6ef54166ef8 dict_hash=0xbfcb975ac5a745f2
V4: capsule v4:starshipos.4th signature: missing (unsigned)
PARITY:V4_CAPSULE name=v4:starshipos.4th capsule_id=0x1734a8f4fe7483a5 capsule_hash=0x1734a8f4fe7483a5 dict_hash=0x75401e63fcca3f0d
V4: capsule v4:centre.4th signature: missing (unsigned)
PARITY:V4_CAPSULE name=v4:centre.4th capsule_id=0x53b1e3df644e8e25 capsule_hash=0x53b1e3df644e8e25 dict_hash=0xc22f69bd157a4a70
V4: capsule v4:hera.4th signature: missing (unsigned)
PARITY:V4_CAPSULE name=v4:hera.4th capsule_id=0x78730b1d6effe892 capsule_hash=0x78730b1d6effe892 dict_hash=0x17a3406cec07df1e
V4: capsule v4:physics.4th signature: missing (unsigned)
PARITY:V4_CAPSULE name=v4:physics.4th capsule_id=0x5b0195fc30828bde capsule_hash=0x5b0195fc30828bde dict_hash=0xf547cf4d6ad5de38
PARITY:V4_POST tests=990 pass=990 fail=0
PARITY:V4_SYSTEM word_count=405 dict_hash=0x0ffb1d31c4aa7857
V4: capsule v4:init.4th signature: missing (unsigned)
V4: capsule v4:ACL.4th signature: missing (unsigned)
INFO: ACL: active
PARITY:V4_CAPSULE name=v4:init.4th capsule_id=0x13fe8932fa4d2934 capsule_hash=0x13fe8932fa4d2934 dict_hash=0xbf5e6cc6fde06a08
PARITY:OK
POST: PASSED
PCI: init...
PCI: ECAM mapped (amd64)
virtio-rng: no device on PCI bus 0
rng: backend = rdrand
entropy: ready
virtio-input: no device on PCI bus 0
Starting heartbeat...
APIC Timer: started (LVT=0x00020020 ICR=10090328)
I/O APIC: keyboard IRQ1 unmasked
Heartbeat running.
Stadium opcodes: 31 resident, hottest opcode 8
Stadium words: promotions=269 evictions=0
Stadium conservation: resident_sum=43679 reservoir=21857 sum=65536 (Q48_ONE=65536)
Stadium conservation: CONSERVED
Stadium quota grant self-test: OK
Hera reservoir=21857
test-vm reservoir=65536
Heartbeat: 3 ticks, trust=0x00010000, variance=0x00000000
blkio_usb: MSC device ready
Artemis: the stick's partition attached
[Hera] Zuse: genesis minted onto attached thumbdrive
[zuse@Hera] ok> 3 4 + .
[zuse@Hera] 7 ok
[zuse@Hera] ok> NODE-ME .
[zuse@Hera] 0 ok
[zuse@Hera] ok> 11 2 2 BIRTH .
[zuse@Hera] V4: capsule v4:forth79.4th signature: missing (unsigned)
[zuse@Hera] PARITY:V4_BIRTH node=11 dict_hash=0xc8c659cdee409171
[zuse@Hera] 1 ok
[zuse@Hera] ok> S" 6 7 * ." 11 SEND 11 AWAIT .
[zuse@Hera] 42 1 ok
[zuse@Hera] ok> 11 KILL
[zuse@Hera] Stadium words: promotions=301 evictions=0
[zuse@Hera] Stadium conservation: resident_sum=115 reservoir=65421 sum=65536 (Q48_ONE=65536)
[zuse@Hera] Stadium conservation: CONSERVED
[zuse@Hera] ok
[zuse@Hera] ok> 11 2 2 BIRTH .
[zuse@Hera] V4: capsule v4:forth79.4th signature: missing (unsigned)
[zuse@Hera] PARITY:V4_BIRTH node=11 dict_hash=0xc8c659cdee409171
[zuse@Hera] 1 ok
[zuse@Hera] ok> S" VARIABLE N1 : SPIN BEGIN 1 N1 +! AGAIN ;" 11 SEND 11 AWAIT .
[zuse@Hera] 1 ok
[zuse@Hera] ok> S" SPIN" 11 SEND
[zuse@Hera] ok
[zuse@Hera] ok> 3 4 + .
[zuse@Hera] 7 ok
[zuse@Hera] ok> 11 KILL
[zuse@Hera] Stadium words: promotions=306 evictions=0
[zuse@Hera] Stadium conservation: resident_sum=168 reservoir=65368 sum=65536 (Q48_ONE=65536)
[zuse@Hera] Stadium conservation: CONSERVED
[zuse@Hera] ok
[zuse@Hera] ok> 
@@ -0,0 +1,20 @@
LOG: logs/20261119-140436/amd64/qemu-amd64-20261119-140436.log
PASS: POST: PASSED
PASS: Boot disk: not a StarshipOS stick (an ISO or ESP boot)
PASS: Zuse: genesis minted onto attached thumbdrive (a fresh data stick)
PASS: the Stadium: its cells allocated
PASS: the Stadium: conservation CONSERVED
PASS: the heartbeat: ticking
PASS: the Stadium: Hera's words admitted after POST
PASS: [zuse@Hera] ok>
PASS: 7 ok, and a prompt
PASS: NODE-ME: Hera is at place 0 of the kernel's fabric
PASS: BIRTH: node 11 born from Hera, its parity recorded
PASS: node 11 answers Hera: 42, and its text completed
PASS: KILL: node 11 removed, the Stadium CONSERVED after
PASS: after a kill, 11 is born again
PASS: node 11 is given SPIN
PASS: Hera's line ends, though node 11 runs for ever
PASS: and the prompt answers while it runs: 7 ok
PASS: a node running for ever is killed, the Stadium CONSERVED after
RESULT: PASS
+269
View File
@@ -0,0 +1,269 @@
CC (loader) v4/src/exec.c
V4ROM capsules/v4/rom -> build/amd64/kernel/v4_rom_64.c build/amd64/kernel/v4_map_64.c build/amd64/kernel/v4_mesh_rom_64.c
CC (loader) v4/system/mesh.c
CC (kernel) v3/src/blkio_ram.c
CC (kernel) v3/src/block_subsystem.c
CC (kernel) v3/src/compudynamics.c
CC (kernel) v3/src/dictionary_heat_optimization.c
CC (kernel) v3/src/dictionary_management.c
CC (kernel) v3/src/heartbeat_export.c
CC (kernel) v3/src/inference_engine.c
CC (kernel) v3/src/io.c
CC (kernel) v3/src/math_portable.c
CC (kernel) v3/src/memory_management.c
CC (kernel) v3/src/physics_execution_hooks.c
CC (kernel) v3/src/physics_hotwords_cache.c
CC (kernel) v3/src/physics_metadata.c
CC (kernel) v3/src/physics_pipelining_metrics.c
CC (kernel) v3/src/physics_runtime.c
CC (kernel) v3/src/profiler.c
CC (kernel) v3/src/rolling_window_of_truth.c
CC (kernel) v3/src/ssm_jacquard.c
CC (kernel) v3/src/stack_management.c
CC (kernel) v3/src/vm_api.c
CC (kernel) v3/src/vm_debug.c
CC (kernel) v3/src/word_registry.c
CC (kernel) v3/src/word_source/acl_words.c
CC (kernel) v3/src/word_source/arithmetic_words.c
CC (kernel) v3/src/word_source/block_words.c
CC (kernel) v3/src/word_source/control_words.c
CC (kernel) v3/src/word_source/defer_words.c
CC (kernel) v3/src/word_source/defining_words.c
CC (kernel) v3/src/word_source/dictionary_heat_diagnostic_words.c
CC (kernel) v3/src/word_source/dictionary_manipulation_words.c
CC (kernel) v3/src/word_source/dictionary_words.c
CC (kernel) v3/src/word_source/double_words.c
CC (kernel) v3/src/word_source/editor_words.c
CC (kernel) v3/src/word_source/format_words.c
CC (kernel) v3/src/word_source/framebuffer_words.c
CC (kernel) v3/src/word_source/inference_words.c
CC (kernel) v3/src/word_source/io_words.c
CC (kernel) v3/src/word_source/keyboard_words.c
CC (kernel) v3/src/word_source/lifecycle_words_hosted.c
CC (kernel) v3/src/word_source/log_words.c
CC (kernel) v3/src/word_source/logical_words.c
CC (kernel) v3/src/word_source/memory_words.c
CC (kernel) v3/src/word_source/mixed_arithmetic_words.c
CC (kernel) v3/src/word_source/physics_benchmark_words.c
CC (kernel) v3/src/word_source/physics_diagnostic_words.c
CC (kernel) v3/src/word_source/physics_freeze_words.c
CC (kernel) v3/src/word_source/physics_pipelining_diagnostic_words.c
CC (kernel) v3/src/word_source/q48_words.c
CC (kernel) v3/src/word_source/return_stack_words.c
CC (kernel) v3/src/word_source/scroll_words.c
CC (kernel) v3/src/word_source/stack_words.c
CC (kernel) v3/src/word_source/starforth_words.c
CC (kernel) v3/src/word_source/string_words.c
CC (kernel) v3/src/word_source/system_words.c
CC (kernel) v3/src/word_source/ttf_words.c
CC (kernel) v3/src/word_source/vocabulary_words.c
CC (kernel) v3/src/test_runner/test_common.c
CC (kernel) v3/src/test_runner/test_contracts.c
CC (kernel) v3/src/test_runner/test_runner.c
CC (kernel) v3/src/test_runner/modules/acl_words_test.c
CC (kernel) v3/src/test_runner/modules/arithmetic_words_test.c
CC (kernel) v3/src/test_runner/modules/block_words_test.c
CC (kernel) v3/src/test_runner/modules/control_words_test.c
CC (kernel) v3/src/test_runner/modules/defining_words_tests.c
CC (kernel) v3/src/test_runner/modules/dictionary_manipulation_words_test.c
CC (kernel) v3/src/test_runner/modules/dictionary_words_test.c
CC (kernel) v3/src/test_runner/modules/double_words_test.c
CC (kernel) v3/src/test_runner/modules/format_words_test.c
CC (kernel) v3/src/test_runner/modules/inference_words_test.c
CC (kernel) v3/src/test_runner/modules/integration_tests.c
CC (kernel) v3/src/test_runner/modules/io_words_test.c
CC (kernel) v3/src/test_runner/modules/logical_words_test.c
CC (kernel) v3/src/test_runner/modules/mama_forth_words_test.c
CC (kernel) v3/src/test_runner/modules/memory_words_test.c
CC (kernel) v3/src/test_runner/modules/mixed_arithmetic_words_test.c
CC (kernel) v3/src/test_runner/modules/physics_freeze_words_test.c
CC (kernel) v3/src/test_runner/modules/q48_words_test.c
CC (kernel) v3/src/test_runner/modules/return_stack_words_test.c
CC (kernel) v3/src/test_runner/modules/stack_words_test.c
CC (kernel) v3/src/test_runner/modules/starforth_words_test.c
CC (kernel) v3/src/test_runner/modules/stress_tests.c
CC (kernel) v3/src/test_runner/modules/string_words_test.c
CC (kernel) v3/src/test_runner/modules/system_words_test.c
CC (kernel) v3/src/test_runner/modules/vocabulary_words_test.c
CC (kernel) v4/src/exec.c
CC (kernel) build/amd64/kernel/v4_map_64.c
CC (kernel) v4/system/mesh.c
MKCAP capsules -> build/amd64/kernel/capsule_generated.c
mkcapsule: scanning capsules
[p] zuse.4th (1684 bytes, hash=0x490ded9be257a90b)
[p] font.4th (17688 bytes, hash=0x3f305911500c78f6)
[p] MANIFEST_AUTO.md (11687 bytes, hash=0xe022545a0755960f)
[p] multiuser-doe.4th (3942 bytes, hash=0x22140588ee7c39e6)
[p] hestia:init.4th (891 bytes, hash=0x64e111990fbc45ff)
[p] contrib:README.md (1855 bytes, hash=0x4212e52b927793e7)
[p] ACL.4th (4318 bytes, hash=0xf8890c05c0d8f921)
[p] workload-3.4th (2189 bytes, hash=0x62b7a71576ad1041)
[p] init-l8-diverse.4th (430 bytes, hash=0xaa293201a6c91838)
[p] user-font-demo.4th (1674 bytes, hash=0xce1fd7d1b581a56d)
[p] workload-9.4th (1321 bytes, hash=0x3f2bec73142aa424)
[p] lib.4th (619 bytes, hash=0x4b216635c359ef73)
[p] workload-calib1.4th (304 bytes, hash=0x3b9f2d17b554fabc)
[m] init.4th (669 bytes, hash=0xd09db9461b336431)
[p] workload-1-lite.4th (540 bytes, hash=0x44a7a7e3176dcc8d)
[p] init-l8-stable.4th (278 bytes, hash=0xdc3830f189063a9a)
[p] v4:physics.4th (2953 bytes, hash=0x5b0195fc30828bde)
[p] v4:forth79.4th (1216 bytes, hash=0x4609d6ef54166ef8)
[p] v4:ACL.4th (2103 bytes, hash=0xdba5690fb0ee12a4)
[p] v4:init.4th (756 bytes, hash=0x13fe8932fa4d2934)
[p] v4:sys:log.f18 (4535 bytes, hash=0x544cd004233dff62)
[p] v4:sys:qmath.f18 (8607 bytes, hash=0xa93783c2c8f9b7db)
[p] v4:sys:map-32.f18 (3215 bytes, hash=0x17ad313814d028ff)
[p] v4:sys:blocks.f18 (6112 bytes, hash=0x09d361dbe6174236)
[p] v4:sys:input.f18 (10692 bytes, hash=0x0f13c3f9d5fd07fc)
[p] v4:sys:dict.f18 (13816 bytes, hash=0xe3453808afd5a0af)
[p] v4:sys:forth.f18 (12617 bytes, hash=0xc4c0ad315c95eda4)
[p] v4:sys:quit.f18 (32141 bytes, hash=0x7fa7a7668b6bf1ed)
[p] v4:sys:map-64.f18 (3254 bytes, hash=0x81bda2bfcf496f6a)
[p] v4:sys:codegen.f18 (4999 bytes, hash=0x36d2ae84d2911b90)
[p] v4:sys:acl.f18 (5303 bytes, hash=0x5ceb5b43b0c5fbb1)
[p] v4:sys:core.f18 (24370 bytes, hash=0x0f415502fccc3fba)
[p] v4:sys:system.f18 (10189 bytes, hash=0xfe257eb084c43a5d)
[p] v4:sys:numout.f18 (6641 bytes, hash=0xca0fb0f9c1589e20)
[p] v4:sys:words.f18 (9642 bytes, hash=0x2f4e5f7f3e7f736f)
[p] v4:sys:compile.f18 (23381 bytes, hash=0xbef95acf00cb404a)
[p] v4:sys:end.f18 (1604 bytes, hash=0x22eea18b132f8faf)
[p] v4:starshipos.4th (706 bytes, hash=0x1734a8f4fe7483a5)
[p] v4:hera.4th (1376 bytes, hash=0x78730b1d6effe892)
[p] v4:rom:sym.f18 (5610 bytes, hash=0xbbad5748f5bbf863)
[p] v4:rom:main.f18 (2284 bytes, hash=0x6994f1f1d567e163)
[p] v4:rom:math.f18 (5108 bytes, hash=0x9be63ad87934622f)
[p] v4:rom:dir.f18 (5112 bytes, hash=0x51b069f0623ded16)
[p] v4:rom:num.f18 (2634 bytes, hash=0x08b76f1b058cac17)
[p] v4:rom:pack.f18 (4583 bytes, hash=0x65a944d8eb7de7f2)
[p] v4:rom:word.f18 (12966 bytes, hash=0x9210d6c2ac424d11)
[p] v4:rom:in.f18 (4230 bytes, hash=0x65798bed38a09f0f)
[p] v4:rom:mesh.f18 (449 bytes, hash=0x83723d76b9620c2c)
[p] v4:centre.4th (4140 bytes, hash=0x53b1e3df644e8e25)
[p] README.md (2305 bytes, hash=0x09a684ebdfbeb01c)
[p] block-acl.4th (980 bytes, hash=0xf6cc2a59e3a6734e)
[p] sdk.4th (2295 bytes, hash=0x008fdbbb62c94a3a)
[p] pki:starshipos-intermediate.der (408 bytes, hash=0xb40aab540c19f877)
[p] init-l8-omni.4th (1986 bytes, hash=0x5979e314d6452045)
[p] acl-std79.4th (5040 bytes, hash=0x773bf9209df191d1)
[p] doe-campaign.4th (2369 bytes, hash=0x26fb485e5c9dc6ff)
[p] init-l8-volatile.4th (718 bytes, hash=0x98caabbbd92abac4)
[p] doe.4th (3244 bytes, hash=0xf154616d248e861f)
[p] fabric.4th (10359 bytes, hash=0x9d9489cbeca4099b)
[p] workload-4.4th (469 bytes, hash=0x099619264e650b1c)
[p] init-l8-temporal.4th (363 bytes, hash=0x51abd4c138246651)
[p] workload-5.4th (480 bytes, hash=0x526964c7c9506a11)
[p] fonts:README.md (1846 bytes, hash=0xf628c2b7a49f4d46)
[p] fonts:JetBrainsMono-Regular.ttf (270224 bytes, hash=0xf4b7077dab274e6b)
[p] init-l8-transition.4th (529 bytes, hash=0xbcc1a81976f0a4c9)
[p] workload-2.4th (1321 bytes, hash=0xf113b3d0bcccae47)
[p] workload-1.4th (1041 bytes, hash=0x63e251adb0a03613)
[p] workload-5-lite.4th (468 bytes, hash=0xea0303f38824f254)
[p] workload-0.4th (290 bytes, hash=0x93f86f60aeba8feb)
[p] artemis:init.4th (16782 bytes, hash=0x7ba120e2a6aab239)
[p] MANIFEST.md (35813 bytes, hash=0x9d3a6fdb7415d224)
[p] workload-7.4th (206 bytes, hash=0x02862291387eb7ac)
[p] BLOCK_MAP.md (22886 bytes, hash=0x86df913cdae857c6)
[p] turtle.4th (3254 bytes, hash=0x4d470418ca543365)
[p] workload-8.4th (172 bytes, hash=0x56b7f2f0efa000df)
[p] workload-6.4th (1986 bytes, hash=0x06fc0ce1e369ef5a)
mkcapsule: 76 capsule(s) collected
CC (loader) v3/src/blkio_ram.c
CC (loader) v3/src/block_subsystem.c
CC (loader) v3/src/compudynamics.c
mkcapsule: wrote build/amd64/kernel/capsule_generated.c
MKCAP capsules -> capsules/BLOCK_MAP.md
mkcapsule: manifest written to capsules/BLOCK_MAP.md (42 capsule(s))
CC (loader) v3/src/dictionary_heat_optimization.c
CC (loader) v3/src/dictionary_management.c
CC (loader) v3/src/heartbeat_export.c
CC (loader) v3/src/inference_engine.c
CC (loader) v3/src/io.c
CC (loader) v3/src/math_portable.c
CC (loader) v3/src/memory_management.c
CC (loader) v3/src/physics_execution_hooks.c
CC (loader) v3/src/physics_hotwords_cache.c
CC (loader) v3/src/physics_metadata.c
CC (loader) v3/src/physics_pipelining_metrics.c
CC (loader) v3/src/physics_runtime.c
CC (loader) v3/src/profiler.c
CC (loader) v3/src/rolling_window_of_truth.c
CC (loader) v3/src/ssm_jacquard.c
CC (loader) v3/src/stack_management.c
CC (loader) v3/src/vm_api.c
CC (loader) v3/src/vm_debug.c
CC (loader) v3/src/word_registry.c
CC (loader) v3/src/word_source/acl_words.c
CC (loader) v3/src/word_source/arithmetic_words.c
CC (loader) v3/src/word_source/block_words.c
CC (loader) v3/src/word_source/control_words.c
CC (loader) v3/src/word_source/defer_words.c
CC (loader) v3/src/word_source/defining_words.c
CC (loader) v3/src/word_source/dictionary_heat_diagnostic_words.c
CC (loader) v3/src/word_source/dictionary_manipulation_words.c
CC (loader) v3/src/word_source/dictionary_words.c
CC (loader) v3/src/word_source/double_words.c
CC (loader) v3/src/word_source/editor_words.c
CC (loader) v3/src/word_source/format_words.c
CC (loader) v3/src/word_source/framebuffer_words.c
CC (loader) v3/src/word_source/inference_words.c
CC (loader) v3/src/word_source/io_words.c
CC (loader) v3/src/word_source/keyboard_words.c
CC (loader) v3/src/word_source/lifecycle_words_hosted.c
CC (loader) v3/src/word_source/log_words.c
CC (loader) v3/src/word_source/logical_words.c
CC (loader) v3/src/word_source/memory_words.c
CC (loader) v3/src/word_source/mixed_arithmetic_words.c
CC (loader) v3/src/word_source/physics_benchmark_words.c
CC (loader) v3/src/word_source/physics_diagnostic_words.c
CC (loader) v3/src/word_source/physics_freeze_words.c
CC (loader) v3/src/word_source/physics_pipelining_diagnostic_words.c
CC (loader) v3/src/word_source/q48_words.c
CC (loader) v3/src/word_source/return_stack_words.c
CC (loader) v3/src/word_source/scroll_words.c
CC (loader) v3/src/word_source/stack_words.c
CC (loader) v3/src/word_source/starforth_words.c
CC (loader) v3/src/word_source/string_words.c
CC (loader) v3/src/word_source/system_words.c
CC (loader) v3/src/word_source/ttf_words.c
CC (loader) v3/src/word_source/vocabulary_words.c
CC (loader) v3/src/test_runner/test_common.c
CC (loader) v3/src/test_runner/test_contracts.c
CC (loader) v3/src/test_runner/test_runner.c
CC (loader) v3/src/test_runner/modules/acl_words_test.c
CC (loader) v3/src/test_runner/modules/arithmetic_words_test.c
CC (loader) v3/src/test_runner/modules/block_words_test.c
CC (loader) v3/src/test_runner/modules/control_words_test.c
CC (loader) v3/src/test_runner/modules/defining_words_tests.c
CC (loader) v3/src/test_runner/modules/dictionary_manipulation_words_test.c
CC (loader) v3/src/test_runner/modules/dictionary_words_test.c
CC (loader) v3/src/test_runner/modules/double_words_test.c
CC (loader) v3/src/test_runner/modules/format_words_test.c
CC (loader) v3/src/test_runner/modules/inference_words_test.c
CC (loader) v3/src/test_runner/modules/integration_tests.c
CC (loader) v3/src/test_runner/modules/io_words_test.c
CC (loader) v3/src/test_runner/modules/logical_words_test.c
CC (loader) v3/src/test_runner/modules/mama_forth_words_test.c
CC (loader) v3/src/test_runner/modules/memory_words_test.c
CC (loader) v3/src/test_runner/modules/mixed_arithmetic_words_test.c
CC (loader) v3/src/test_runner/modules/physics_freeze_words_test.c
CC (loader) v3/src/test_runner/modules/q48_words_test.c
CC (loader) v3/src/test_runner/modules/return_stack_words_test.c
CC (loader) v3/src/test_runner/modules/stack_words_test.c
CC (loader) v3/src/test_runner/modules/starforth_words_test.c
CC (loader) v3/src/test_runner/modules/stress_tests.c
CC (loader) v3/src/test_runner/modules/string_words_test.c
CC (loader) v3/src/test_runner/modules/system_words_test.c
CC (loader) v3/src/test_runner/modules/vocabulary_words_test.c
CC (loader) build/amd64/kernel/v4_map_64.c
CC build/amd64/kernel/capsule_generated.c
CC (kernel) build/amd64/kernel/capsule_generated.c
LD (kernel) build/amd64/kernel/starkernel_kernel.elf
ld: warning: build/amd64/kernel/obj/kernel/arch/amd64/switch.o: missing .note.GNU-stack section implies executable stack
ld: NOTE: This behaviour is deprecated and will be removed in a future version of the linker
Kernel built: build/amd64/kernel/starkernel_kernel.elf
LD (loader PE) build/amd64/kernel/starkernel_loader.efi
Loader built: build/amd64/kernel/starkernel_loader.efi
StarKernel built successfully for amd64
Loader: build/amd64/kernel/starkernel_loader.efi
Kernel: build/amd64/kernel/starkernel_kernel.elf
rc=0
@@ -0,0 +1,4 @@
[ASan+UBSan mesh boot, V4_CELL_BITS=64]
v4 mesh boot: V4_CELL_BITS=64
PARITY:V4_POST tests=990 pass=990 fail=0
120 checks, 0 failures
+2
View File
@@ -0,0 +1,2 @@
3112 checks, 0 failures
1360 checks, 0 failures
+272
View File
@@ -0,0 +1,272 @@
[V4_CELL_BITS=32 run-32-test_asm.c]
v4 asm tests: V4_CELL_BITS=32
32 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_cells.c]
v4 single-cell word tests: V4_CELL_BITS=32
code: 99 of 1024 words
NIP headroom: data 7 below canary, return 7 below its return address
SWAP headroom: data 6 below canary, return 6 below its return address
ROT headroom: data 5 below canary, return 4 below its return address
-ROT headroom: data 5 below canary, return 5 below its return address
?DUP headroom: data 7 below canary, return 8 below its return address
+! headroom: data 7 below canary, return 8 below its return address
-! headroom: data 7 below canary, return 8 below its return address
2@ headroom: data 7 below canary, return 8 below its return address
2! headroom: data 6 below canary, return 6 below its return address
- headroom: data 6 below canary, return 8 below its return address
MIN headroom: data 3 below canary, return 6 below its return address
MAX headroom: data 3 below canary, return 6 below its return address
OR headroom: data 6 below canary, return 8 below its return address
0> headroom: data 8 below canary, return 8 below its return address
<> headroom: data 7 below canary, return 8 below its return address
< headroom: data 5 below canary, return 7 below its return address
> headroom: data 5 below canary, return 6 below its return address
<= headroom: data 5 below canary, return 6 below its return address
>= headroom: data 5 below canary, return 6 below its return address
U< headroom: data 5 below canary, return 7 below its return address
WITHIN headroom: data 3 below canary, return 5 below its return address
21420 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_console.c]
v4 console tests: V4_CELL_BITS=32, capture 4096 characters
312 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_dump.c]
test_dump: 15 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_exec.c]
v4 exec tests: V4_CELL_BITS=32
3109 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_fabric.c]
v4 fabric tests: V4_CELL_BITS=32, 8 ports to a node
334 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_fabric_walk.c]
v4 fabric walk tests
13 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_foundation.c]
v4 foundation tests: V4_CELL_BITS=32
code: 949 of 1024 words
Q.+ random cases that overflow Q48.16: 2682 of 20000
Q.> as written (SWAP D<): 11702 wrong of 20169
(UQ/) cases run: 8687
UM* headroom: data 5 below canary, return 6 below its return address
UM/MOD headroom: data 5 below canary, return 6 below its return address
ABS headroom: data 7 below canary, return 7 below its return address
U> headroom: data 5 below canary, return 5 below its return address
D+ headroom: data 5 below canary, return 5 below its return address
DNEGATE headroom: data 6 below canary, return 7 below its return address
DABS headroom: data 6 below canary, return 6 below its return address
M+ headroom: data 5 below canary, return 4 below its return address
M- headroom: data 4 below canary, return 5 below its return address
M* headroom: data 5 below canary, return 4 below its return address
M/MOD headroom: data 4 below canary, return 3 below its return address
MOD headroom: data 4 below canary, return 2 below its return address
*/MOD headroom: data 4 below canary, return 2 below its return address
*/ headroom: data 4 below canary, return 2 below its return address
D0< headroom: data 7 below canary, return 7 below its return address
D2* headroom: data 6 below canary, return 7 below its return address
D2/ headroom: data 7 below canary, return 7 below its return address
2ROT headroom: data 2 below canary, return 1 below its return address
D- headroom: data 4 below canary, return 4 below its return address
D0= headroom: data 6 below canary, return 7 below its return address
D= headroom: data 4 below canary, return 3 below its return address
< headroom: data 5 below canary, return 7 below its return address
= headroom: data 7 below canary, return 7 below its return address
D< headroom: data 3 below canary, return 3 below its return address
(D<) headroom: data 2 below canary, return 5 below its return address
2SWAP headroom: data 4 below canary, return 4 below its return address
2OVER headroom: data 2 below canary, return 3 below its return address
DMAX headroom: data 2 below canary, return 4 below its return address
DMIN headroom: data 2 below canary, return 4 below its return address
Q.> (2SWAP D<) headroom: data 3 below canary, return 2 below its return address
Q.* headroom: data 2 below canary, return 3 below its return address
(UQ/) headroom: data 3 below canary, return 4 below its return address
Q./ headroom: data 2 below canary, return 3 below its return address
Q.EXP headroom: data 2 below canary, return 2 below its return address
Q.SQRT headroom: data 2 below canary, return 2 below its return address
Q.LOG headroom: data 2 below canary, return 2 below its return address
(Q.REDUCE) headroom: data 4 below canary, return 5 below its return address
Q.SIN headroom: data 2 below canary, return 2 below its return address
Q.COS headroom: data 2 below canary, return 2 below its return address
LSHIFT headroom: data 6 below canary, return 5 below its return address
RSHIFT headroom: data 6 below canary, return 5 below its return address
C@ headroom: data 7 below canary, return 7 below its return address
C! headroom: data 6 below canary, return 7 below its return address
SM/REM headroom: data 4 below canary, return 3 below its return address
/MOD headroom: data 4 below canary, return 2 below its return address
/ headroom: data 4 below canary, return 2 below its return address
* headroom: data 5 below canary, return 5 below its return address
1023754 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_guard.c]
v4 guard tests: V4_CELL_BITS=32, data bound 1, return bound 1
60 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_heat.c]
v4 heat tests: V4_CELL_BITS=32
67 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_blocks.c]
v4 block request tests: V4_CELL_BITS=32, V4_NODE_WORDS=32768
52 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_codegen.c]
v4 host code generator tests: V4_CELL_BITS=32, V4_NODE_WORDS=32768
code: 1728 words
856 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_compile.c]
v4 host compiler tests: V4_CELL_BITS=32, V4_NODE_WORDS=32768
capsule: 4562 words
a line may have 270 values on the stack while the interpreter reads its next word
a word run from the interpreter has 29 return entries to itself
defining and running a word leaves 1017 data cells under it untouched
1096 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_depth.c]
v4 mesh depth tests: V4_CELL_BITS=32, V4_NODE_WORDS=32768
a text that prints 1012..1024 values: works to 1020, then a stack error and nothing else; calls: works to 23 deep; 19 worked, 14 clean errors, 0 failures
SEND 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 26 deep; 20 worked, 13 clean errors, 0 failures
SEND with no way 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 27 deep; 21 worked, 12 clean errors, 0 failures
AWAIT answered 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 24 deep; 18 worked, 15 clean errors, 0 failures
AWAIT ended by a GONE 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 24 deep; 18 worked, 15 clean errors, 0 failures
passing on while its text waits for room 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 17 deep; 11 worked, 22 clean errors, 0 failures
AWAIT broken by a line from the console 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 24 deep; 18 worked, 15 clean errors, 0 failures
a refusal while its text waits for room 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 17 deep; 11 worked, 22 clean errors, 0 failures
GONE 1012..1024 values: works to 1019, then a stack error and nothing else; calls: works to 26 deep; 21 worked, 12 clean errors, 0 failures
a spent message refused while its text waits 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 17 deep; 11 worked, 22 clean errors, 0 failures
330 runs: 168 worked, 162 ended in a stack error and nothing else, 0 did neither
397 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_dict.c]
v4 host dictionary tests: V4_CELL_BITS=32, V4_NODE_WORDS=32768
code: 1633 words
300 entries in 2218 cells
FIND headroom: data 1020 below canary, return 28 below its return address
(') headroom: data 1020 below canary, return 28 below its return address
MAKE headroom: data 1020 below canary, return 28 below its return address
, headroom: data 1020 below canary, return 31 below its return address
ALLOT headroom: data 1020 below canary, return 30 below its return address
708 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_input.c]
v4 host input tests: V4_CELL_BITS=32, V4_NODE_WORDS=32768
code: 1108 words
WORD headroom: data 1020 below canary, return 29 below its return address
NUMBER headroom: data 1016 below canary, return 25 below its return address
EXPECT headroom: data 1020 below canary, return 30 below its return address
ENCLOSE headroom: data 1017 below canary, return 28 below its return address
6569 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_mesh.c]
v4 mesh tests: V4_CELL_BITS=32, V4_NODE_WORDS=32768
the flood: 268 sends tried: 2 refused at once, 121 let go on the way, 145 done; 1 of the two texts that set a node sending let go; (LOST) 122, (REFUSED) 124
between texts the nucleus used at most 3 cells of the data stack and 4 entries of the return stack
a node removed or a wire cut: 19983 times in all
244 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_node.c]
v4 host node tests: V4_CELL_BITS=32, V4_NODE_WORDS=32768
45 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_quit.c]
v4 host prompt tests: V4_CELL_BITS=32, V4_NODE_WORDS=32768
capsule: 7426 words
from the prompt, words may call each other 30 deep
1020 values may wait on the stack while the next line is typed and interpreted
defining and running a word from the prompt leaves 1017 data cells under it untouched
.S prints a stack of up to 1018 values; it needs 6 cells free
WORDS: 318 names, longest line 74 columns
1356 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_rom_asm.c]
test_host_rom_asm: 466 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_rom_in.c]
test_host_rom_in: 26 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_rom_math.c]
v4 ROM math tests: V4_CELL_BITS=32
the host ROM: 2383 words; the mesh ROM: 265 words
156 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_rom_nucleus.c]
the ROM assembled the system: 63854391 instructions, 16656301 instruction words, 1.14 s (32-bit cells)
test_host_rom_nucleus: 6 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_rom_num.c]
test_host_rom_num: 31 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_rom_pack.c]
test_host_rom_pack: 7 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_rom_range.c]
test_host_rom_range: 19 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_rom_sym.c]
test_host_rom_sym: 81 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_host_unit.c]
v4 unit tests: V4_CELL_BITS=32, V4_NODE_WORDS=32768
not run at this width: the capsules are the 64-bit products'
[V4_CELL_BITS=32 run-32-test_iword.c]
v4 iword tests: V4_CELL_BITS=32
1763 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_loops.c]
v4 loop tests: V4_CELL_BITS=32
code: 298 of 1024 words
loops run against C: 3008 (1696 more would run past 63 times and were left out)
DO .. LOOP headroom: data 5 below canary, return 6 below its return address
DO .. +LOOP headroom: data 5 below canary, return 6 below its return address
?DO .. LOOP headroom: data 5 below canary, return 6 below its return address
DO .. LEAVE .. LOOP headroom: data 5 below canary, return 6 below its return address
nested DO, I and J headroom: data 5 below canary, return 4 below its return address
3104 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_manage.c]
v4 manage tests: V4_CELL_BITS=32
78 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_node.c]
v4 node tests: V4_CELL_BITS=32, 1024 words
node: 1024 words + 52 head + 52 tail boundary (10.2% overhead)
1078 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_numout.c]
v4 number-output tests: V4_CELL_BITS=32
code: 382 of 1024 words
SPACES headroom: data 6 below canary, return 7 below its return address
. headroom: data 3 below canary, return 2 below its return address
.R headroom: data 3 below canary, return 2 below its return address
U. headroom: data 3 below canary, return 3 below its return address
U.R headroom: data 3 below canary, return 3 below its return address
D. headroom: data 3 below canary, return 2 below its return address
D.R headroom: data 3 below canary, return 2 below its return address
25242 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_pictured.c]
v4 pictured-output tests: V4_CELL_BITS=32
<# #S #> headroom: data 3 below canary, return 3 below its return address
signed picture headroom: data 3 below canary, return 2 below its return address
4716 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_port.c]
v4 port tests: V4_CELL_BITS=32
25 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_printing.c]
v4 printing tests (? Q.PRINT DUMP BASE HLD): V4_CELL_BITS=32
code: 506 of 1024 words
DECIMAL headroom: data 7 below canary, return 8 below its return address
? headroom: data 3 below canary, return 2 below its return address
Q.PRINT headroom: data 3 below canary, return 3 below its return address
DUMP headroom: data 3 below canary, return 4 below its return address
13439 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_stack.c]
v4 stack tests: V4_CELL_BITS=32, data depth 10, return depth 9
exhaustive: 2046 sequences of length <= 10
differential: 200000 ops
730137 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_strings.c]
v4 string tests: V4_CELL_BITS=32
code: 234 of 1024 words
COUNT headroom: data 6 below canary, return 6 below its return address
CMOVE headroom: data 4 below canary, return 5 below its return address
CMOVE> headroom: data 3 below canary, return 5 below its return address
MOVE headroom: data 5 below canary, return 6 below its return address
FILL headroom: data 4 below canary, return 5 below its return address
BLANK headroom: data 4 below canary, return 5 below its return address
-TRAILING headroom: data 5 below canary, return 6 below its return address
COMPARE headroom: data 3 below canary, return 5 below its return address
SEARCH headroom: data 2 below canary, return 5 below its return address
SCAN headroom: data 4 below canary, return 5 below its return address
SKIP headroom: data 4 below canary, return 5 below its return address
16729 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_terminal.c]
v4 terminal-output tests: V4_CELL_BITS=32
KEY headroom: data 8 below canary
EMIT headroom: data 7 below canary, return 8 below its return address
CR headroom: data 7 below canary, return 8 below its return address
TYPE headroom: data 5 below canary, return 6 below its return address
1212 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_text.c]
v4 text assembler tests: V4_CELL_BITS=32
240 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_umul.c]
v4 umul tests: V4_CELL_BITS=32
2009 checks, 0 failures
[V4_CELL_BITS=32 run-32-test_wire.c]
v4 wire tests: V4_CELL_BITS=32, 1024 cells to a queue
112 checks, 0 failures
rc=0
+281
View File
@@ -0,0 +1,281 @@
[V4_CELL_BITS=64 run-64-test_asm.c]
v4 asm tests: V4_CELL_BITS=64
32 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_cells.c]
v4 single-cell word tests: V4_CELL_BITS=64
code: 99 of 1024 words
NIP headroom: data 7 below canary, return 7 below its return address
SWAP headroom: data 6 below canary, return 6 below its return address
ROT headroom: data 5 below canary, return 4 below its return address
-ROT headroom: data 5 below canary, return 5 below its return address
?DUP headroom: data 7 below canary, return 8 below its return address
+! headroom: data 7 below canary, return 8 below its return address
-! headroom: data 7 below canary, return 8 below its return address
2@ headroom: data 7 below canary, return 8 below its return address
2! headroom: data 6 below canary, return 6 below its return address
- headroom: data 6 below canary, return 8 below its return address
MIN headroom: data 3 below canary, return 6 below its return address
MAX headroom: data 3 below canary, return 6 below its return address
OR headroom: data 6 below canary, return 8 below its return address
0> headroom: data 8 below canary, return 8 below its return address
<> headroom: data 7 below canary, return 8 below its return address
< headroom: data 5 below canary, return 7 below its return address
> headroom: data 5 below canary, return 6 below its return address
<= headroom: data 5 below canary, return 6 below its return address
>= headroom: data 5 below canary, return 6 below its return address
U< headroom: data 5 below canary, return 7 below its return address
WITHIN headroom: data 3 below canary, return 5 below its return address
21420 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_console.c]
v4 console tests: V4_CELL_BITS=64, capture 4096 characters
312 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_dump.c]
test_dump: 15 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_exec.c]
v4 exec tests: V4_CELL_BITS=64
3112 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_fabric.c]
v4 fabric tests: V4_CELL_BITS=64, 8 ports to a node
334 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_fabric_walk.c]
v4 fabric walk tests
13 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_foundation.c]
v4 foundation tests: V4_CELL_BITS=64
code: 949 of 1024 words
Q.+ random cases that overflow Q48.16: 2682 of 20000
Q.> as written (SWAP D<): 12834 wrong of 20169
(UQ/) cases run: 9000
UM* headroom: data 5 below canary, return 6 below its return address
UM/MOD headroom: data 5 below canary, return 6 below its return address
ABS headroom: data 7 below canary, return 7 below its return address
U> headroom: data 5 below canary, return 5 below its return address
D+ headroom: data 5 below canary, return 5 below its return address
DNEGATE headroom: data 6 below canary, return 7 below its return address
DABS headroom: data 6 below canary, return 6 below its return address
M+ headroom: data 5 below canary, return 4 below its return address
M- headroom: data 4 below canary, return 5 below its return address
M* headroom: data 5 below canary, return 4 below its return address
M/MOD headroom: data 4 below canary, return 3 below its return address
MOD headroom: data 4 below canary, return 2 below its return address
*/MOD headroom: data 4 below canary, return 2 below its return address
*/ headroom: data 4 below canary, return 2 below its return address
D0< headroom: data 7 below canary, return 7 below its return address
D2* headroom: data 6 below canary, return 7 below its return address
D2/ headroom: data 7 below canary, return 7 below its return address
2ROT headroom: data 2 below canary, return 1 below its return address
D- headroom: data 4 below canary, return 4 below its return address
D0= headroom: data 6 below canary, return 7 below its return address
D= headroom: data 4 below canary, return 3 below its return address
< headroom: data 5 below canary, return 7 below its return address
= headroom: data 7 below canary, return 7 below its return address
D< headroom: data 3 below canary, return 3 below its return address
(D<) headroom: data 2 below canary, return 5 below its return address
2SWAP headroom: data 4 below canary, return 4 below its return address
2OVER headroom: data 2 below canary, return 3 below its return address
DMAX headroom: data 2 below canary, return 4 below its return address
DMIN headroom: data 2 below canary, return 4 below its return address
Q.> (2SWAP D<) headroom: data 3 below canary, return 2 below its return address
Q.* headroom: data 2 below canary, return 3 below its return address
(UQ/) headroom: data 3 below canary, return 4 below its return address
Q./ headroom: data 2 below canary, return 3 below its return address
Q.EXP headroom: data 2 below canary, return 2 below its return address
Q.SQRT headroom: data 2 below canary, return 2 below its return address
Q.LOG headroom: data 2 below canary, return 2 below its return address
(Q.REDUCE) headroom: data 4 below canary, return 5 below its return address
Q.SIN headroom: data 2 below canary, return 2 below its return address
Q.COS headroom: data 2 below canary, return 2 below its return address
LSHIFT headroom: data 6 below canary, return 5 below its return address
RSHIFT headroom: data 6 below canary, return 5 below its return address
C@ headroom: data 7 below canary, return 7 below its return address
C! headroom: data 6 below canary, return 7 below its return address
SM/REM headroom: data 4 below canary, return 3 below its return address
/MOD headroom: data 4 below canary, return 2 below its return address
/ headroom: data 4 below canary, return 2 below its return address
* headroom: data 5 below canary, return 5 below its return address
1024904 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_guard.c]
v4 guard tests: V4_CELL_BITS=64, data bound 1, return bound 1
60 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_heat.c]
v4 heat tests: V4_CELL_BITS=64
67 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_blocks.c]
v4 block request tests: V4_CELL_BITS=64, V4_NODE_WORDS=32768
54 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_codegen.c]
v4 host code generator tests: V4_CELL_BITS=64, V4_NODE_WORDS=32768
code: 1728 words
856 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_compile.c]
v4 host compiler tests: V4_CELL_BITS=64, V4_NODE_WORDS=32768
capsule: 4562 words
a line may have 270 values on the stack while the interpreter reads its next word
a word run from the interpreter has 29 return entries to itself
defining and running a word leaves 1017 data cells under it untouched
1096 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_depth.c]
v4 mesh depth tests: V4_CELL_BITS=64, V4_NODE_WORDS=32768
a text that prints 1012..1024 values: works to 1020, then a stack error and nothing else; calls: works to 23 deep; 19 worked, 14 clean errors, 0 failures
SEND 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 26 deep; 20 worked, 13 clean errors, 0 failures
SEND with no way 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 27 deep; 21 worked, 12 clean errors, 0 failures
AWAIT answered 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 24 deep; 18 worked, 15 clean errors, 0 failures
AWAIT ended by a GONE 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 24 deep; 18 worked, 15 clean errors, 0 failures
passing on while its text waits for room 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 17 deep; 11 worked, 22 clean errors, 0 failures
AWAIT broken by a line from the console 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 24 deep; 18 worked, 15 clean errors, 0 failures
a refusal while its text waits for room 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 17 deep; 11 worked, 22 clean errors, 0 failures
GONE 1012..1024 values: works to 1019, then a stack error and nothing else; calls: works to 26 deep; 21 worked, 12 clean errors, 0 failures
a spent message refused while its text waits 1012..1024 values: works to 1018, then a stack error and nothing else; calls: works to 17 deep; 11 worked, 22 clean errors, 0 failures
330 runs: 168 worked, 162 ended in a stack error and nothing else, 0 did neither
397 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_dict.c]
v4 host dictionary tests: V4_CELL_BITS=64, V4_NODE_WORDS=32768
code: 1633 words
300 entries in 2218 cells
FIND headroom: data 1020 below canary, return 28 below its return address
(') headroom: data 1020 below canary, return 28 below its return address
MAKE headroom: data 1020 below canary, return 28 below its return address
, headroom: data 1020 below canary, return 31 below its return address
ALLOT headroom: data 1020 below canary, return 30 below its return address
708 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_input.c]
v4 host input tests: V4_CELL_BITS=64, V4_NODE_WORDS=32768
code: 1108 words
WORD headroom: data 1020 below canary, return 29 below its return address
NUMBER headroom: data 1016 below canary, return 25 below its return address
EXPECT headroom: data 1020 below canary, return 30 below its return address
ENCLOSE headroom: data 1017 below canary, return 28 below its return address
6569 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_mesh.c]
v4 mesh tests: V4_CELL_BITS=64, V4_NODE_WORDS=32768
the flood: 268 sends tried: 2 refused at once, 121 let go on the way, 145 done; 1 of the two texts that set a node sending let go; (LOST) 122, (REFUSED) 124
between texts the nucleus used at most 3 cells of the data stack and 4 entries of the return stack
a node removed or a wire cut: 26895 times in all
244 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_node.c]
v4 host node tests: V4_CELL_BITS=64, V4_NODE_WORDS=32768
45 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_quit.c]
v4 host prompt tests: V4_CELL_BITS=64, V4_NODE_WORDS=32768
capsule: 7426 words
got: "B ok\nok> A ok\nok> 5 ok\nok> "
wanted: "WARN: ACL: denied 'FOO'\n ERROR\nok> UNKNOWN WORD: 'BAR'\n ERROR\nok> 4 ok\nok> "
FAIL /home/user/LithosAnanke/v4/tests/test_host_quit.c:976: session 187
from the prompt, words may call each other 30 deep
1020 values may wait on the stack while the next line is typed and interpreted
defining and running a word from the prompt leaves 1017 data cells under it untouched
.S prints a stack of up to 1018 values; it needs 6 cells free
got: "B ok\nok> "
wanted: "BWARN: ACL: denied 'FOO'\n ERROR\nok> "
FAIL /home/user/LithosAnanke/v4/tests/test_host_quit.c:1654: that word is refused, interpreted or compiled, and nothing else is
WORDS: 318 names, longest line 74 columns
1360 checks, 2 failures
make: *** [Makefile:358: run-64-test_host_quit.c] Error 1
RC-FAIL test_host_quit.c
[V4_CELL_BITS=64 run-64-test_host_rom_asm.c]
test_host_rom_asm: 472 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_rom_in.c]
test_host_rom_in: 26 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_rom_math.c]
v4 ROM math tests: V4_CELL_BITS=64
the host ROM: 2383 words; the mesh ROM: 265 words
156 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_rom_nucleus.c]
the ROM assembled the system: 63864013 instructions, 16659023 instruction words, 0.98 s (64-bit cells)
test_host_rom_nucleus: 6 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_rom_num.c]
test_host_rom_num: 31 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_rom_pack.c]
test_host_rom_pack: 7 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_rom_range.c]
test_host_rom_range: 19 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_rom_sym.c]
test_host_rom_sym: 81 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_host_unit.c]
v4 unit tests: V4_CELL_BITS=64, V4_NODE_WORDS=32768
after POST and COLD: 212 of the 8302 cells below HERE differ from before POST (the first at 25); dict_hash differs
the four outer nodes: dict_hash=0xc8c659cdee409171
126 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_iword.c]
v4 iword tests: V4_CELL_BITS=64
1763 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_loops.c]
v4 loop tests: V4_CELL_BITS=64
code: 298 of 1024 words
loops run against C: 3008 (1696 more would run past 63 times and were left out)
DO .. LOOP headroom: data 5 below canary, return 6 below its return address
DO .. +LOOP headroom: data 5 below canary, return 6 below its return address
?DO .. LOOP headroom: data 5 below canary, return 6 below its return address
DO .. LEAVE .. LOOP headroom: data 5 below canary, return 6 below its return address
nested DO, I and J headroom: data 5 below canary, return 4 below its return address
3104 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_manage.c]
v4 manage tests: V4_CELL_BITS=64
78 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_node.c]
v4 node tests: V4_CELL_BITS=64, 1024 words
node: 1024 words + 52 head + 52 tail boundary (10.2% overhead)
1078 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_numout.c]
v4 number-output tests: V4_CELL_BITS=64
code: 382 of 1024 words
SPACES headroom: data 6 below canary, return 7 below its return address
. headroom: data 3 below canary, return 2 below its return address
.R headroom: data 3 below canary, return 2 below its return address
U. headroom: data 3 below canary, return 3 below its return address
U.R headroom: data 3 below canary, return 3 below its return address
D. headroom: data 3 below canary, return 2 below its return address
D.R headroom: data 3 below canary, return 2 below its return address
25242 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_pictured.c]
v4 pictured-output tests: V4_CELL_BITS=64
<# #S #> headroom: data 3 below canary, return 3 below its return address
signed picture headroom: data 3 below canary, return 2 below its return address
4716 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_port.c]
v4 port tests: V4_CELL_BITS=64
25 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_printing.c]
v4 printing tests (? Q.PRINT DUMP BASE HLD): V4_CELL_BITS=64
code: 506 of 1024 words
DECIMAL headroom: data 7 below canary, return 8 below its return address
? headroom: data 3 below canary, return 2 below its return address
Q.PRINT headroom: data 3 below canary, return 3 below its return address
DUMP headroom: data 3 below canary, return 4 below its return address
13439 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_stack.c]
v4 stack tests: V4_CELL_BITS=64, data depth 10, return depth 9
exhaustive: 2046 sequences of length <= 10
differential: 200000 ops
730137 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_strings.c]
v4 string tests: V4_CELL_BITS=64
code: 234 of 1024 words
COUNT headroom: data 6 below canary, return 6 below its return address
CMOVE headroom: data 4 below canary, return 5 below its return address
CMOVE> headroom: data 3 below canary, return 5 below its return address
MOVE headroom: data 5 below canary, return 6 below its return address
FILL headroom: data 4 below canary, return 5 below its return address
BLANK headroom: data 4 below canary, return 5 below its return address
-TRAILING headroom: data 5 below canary, return 6 below its return address
COMPARE headroom: data 3 below canary, return 5 below its return address
SEARCH headroom: data 2 below canary, return 5 below its return address
SCAN headroom: data 4 below canary, return 5 below its return address
SKIP headroom: data 4 below canary, return 5 below its return address
16729 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_terminal.c]
v4 terminal-output tests: V4_CELL_BITS=64
KEY headroom: data 8 below canary
EMIT headroom: data 7 below canary, return 8 below its return address
CR headroom: data 7 below canary, return 8 below its return address
TYPE headroom: data 5 below canary, return 6 below its return address
1212 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_text.c]
v4 text assembler tests: V4_CELL_BITS=64
240 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_umul.c]
v4 umul tests: V4_CELL_BITS=64
2808 checks, 0 failures
[V4_CELL_BITS=64 run-64-test_wire.c]
v4 wire tests: V4_CELL_BITS=64, 1024 cells to a queue
112 checks, 0 failures
@@ -0,0 +1,3 @@
[V4_CELL_BITS=64 run-64-test_exec.c]
v4 exec tests: V4_CELL_BITS=64
3112 checks, 0 failures
@@ -0,0 +1,9 @@
/home/user/LithosAnanke/v4/tests/test_exec.c: In function 'test_call_hook_sees_every_call':
/home/user/LithosAnanke/v4/tests/test_exec.c:616:16: error: assignment to 'v4_call_hook' {aka 'void (*)(void *, v4_node *, long int)'} from incompatible pointer type 'v4_cell (*)(void *, v4_node *, v4_cell)' {aka 'long int (*)(void *, v4_node *, long int)'} [-Werror=incompatible-pointer-types]
616 | es.on_call = record_call; es.on_call_ctx = (void *)&seen;
| ^
/home/user/LithosAnanke/v4/tests/test_exec.c:637:16: error: assignment to 'v4_call_hook' {aka 'void (*)(void *, v4_node *, long int)'} from incompatible pointer type 'v4_cell (*)(void *, v4_node *, v4_cell)' {aka 'long int (*)(void *, v4_node *, long int)'} [-Werror=incompatible-pointer-types]
637 | es.on_call = redirect_call; es.on_call_ctx = 0;
| ^
cc1: all warnings being treated as errors
make: *** [Makefile:357: /home/user/LithosAnanke/v4/build/64-test_exec.c] Error 1

Some files were not shown because too many files have changed in this diff Show More