TLL OS
A specification-driven, self-hosted language with a pure-TLL compiler, native bytecode VM, and first-class closures. Zero Node.js, zero npm, zero JavaScript in the production chain.
Built to compile itself.
The compiler, type system, and standard library are implemented in TLL. Once the C launcher is built, TLL compiles and runs itself — verified by SHA256 across generations.
Self-Hosting Compiler
Lexer, parser, typechecker, codegen, linker in pure TLL. The compiler compiles itself — deterministically, SHA256-verified across generations.
compiler/*.tllNative Bytecode VM
Register-based VM, 46 frozen opcodes, frame pool, max-register optimization. 357× faster function calls than the naive stack model.
opcode 0–45First-Class Closures
Function values, higher-order functions, mutable capture, shared UpvalueBox, escaping closures. Flat model — no chain lookups.
opcode 42–45Spec-First Architecture
The spec is the single semantic authority. Every VM — C today, Rust/Go/WASM tomorrow — is a conforming implementation.
spec/Zero JS Runtime
No Node.js, npm, TypeScript, or JavaScript in the production chain. C is the only stage-0 — and it only touches OS boundaries.
native-onlyProduction HTTP
Worker-pool HTTP server, file system, JSON, time, process APIs. Dogfooded by an e-commerce platform and a 46k-tick/sec market system.
http.serveThe C spark. The TLL fire.
A C compiler builds tllvm once. From that point, every compilation and every execution is TLL itself.
Write TLL. Be TLL.
Lexical scoping, first-class functions, closures, exceptions, modules. Familiar C-like syntax — semicolons optional.
46 opcodes. One bytecode schema.
The closure model is encoded directly in the instruction set — not a library layer on top.
Start building TLL.
Apache 2.0 · Self-hosting · No JS · Deterministic · 46 opcodes frozen