Foundations · 01

Why this exists

Most engineering teams have a process that lives in habit. Ours cannot.

A meaningful share of our work is done by agent sessions that start with no memory of yesterday. A process that lives in habit is a process an agent cannot join — it has nowhere to read it from.

So the process is written down, argued from first principles, and derived rather than accumulated. Every stage, route, and board column on this site follows from six claims. If you want to change the machine, change those.

How to read this. Foundations are the argument. The machine is the shape it produces, on one diagram. The running pages show it alive on a normal day, and the reference pages are the actual semantics and prompts — no summaries, and no redactions beyond credentials.

There is a second effect worth naming: a process an agent can join is also a process a person can join. The same document that lets a fresh session act correctly on its first turn lets a new teammate — or a stranger reading this site — predict what happens to any piece of work here.