Launch versions from the roadmap

A workshop does not stop at documents. It slices the work into versions and queues them as drafts. The Roadmap tab is where that queue lives, and where you launch it.

Versions run one at a time, in order: that is a rule of the product, not a preference: a project has at most one version in development, and a workshop launches its drafts strictly in the order it planned them.

Reading the pipeline

The tab is titled Build pipeline, with the rule under it: versions run one at a time, in order. On the right, the header counts what is still queued and how many production units the workspace has left, above a bar with one segment per version.

Below it, the pipeline is built around a hero: the single version that matters right now.

Then come the other sections:

• Up next: the rest of the queue on a timeline, in execution order.
• Done: collapsed at the bottom, each version with its ship position, its V number and a link to open it.
• Cancelled attempts: collapsed and grouped by version name, each attempt with the reason it was cancelled.

Launch one version

Press Start version on the hero. The version becomes visible in the project, the design conversation opens, and the workshop's brief is injected as the first message. From there it is an ordinary version. See What happens inside a version.

A draft that has no brief yet says so (No build brief yet), and Edit lets you write one before launching.

Launch a batch

When nothing is running, the strip above the hero arms a batch:

1. Pick how far to go with Batch up to: the target version in the queue.
2. Click Start {n}-version batch.

The agent then builds them back to back, unattended. You can close the tab; you are notified when the batch finishes. Each version queued by the batch carries an auto badge in Up next.

While it runs, the strip becomes a banner: Batch in progress, the position (3 of 7), and the name of the version coming next.

Stop a batch

Stop batch disarms the queue after a confirmation. Read the wording carefully: the version building now keeps going, the batch simply stops launching further ones. To stop what is currently building, cancel that version.

Re-arming afterwards is just picking a target again. There is no paused state to resume.

Cancelling is a retry

Cancelling a version from the pipeline reverts its changes and re-creates a fresh draft in the same slot. The cancelled attempt drops into Cancelled attempts with its reason, and the plan keeps its shape.

That is what makes a roadmap safe to run unattended: a version that goes wrong costs you an attempt, not the plan.