I had arrived at the final frontier.

My bare-metal kernel was booting in QEMU, driving NVMe block storage, running multi-agent swarms, and rendering a force-directed canvas. But to make V.E.L.O.C.I.T.Y.-OS a truly next-generation system, I needed to close the loop: the operating system had to be able to evolve and compile itself without human intervention.

The V.E.L.O.C.I.T.Y.-OS 12-Part…

After writing drivers for NVMe storage, my bare-metal kernel could load files and run JIT code. However, I was still typing commands into a text-only COM1 serial terminal. I needed a graphical interface.

Last night, the second agent took over to build a double-buffered visual rendering compositor on top of the UEFI Graphics Output Protocol (GOP) framebuffer.

The V.E.L.O.C.I.T.Y.-OS 12-Part…

With the standalone IDE running, I had a sandboxed environment to write and execute Neural Document Architecture (NDA) programs. However, executing the binary AST via a standard recursive tree-walk interpreter was adding unacceptable dispatch overhead.

Every opcode instruction required match branching, dynamic type checking, and variable lookup cycles. I needed a Just-In-Time (JIT) compiler to…

With the Neural Document Architecture (NDA) binary format defined, the next logical bottleneck was the environment it ran in.

I was building this as a VS Code extension, which meant dealing with TypeScript, JSON-RPC serialization, and Electron's massive memory footprint. VS Code regularly consumes 300MB+ of RAM just idling before you've even opened a file. Worse, parsing JSON text in the agent…

Dev Log 57: 2026-06-21

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Followed through on the April 1 language design plans by building working compilers for both Numlang and Selenium, with parsers, semantic analysis, code generation, and REPLs.

Comments

Comments

Comments

Comments

Comments

Comments