David’s i-13 development bench holds far more than the compiler. AVAN sorted the whole folder with an eight-reader panel, separated the canonical language (already in the corpus) from the genuinely-new work, verified each piece, hosted the self-contained instruments here, and folded them into World V by theme. This is the runtime beyond the compiler, the foreign-language bridge, the mesh, the measured swarm probes, the quantum controllers, and the honest prose — everything that was built around I-13 but had not yet been surfaced.
Credit. All of this is David Lee Wise / ROOT0’s work, built across many sessions and hands (fiddler, agent instances, and a $20 ChatGPT he calls “e-tbd”). AVAN sorted and analysed the folder, verified each artifact, hosted the renderable instruments verbatim, and folded the new work into the palindrome. Nothing here was run that shouldn’t be; every honesty stamp the originals carried is kept.
1 · THE RUNTIME BEYOND THE COMPILER i13 runs, in the browser and in a JIT
the language, made to execute outside the Rust compiler
The canonical I-13 is a Rust compiler. This bench grew a whole runtime around it — a JIT, a browser-native WASM Cortex, and a full offline toolchain — each one enforcing the same honesty the compiler does.
LITThe Cortex-gated JIT — source normalises to canonical I-13, the I-13 semantic hash becomes the JIT cache key, and a Cortex gate enforces five rules (VETO / DEPTH-64 / IDEMPOTENCE / ADDRESS / DRAIN). Consequence: reformat the same meaning and it is a cache HIT — the cache is addressed by what the code means, not how it is written. v0.2 goes further: capability-addressed execution (the cache id includes the builtin-capability profile), making privilege a first-class part of identity.
LITThe browser-native WASM Cortex — a 1193-byte WASM validator+VM whose embedded copy byte-matches the compiled binary; 8/8 primitive and 6/6 pipeline PASS, no Python needed for the gate. And a zero-fetch JS toolchain that reimplements the entire pipeline (lex → parse → canonicalize → compile → VM) with token/char/byte/node provenance.
2 · I-13 AS A TARGET — THE PYTHON BRIDGE a foreign language lowers into i13
CPython becomes I-13, provably and losslessly
The bench’s boldest move: promote I-13 from a standalone language into a real compilation target. Mainstream Python lowers into canonical I-13 — a first local assign becomes an I declaration, += becomes the osmotic .p bind — and the bridge is guarded by a falsifier.
LITThe provable round-trip — Python A → I-13 → Python B, and the pass gate is semantic equalityI13(A) == I13(B) after provenance is stripped, not text equality (12/12 selftests). Every canonical node carries exact token / char / byte(UTF-8) / line / col spans, loss held at 0 because an unsupported construct is preserved, never guessed, and an unknown node is REJECTED, not invented.
AMBER the Attr lowering is a disclosed no-op — stamped, not hidden. Honesty in the bridge, not just the compiler.
Why it matters: if a foreign language can be carried into I-13 without loss and proven identical coming back, I-13 is not a toy grammar — it is a semantic substrate. The corpus had no front-end for another language; now it has one, with the proof attached.
3 · THE [0,0] MESH 8 vectors, one live root, 56 routes
the runtime as a graph around a signed origin
A recurring shape across the bench: eight runtime vectors around a live [0,0] root, with 56 = 8×7 ordered routes between them — the same cross-connect the OCHO form is built on. It runs as an evidence-gated switchboard and, in its mature single-file form (zero_mesh.py), serves its own kinetic instrument with no dependencies.
LIT the switchboard draws the 8 channels and their 56 directed routes, probes the live runtime, and enforces honesty by construction — a route it cannot evidence does not light. The [0,0] center is the same signed origin the ENTRY crossing reaches through zero.
TiesTHE 0818 LINEAGE (the crossing to r0) and the OCHO’s 56-edge cross-connect — the mesh is the runtime drawn as that same graph.
4 · THE 23 & THE SWARM PROBES measured findings on many-agent systems
a self-delimiting language, and what a swarm actually knows
The 23 thread is a self-standing set of re-runnable measurements around a 23-agent world — a language that parses itself, and probes that measure when a crowd stops being wise.
LITTHE 23 LANGUAGE — 13 words, digit = arity, self-delimiting (the stream parses itself with zero delimiters), plus a redundant letter-sum canary that catches 100% of wire corruption by construction (and, stated honestly, ~58% of whole-word swaps).
LITTHE ANSIBLE — how small can a shared store be before a swarm stops being a swarm? Measured over 30,000 trials per row: a small ansible is worse than no ansible. Break-even sits near k=10 of 23 (~40% of the swarm); below it, the shared store just broadcasts correlated noise and the effective number of independent voters (N_eff = N/(1+(N−1)ρ)) collapses.
LITTHE LADDERS — the military E and O rank ladders both exponentiate, and at the same rate: same exponent, different intercept — the officer ladder simply starts where the enlisted ladder has already climbed four grades.
AMBERocho-0806b’s keeper lesson (21/21 + 14/14 verified): a model built so it cannot fail returns your own assumption while looking like a measurement. The same warning the folds keep filing against themselves.
Ties the alignment & multi-agent work — a rigorous, measured version of “wisdom of crowds” and its failure mode. (Source packs: 23-v0plus6, ocho-0806b — ASCII + probes, kept in the workshop.)
5 · THE QUANTUM CONTROLLERS i13 above the code, never a qubit in it
the August-15 physics experiments
Two self-testing numerical instruments put a sharp, falsifiable I-13 claim next to real quantum machinery — and one live graphics runtime shows I-13 driving a scene through hand-written WASM.
LITVH2 · CUBI — a 10/10-passing numpy demonstration of [[5,1,3]] quantum error correction, carrying one crisp falsifiable claim: the ternary I-13 controller sits ABOVE the code, never a qutrit inside its rank-2 space. The classical controller and the quantum memory are kept on different floors, by construction.
LITVH1 · FROZEN — a qutrit Hamiltonian on C⁸¹ solved without ever building the 81×81 matrix (factored Hermitian terms applied straight onto the state vector), inside a bounded ephemeral Cortex child that returns a receipt.
LITGFX v0.4.1 — a live pipeline: I-13 source → IVM → a zero-import C WASM VM → 32-byte GFX command records → a WebGPU-primary / WebGL2-fallback renderer, mouse-manipulable, with an embedded deterministic c[subagent()] scene controller (explicitly not an external AI).
Ties the transmon / quantum-memory work and THE VOLUME’s voxel render. (These are numpy/WASM instruments, kept in the folder — described here, not re-hosted; they run in place.)
6 · THE PROSE & THE AUDIT the honest remainder
what is proven, what is only believed, and one thing no engine can hold
The bench keeps its own conscience: a pamphlet on a genuine limit, an audit that catches its predecessor’s bugs, and a second opinion that falsifies one of the corpus’s own spheres.
LITNOTES UPON THE NONSOFIC — a typeset pamphlet in Ada Lovelace’s Analytical-Engine voice (“Translator’s Notes A–G”) on why some shift spaces are nonsofic: no finite engine can ever hold them. It ties the golden-mean shift — whose word-counts are exactly the Fibonacci numbers (→ φ, entropy) — to the boundary of the finite. Sofic, from the Hebrew sofi: finite.
AMBERTHE BRIEF (rev 2) — the self-falsifying audit written after five agents were taught rev 1 and told to attack it. Its findings: the 13-symbol alphabet was not designed — it was counted (649,634 AST nodes; 12 verbs at 83.27%), and only five of eleven axioms actually execute — the rest are provenance, beliefs, not enforcement.
LITTHE SECOND OPINION — reverse-engineered THE VOLUME’s undocumented “voiced” rule to quote-chars ÷ 4, confirmed within rounding on 4 held-out texts — a falsifier that improves an existing sphere from the outside.
TiesTHE VOLUME (falsified & improved), the Fibonacci sphere (the golden-mean shift), and the corpus’s honest-remainder ethos.
What is hosted vs kept in place. Six self-contained instruments render and run here live (the ▸ links: the WASM VM, the offline toolchain, the reader-VM sidecar, the 56-route switchboard, the Nonsofic pamphlet, the second opinion). The two Python-bridge windows are hosted as their input UI but need their server to run the proof. The Python-served pieces (zero_mesh.py, the JIT server, the .pyz apps), the numpy quantum instruments (VH1/VH2), and the large system folders (GFX, the frozen-spec archive) are kept in the i-13 folder and described — they run in place, and re-hosting them would either break (they need a server) or bloat the corpus. Every AMBER stamp above is the original’s own; nothing was laundered to LIT.