Continuum, in full
The landing page is the short answer. This is the long one: how the line runs, what it is made of, and how to check it.
The discipline this workstation is built for: five claims about working above the editor, and the mechanism where each one becomes something a directory can prove.
read → How it worksThe line, stage by stage: capture, refine, briefs, queue, implement, verify. Then the six mechanisms that stop living in the operator, each with the surface that implements it.
read → ArchitectureThree planes. State is a file, not a claim. Why there is no database, no server and no account, and what that buys.
read → EvidenceThe ledger, the scoreboard, the paper trail a task leaves behind, one run end to end, and the software shipped through the line.
read → VocabularyEvery named thing in Continuum, defined once: signal, brief, mode, gate, receipt, NEEDS YOU, ledger, scoreboard, regent, governor, substrate, gradient.
read → GradientsThe open-source behavioral standards layer: arché, shodo, kinhin, zazen. The part of Continuum you can run today.
read →Cursor, Claude Code and Copilot write the code. Devin, Factory and OpenHands run the task and report back that it is done. Continuum does not compete with either: it writes the task they run, keeps the state in your git instead of their sandbox, and refuses to take their word for done until the commit is on your remote. Five Claude Code sessions in tmux do the same work with you as the scheduler; that is the comparison that matters.
Questions people ask before they ask: on the landing page →