Roadmap
The one page here with no figures on it, because nothing on it has happened yet. This is intent, labelled as intent.
The rest of the site publishes nothing it cannot recompute, so a page about the future has to earn its place differently: every item below names where it is written down — the conductor repository is public, so the plans and the research can be read, not taken on trust — and what it honestly waits on. When one ships, it leaves this page and enters the corpus. The way off this page is through the record.
Clean-tree discipline before anything else writes
The engine warns about branch hygiene today and enforces nothing. Before the more visible items below, the next plan starts by making the dull rule mechanical: a run that would write onto a dirty tree or the wrong branch stops and says so, instead of trusting the agent to have noticed.
written down in plans/karvan/lanes.plan.jsonwaits on the lanes plan launching — it is the plan's first stage
Several repositories under one plan
Today one plan drives one repository, and the others a run touches are verified but second-class. The authored next era makes the set of repositories first-class: one plan, one record, several trees — which is what a real piece of work usually is.
written down in docs/history/CONDUCTOR-KARVAN.mdwaits on the clean-tree discipline above
Analysis running in lanes beside the session
Read-only work — review, measurement, advice — running parallel to the main session, each lane with its own cost line so the record can say what the second opinion cost. The plural in multi-agent stays where the corpus already put it: in the roles, not in a fleet.
written down in plans/karvan/lanes.plan.jsonwaits on the lanes plan launching
The board pushed to GitHub
The plan is declarative and the checkpoint board already exists in the run store; this mirrors it out — checkpoints as issues that open and close as the engine confirms them, and each run leaving one issue that reads as its diary, a comment per session with its outcome and its cost. A run becomes watchable from a phone, and the history outlives the machine that made it.
One direction only, by decision: the engine writes, GitHub shows. Dragging a card on the board changes nothing in the run, because the tracker is the verified contract and a mirror that talks back is how two records disagree.
written down in docs/history/CONDUCTOR-KARVAN.mdwaits on the clean-tree discipline, and a token the engine can hold
The truthful read side
The researched era after that one, not yet authored into a plan: the event log becomes the single truth and every other surface — status, history, archive listings — becomes a view that reconciles against it. The direction exists because the record has already been caught disagreeing with itself, and the article about the ledger that lied is the measured half of this intention.
written down in docs/dev/NEXT-ERA-FINDINGS-2026-08-04.mdwaits on being authored into a plan the engine can enforce
This site keeps eating its own record
Runs join the corpus as they finish, including the ones that fail — the harvest recomputes every figure from the store, so a new run changes the front page without anyone typing a number. Concepts get revised when the record contradicts them, which is the only kind of revision this site is allowed.
written down in this repository's harvest and evidence gateswaits on the next run finishing
The record so far — what has already run, and what it cost — is the runs page; the plans themselves are in the conductor repository.