Machine substrate
UEFI bootstrap, owned memory, paging, traps, interrupts, time, SMP, DMA, update, and recovery. Every native boundary is explicit and fail-closed.
ARCHITECTURE / CLEAN-SHEET BEAM
Small trusted core. Explicit outward power.
The primitive vision was a dense multi-cluster fabric. The final direction is more disciplined: keep resilience, isolation, and dynamic routing; retire decorative governance and unnecessary language layers; make every dependency auditable.
SYSTEM LAYERS
A dependency chain that can be refuted.
Higher layers inherit no authority merely by existing. They earn bounded capabilities from the layer below and remain incomplete until their own evidence gates pass.
active construction
Clean-sheet BEAM core
A fresh loader, terms, interpreter, garbage collection, processes, schedulers, code management, and bounded built-in functions. OTP is a semantic oracle, not a shipping runtime dependency.
Sovereign services
Capability-bound storage, networking, cryptography, distribution, and supervision without Linux, POSIX, or an upstream ERTS underneath BEAM.
Local AI gateway
A usable operator surface for models, tools, data, and policy—packaged for offline-first installation and recovery at the far edge.
NON-NEGOTIABLES
No host hiding below the promise.
- No Linux below BEAM.The release target is bare metal, not a branded Linux appliance.
- No upstream ERTS as the product runtime.Compatibility is proven against an oracle; the shipping core is fresh.
- No inferred acceptance.A neighboring test cannot promote an unrun gate.
- No cloud requirement for useful operation.Networks expand capability; they do not grant local permission.