Executable reference runtime · 19/19 Python · 7/7 GAP

A network of microVMs that is itself a microVM.

HoloBox stores a W33 leaf, a 40-child network, and every deeper recursive network in one immutable state grammar. A nested guest can receive a message, execute, and checkpoint without expanding or rewriting its siblings.

105,025,641

internal network VMs at level 6

4,096,000,000

addressable leaf VMs

4,201,025,641

total stateful VMs

uniform node blobs

≤ 2n

W33 line hops for an n-digit route

The implemented object

buildseal image graph

sendroute mailbox value

runexecute addressed guest

forkcopy one digest path

verifyreplay every reachable hash

Each guest state is an incident point–line chamber. The six deterministic panel-transition opcodes are named by behavior: HP0..HP2 hold the point and change the line; HL0..HL2 hold the line and change the point. The small VM ISA also has ADD:<int>, RECV, YIELD, and HALT. The selector order is a declared software chart, not an intrinsic ordering supplied by the geometry.

Exact fresh-transition check. At depth six, delivery of the value 13 creates seven path-state blobs and one content-addressed receipt. Executing the recipient consumes the value, reaches accumulator 13, and creates seven path-state blobs. These are upper bounds for arbitrary writes because a content-identical replay can reuse every key. Every untouched sibling retains its original digest. The checked route takes 12 line transactions, meeting the level-six bound 12 with zero stored next-hop tables. Here one hop is a logical W33 line-bus transaction. BT827's chart-aware lowering remains an 8n budget because it counts three cube and five chart-web moves per digit.

Run it

python3 analysis/holobox.py build --output /tmp/holobox --levels 6 \
  --program RECV,HALT
python3 analysis/holobox.py send /tmp/holobox --source 0/0/0/0/0/0 \
  --target 3/10/17/24/31/38 --message 13 --output /tmp/holobox-message
python3 analysis/holobox.py run /tmp/holobox-message \
  --address 3/10/17/24/31/38 --commit /tmp/holobox-run
python3 analysis/holobox.py verify /tmp/holobox-run

What is inherited, and what is new

BT339 already asserted the 40^n/2n hierarchy; BT350 supplied the network-as-node nested-VM framing; Passes 2642–2644 built a same-port recursive hardware module; and the Witting architecture designed immutable CID containers, WASM/OCI components, policies, receipts, and a Projection Engine. HoloBox does not rename those ideas. It fills their executable-state gap: nested lifecycle, a content-addressed state DAG, mailbox delivery, addressed execution, path-only copy-on-write, and one loader contract at every depth.

Lowering path

Artifact identity: the bundle deliberately follows the OCI image layout and descriptor shape while using W33-specific media types.
Least-authority guest: a future leaf backend can expose the same mailbox/lifecycle contract as a WebAssembly Component.
Hardware-isolated guest: a future adapter can package state around Firecracker snapshots or a Kata sandbox.

Scope boundary. This release is a deterministic Python reference runtime and immutable content graph. “OCI-shaped” does not mean OCI conformance. It provides no Linux namespace, guest kernel, KVM boundary, confidential attestation, portable Firecracker snapshot, adversarial security proof, or measured performance. The finite W33 relations organize state and routing; they do not create isolation by themselves.