OpenLight

Image from the first pilot (archived)

The art of building software has always been about understanding first. The bottleneck is never typing — it's knowing what to build. Misunderstanding compounds. The best work happens when the understanding is clear enough that implementation feels inevitable rather than forced.

Agents now have the capability to participate deeply in that process — reading, reasoning, generating, refactoring. But what makes a session productive is the same thing that has always made software work: the quality of understanding going in. An agent that starts with clear context — structured knowledge, clear types, honest requirements — produces clear work. An agent that starts cold produces plausible noise.

The missing piece is not more capability. It's continuity. Understanding built in one session doesn't carry to the next. The work fragments instead of compounding.

OpenLight is a substrate where understanding persists and compounds. You structure what you know — types, contracts, relationships — in a field that carries its own structure and enforces its own integrity. An agent reads the field and knows what to do. An interface is projected from it. The next session stands on the ground the last one built. A type placed today is a contract an agent reads tomorrow, a surface someone interacts with the day after.

The field grows richer by being worked in.

This is not a knowledge base an agent queries. It is a computing environment — the substrate where knowledge, types, agents, interfaces, and programs all live as one integrated system. A program that reads the filesystem, an agent loop running a completion model, a tile projecting scope onto screen — these are all functions native to the same field, reaching the same contracts, writing back to the same history. The full cycle of a computing environment, not a retrieval layer bolted onto one.

Read in order. Each file below assumes the previous as ground. pilot/ sub-specs and research/ are reference depths — descend only when work calls for them.

inside.md — the values and visions, inside-out. Everything else answers to this.

pilot.md and pilot/ — the substrate contract and the first end-to-end proof. The substrate-and-program shape the values demand. The substrate library lives under pilot/db/.

conventions.md — working principles that shape how the work happens. Short, hard-earned.

board.md — current state, recent decisions, tracked debt. Where the work stands against the pilot's plan.

horizon.md — live ideas being worked on. Not settled into inside.md, not committed in pilot.md. Open directions held deliberately open.

research/ — ecosystem reading, a portrait gallery of software inventors whose work mirrors and pushes back on the values, and the audit trail behind inside.md. Reference depth.