Roadmap
In short
Section titled “In short”This is the order in which Qren gets built, and why that order. The destination is one real team running on Qren with their old system switched off — Faisal’s RunRec — while our own companies run on it alongside as the test bed. There is no calendar date; each step is done when it is done properly. Every step below points at the documents that define it, and the Current state page shows where each one stands today, so this page never needs a hand-written status.
The destination
Section titled “The destination”RunRec live on Qren.app, runrec.org retired. Nuchay, Elora Greens and the owner’s personal workspace run on this Mini in parallel — we are client zero, and we find the embarrassments before a client does.
How we get there
Section titled “How we get there”Horizontally: every core system gets a thin, end-to-end-usable version first; nothing goes deep until all of them work on a real workspace. Spec first, approved before a plan exists. Nothing crosses from the old system unexamined — the Gardener proposes, a human approves, and that trains it.
The sequence
Section titled “The sequence”| Step | Defined in | State | Done when |
|---|---|---|---|
| Step 0: The recordThe docs platform, the decisions, the glossary, this page | specs/docs-platformplans/docs-platform-slice | shipped | shipped |
| Step 1: Front doorqren.ai becomes invite-only: one page, request an invite → the approval queue | specs/front-door | specifying | a stranger can ask, the owner can approve |
| Step 2: First-slice specsWork core · approval queue + Gardener · brain · agent model · Supervisor + Control API · companion import · connections + secrets | specs/work-corespecs/approval-queuespecs/brainspecs/agent-modelspecs/supervisorspecs/companion-importspecs/connections | not started | each approved by the owner |
| Step 3: Walking skeletonOne app, one background service, one hidden folder, the Drive; every core system thin but usable; one Lead agent; the approval queue | plans/walking-skeleton | not started | our own Qren work is tracked in it |
| Step 4: Gardener, run oneOur own vault and tasks cross through the approval queue | specs/approval-queue | not started | Nuchay, Elora Greens, Personal exist as workspaces |
| Step 5: Second engineCodex proven at the engine socket | adr/0004-engine-pluralism-acp | decided | one task completed end-to-end on a non-Claude engine |
| Step 6: RunRec v1Faisal's answers folded in; workspace, members, import, meetings as feeds, one connection | the vault | —kept in the vault, not in this record | his team works in it for two weeks alongside the old system |
| Step 7: Cutoverrunrec.org points at the workspace; old services retire | runbooks/cutover | not started | Fireflies is the only thing left running |
| Step 8: AOS 0.8.0The last AOS release — clean and freeze — built in parallel, released when the install path is clear | the vault | —kept in the vault, not in this record | every old install is tidy, stable, and told |
| Step 9: DeepenChat polish, companion capture, more connections, arms, mobile via the edge | later | —no spec yet, by choice | — |
Steps 1, 2 and 8 run in parallel with each other; 3 starts as soon as the first specs are approved; 6 starts the day 3 holds on our own workspaces.
Tracks (the vision’s three, mapped)
Section titled “Tracks (the vision’s three, mapped)”- Track 1 — engagement-ready instance: steps 0–5.
- Track 2 — first team (RunRec): steps 6–7.
- Track 3 — companion and core surfaces: step 9.
Parked, deliberately
Section titled “Parked, deliberately”Brand identity (its own session; research done), the companion’s live capture, mobile apps, arms, local engines. Each has a note in the record saying why it waits.