--- title: "AIEN | About the engineer | AienOS" description: "AIEN is a sovereign computing stack built in the open on one machine: AienOS, Omega, the sovereign core runtime and the Spark verification pipeline, gathered into the Aienix core tree." last_updated: "2026-10-26" canonical_url: "https://www.aienos.com/engineer/works/aien/" --- [About the engineer](https://www.aienos.com/engineer/) ## Six parts, one machine Everything runs on a single NVIDIA DGX Spark (Grace Blackwell GB10). The parts are being gathered into one source tree, Aienix, so they move in step and are judged as one. - ### AienOS The operating system Agent-first: the agent is the control plane and the model is never the kernel. - ### Omega Language and GPU engine The language and semantic substrate the stack is being rewritten into, with its own GPU engine for the GB10. - ### Sovereign core Host runtime, in Rust Command line tool and daemon, inference ABI, paged KV cache and scheduler, and the judging pipeline. - ### Architecture Flows and decisions The canonical flows, boundaries and Architecture Decision Records. - ### Protocols Specs and schemas The specifications, wire protocols and schemas. - ### Physics Machine realization The FORGE layer and the boot artefacts that bring the hardware up, with their evidence. ## How a change gets in - ### Pull request Opened in any AIEN repository. - ### Judged on the Spark My own pipeline runs the repository's gates on the real hardware, not a hosted runner. - ### Signed evidence bundle Tied to the exact commit and published with the verdict. - ### Verdict A change merges only when the verdict is PASS. A green hosted check means the bridge ran. It is not the verdict. AIEN is the project I spend my days on. The goal is persistent machine intelligence on a machine I own, with nothing in the trusted base that depends on an outside service, and with every claim the project makes resolving to a command anyone can rerun and an evidence bundle anyone can read. The development machine is a single NVIDIA DGX Spark (Grace Blackwell GB10). I lead the project and decide; AI agents write, test and review as day-to-day collaborators. The architecture, the decision records and the execution plan are public and are the authority for what gets built. ## What the stack is Six parts depend on each other and are the reason the project exists. - AienOS , the operating system. Agent-first: the agent is the control plane, and the model is never the kernel. Its kernel passes its gates in the emulator and has not yet booted on the real machine. - Omega , the language and semantic substrate the stack is being rewritten into, with its own GPU engine for the GB10. No CUDA in the plan. - Sovereign core , the host runtime in Rust: the command line tool and daemon, the inference ABI, the paged KV cache and scheduler, and the pipeline that judges every repository. - Architecture , the canonical flows, boundaries and Architecture Decision Records, and the map from design to implementation. - Protocols , the specifications, wire protocols and schemas. - Physics , the FORGE machine-realization layer and the boot artefacts that bring the hardware up, with their evidence. These are being gathered into one source tree, Aienix , so they move in step and are judged as one. Components that only consume the core are attachments in their own repositories, pinned at the boundary: among them INTERPLANE, the open protocol between models and agent runtimes, and the benchmarks repository that holds every measurement bundle. ## How a change gets in Every pull request in every AIEN repository is judged on the Spark itself, by my own pipeline, not by a hosted runner. The judge runs the repository's gates on the real hardware, signs an evidence bundle tied to the exact commit, and publishes the verdict. A change merges only when that verdict is PASS. A green hosted check means the bridge ran; it is not the verdict. ## What I measure Two rules govern every number the project publishes. - Against my own runs and the ceiling. Speed is reported against the machine's physical limit and against my own previous run. I do not publish comparisons with other people's systems; anyone who wants a comparison can run the published bundle against mine. - Receipts, not promises. A figure appears only when it resolves to a reproducible command and a signed bundle. Figures that predate this standard were withdrawn from this site on 23 September 2026 and live on only in the repository history. The guiding measure is what I call Turing yield: how many held-out bits the system actually learned, what it cost to learn them, and whether that learning made the next discovery easier. The model's standing question is "how do I get more Turing today?" ## Principles - Own the hardware, own the memory, own the code. No metered tokens in the loop. - Build close to the metal. When an outside tool looks tempting, learn how it works and build the native version that fits. - Never hand-roll cryptography or weaken security to stay native. That exception is said out loud. - Open source everything, under Apache-2.0 with the LLVM exception (see [licensing](https://www.aienos.com/licensing/)). - Pre-alpha and honest about it. Nothing on this page is a release or a hardware qualification claim; when a component is qualified on the Spark, the bundle that proves it will be linked. ## Where to look - The project site, with the live state of every component: [aienos.com](https://www.aienos.com/) - The core tree and the map of repositories: [Aienix](https://github.com/aien-dev/aienix) - The organisation on GitHub: [aien-dev](https://github.com/aien-dev) - The protocol between models and runtimes: [interplane.io](https://interplane.io/) ## AIEN today This block is not typed by hand. It is read from the record [facts.json](https://www.aienos.com/facts.json) that this site gathers from GitHub every hour, when the page is built. NO VERDICT Spark judge, sovereign core Verdict for commit f30eb96 of the host runtime: The Spark has not published a verdict for this commit yet.. Component Last merged change Open proposals [Aienux](https://github.com/aien-dev/aienux) [docs: point aienux links at aien-dev/aienux (aienos becomes the distribution repo)](https://github.com/aien-dev/aienux/pull/460) 22 [Omega](https://github.com/aien-dev/omega) [fix(omc): saturating float-to-int casts; consts after a fn stay visible](https://github.com/aien-dev/omega-mv/pull/815) 76 [Sovereign core](https://github.com/aien-dev/aien-sovereign-core) [docs: point aienux links at aien-dev/aienux (aienos becomes the distribution repo)](https://github.com/aien-dev/aien-sovereign-core-mv/pull/775) 43 [Architecture](https://github.com/aien-dev/aien-architecture) [sanitize: alpha-testing hygiene (paths, hosts, emails, licence, labels)](https://github.com/aien-dev/aien-architecture-mv/pull/334) 11 [Protocols](https://github.com/aien-dev/aien-protocols) [fix(protocols): frame signed grant and evaluation digests (SECNET-02)](https://github.com/aien-dev/aien-protocols-mv/pull/59) 3 [Physics](https://github.com/aien-dev/physics) [sanitize: alpha-testing hygiene (paths, hosts, emails, licence, labels)](https://github.com/aien-dev/physics-mv/pull/89) 1 Record generated 2026-10-26T18:06:30Z. ## Sitemap See the full [sitemap](https://www.aienos.com/sitemap.md) for every page on aienos.com.