Routines & Tech Tree
From suggesting an ordering to launching the work — and the tech tree that orders it.
This feature spans two levels. At Warp 3, routines suggest what to do next and a tech tree keeps the dependencies straight. At Warp 4, routines stop suggesting and start launching — the same machinery, one trust step further.
Warp 3 — routines suggest, you launch
At Warp 3, routines help prioritize tickets and tasks, but you still control risk and launch tasks one by one — routines only suggest. Alongside them, a tech tree manages growing task dependencies and visualizes the main themes you're juggling toward a functional product.
Warp 4 — routines launch the work
At Warp 4 the launch step itself is delegated. Routines launch tasks autonomously, brief you with a suggested ordering, then proceed on their own. They follow a configurable sprint cadence and batch similar tasks. You still own the schedule — the system just runs ahead of you while you're away.
The one thing that changes
The single difference between Warp 3 and Warp 4 here is who pulls the trigger: at Warp 3 you launch, at Warp 4 the routine launches. That small wording change is a large trust change — and it only works because the safety spine contains every action a routine can take and the bookkeeping records what each autonomous run cost.