TempleOS

TempleOS ran everything in ring 0 in one address space, compiled its own language on the fly, and treated the whole machine as one programmable surface. It was dismissed for a long time as a curiosity. The architecture underneath was a serious position about what a personal computer could be when nobody has to be protected from anybody.

The inheritance

Four things here come more or less directly from it.

One address space, one privilege level. The justification differs, because TempleOS wanted immediacy and this wants to remove a boundary that a language model would otherwise cross thousands of times per answer. The consequence is the same, and so are the risks.

A system language that belongs to the system. HolyC was the shell, the scripting language and the compiled language at once. Aiksi occupies the same position here: everything above the kernel is written in it, the shell evaluates it, and stored programs are the same artefacts the machine writes for itself.

The graphics are simple on purpose. A linear framebuffer, a fixed glyph, drawing that anybody can follow. There is no acceleration, and the compositor is a back buffer and a row-span diff.

An oracle. TempleOS drew words from a dictionary seeded by the timing of the operator's own hands. That entropy source is kept here, with keyboard and mouse interrupt timing folded into a sampler. The subject changed.

Where the two diverge

TempleOS was 640x480 at sixteen colours by choice, and this runs at whatever the graphics output protocol offers. TempleOS had no networking, and this has a full stack including TLS. TempleOS compiled HolyC to native code immediately, and Aiksi is a tree walker with a code generator that so far handles integer arithmetic and control flow and refuses everything else.

The largest divergence is the oracle. Drawing random words and reading them as prophecy is the part of TempleOS that cannot be defended on any technical ground. The mechanism here fits a linear dynamical model to real telemetry, heap and task-switch rate and touch rate, then rolls the state forward under three interventions and plots the branches. It is a controlled linear system fitted from measurements. The first draft did generate prophetic words, and it was scrapped for exactly the reason this paragraph gives.

What it got right

That the boundary is a cost as well as a protection, and that a machine which is entirely yours can be organised around immediacy. Most of that argument was dismissed alongside everything else about its author, and most of it holds.

The parts that turned out to be practical rather than only philosophical are the ones this project leans on hardest. A tool call as a function call. A language whose programs are values the system can store, hash and reason about. A screen you can write to without asking anybody. None of those needed the theology, and all of them survive it.