admin/LithosAnanake
1
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

FABRIC-3.8.md: design for real concurrency; stop the serialized DoE campaign

Browse Source 
The per-ISA amd64 campaign (12345 3 S" amd64" DOE) was stopped ~49 min in,
zero trials complete: its harness drives workers by synchronous VM-EXEC on
Hera's stack, so the concurrency factor counted resident VMs while execution
stayed serialized. Tracing further showed the v2.1.0 reshuffle stops short of
real concurrency: kernel-Hermes never publishes eligibility (no mark_work in
sk_hermes_send_one), the switch trampoline is still the Stage-2 placeholder,
delivery to passive VMs still goes through the idle pump, only Tripod/WIREBIND
VMs are switch participants, and the stack-ownership gate is a single global.

FABRIC-3.8.md records the gap analysis and a staged A-I design, each stage its
own commit and 3-arch acceptance. FABRIC-3.md SXXXV.16 points to it. Logs and
extracted CSVs from today's boots and the stopped run are kept as audit
artifacts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Robert Allan James
2026-09-23 13:58:36 -04:00
co-authored by Claude Opus 5.5
parent e40cafcd49
commit 0532c1d8b8
8 changed files with 207431 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
FABRIC-3.md
+12
View File
@@ -5869,3 +5869,15 @@ campaign's first two trials correctly: `run=0 cfg=0 rep=14 nw=2 mode=uniform fai
`run=1 cfg=5 rep=8 nw=8 mode=heterogeneous fail=0`, both `fleet_conserved=1`,
`fleet_k_q48=65536` (exactly Q48.16 1.0) -- clean so far.
### XXXV.16 -- Campaign stopped: the harness was never concurrent. Design moved to `FABRIC-3.8.md`
The amd64 per-ISA campaign (`12345 3 S" amd64" DOE`, `logs/20260923-125936/`) was stopped by
direct instruction 2026-09-23, about 49 minutes in, with zero trials complete. The log and CSV
(`runs/doe-amd64-20260923-125936.csv`) are kept. Cause: `MU-TOUCH-ALL` drives workers by
synchronous `VM-EXEC` on Hera's stack, and `WORKER-BIRTH` VMs aren't switch participants. So the
concurrency factor counted resident VMs while execution stayed serialized (§XIX's null
hypothesis). Tracing further showed the `v2.1.0` reshuffle itself stops short of real
concurrency: kernel-Hermes never publishes eligibility, the switch trampoline is still a
placeholder, and delivery to passive VMs still goes through the idle pump. Full gap analysis and
the staged design are in **`FABRIC-3.8.md`**. No DoE relaunch until its stages land.