Page Roulette

These pages do not exist yet. Each link leads to a doesNotUnderstand response — the server acknowledging a capability gap. Pick one. See what happens.

Intent Algebra

Formal operations on intent specifications — composition, refinement, and contradiction detection

Behavioral Diff

What changed between two versions of a running system, expressed in human terms rather than line-by-line diffs

Semantic Type System

Types defined by meaning rather than structure — “a temperature” is not “an i64” even if both are 64 bits

Self-Repair Log

A live stream of the kernel detecting and fixing its own bugs — every diagnosis, every patch, every rebuild

Intent Debugger

Step through execution at the intent level, not the instruction level — “the sort is comparing elements” rather than “icmp slt i64”

Meaning-Preserving Transforms

Refactoring verified by semantic equivalence rather than test passage — prove the behavior is identical, not just that tests still pass

Pattern Archaeology

Tracing how the kernel’s learned patterns evolved across generations — which survived, which mutated, which went extinct

Trust Boundaries

Where the semantic compiler’s confidence drops below threshold — the map of what it knows it doesn’t know

Collaborative Intent

Multiple humans contributing to a single intent specification — merging what different people mean into one coherent program

IR Cartography

Visual maps of the LLVM IR modules and their semantic relationships — how 50+ modules connect and depend on each other

doesNotUnderstand Cascade

What happens when a system encounters intent it cannot yet compile — the Smalltalk pattern applied recursively

Zero-Dependency Philosophy

Why this entire system has zero external dependencies — and what that means for trust, portability, and understanding

How this works

The semantic compiler’s HTTP server uses a data-driven route table. When a request arrives for a path with no registered handler, handler_dispatch returns -1 — the doesNotUnderstand signal. Right now, that means a styled 404 page. In the future, this is where the kernel would read the semantic intent embedded in the URL, generate an LLVM IR handler via the Claude API, compile it, register it in the route table, and serve the response — all from a single request to a path that did not exist moments before.