Nothing you decide to do ever gets dropped.
RoadWork is the roadmap and work-tracker for teams where agents do most of the work. One durable record — from Idea to Task, with priority — and it will not let you close the day while planned work is still uncaptured.
Work gets dropped between the conversations that decide it.
When a team plans across many chats and terminals, ideas and decisions get lost. A useful finding surfaces in the middle of one discussion and is never written down anywhere durable — so it evaporates. There is no single, trustworthy list of everything the team decided to do. When agents do most of the work, this gets worse, not better: more parallel streams, more hand-offs, more places for a decided task to fall through. (The problem RoadWork exists to fix — draft business requirements, §Problem 1.)
The no-drop guarantee
Every finding the team raises becomes a durable work lane that carries an owner and a trigger — the condition that will fire it. A finding cannot be quietly parked as "later" with nobody on it. And a work session cannot close while something raised in it is still uncaptured: the system warns loudly and holds the item safely — it never drops it silently, and it never freezes you out.
A finding is raised
An idea, a gap, a decision — anywhere in the work. It is spotted, not lost.→
It becomes a lane
Written as a work lane with an owner and a trigger. Bare "later" with nobody on it is refused.→
The owner does it when the trigger fires
It drills into the Idea → Task tree, with its priority, and moves across work-states.→
Closed with a reason — never before
An independent check clears it (the checker is never the builder), then the next item is released.
One team's shape
Renata's people are outnumbered by her agents. Decisions get made in a dozen chats a day. Her real fear isn't speed — it's forgetting a decided piece of work between one agent's chat and the next. Here is her day on RoadWork, using only what the board does today.
Most valuable first
Everything RoadWork is for, in the order that matters — the no-drop guarantee leads. The full honest state of each (built, partial, or designed) is in All the use cases below.
Nothing you decide to do gets droppedKiller · the hero above
Anyone running work across many chats and terminals: a session can't close while something raised in it is still uncaptured — RoadWork warns loud and holds it safe, never silently loses it. That is the animated capture at the top of this page. See how it holds →
Capture a finding the moment it surfaces mid-work
A PM or owner mid-task: an idea or gap raised in one conversation becomes a durable work lane with an owner and a trigger — not a note that evaporates. See it captured →
One durable record the whole team trusts
A team running on agents: 221 real work items live on it right now — AIU runs its own work on RoadWork, so the page's claims are its own dogfood. See the surfaces →
A sprint board that doesn't assume humans do the work
A team where agents do most of the work: a five-level Idea → Task tree built for agent-heavy teams, not human swimlanes. Open the Work Board →
See what's in flight versus what's queued
A PM coordinating agents: the Active-flow lens shows exactly what's in motion versus backlog, at a glance. See the board →
More you can do
- 6
Drill from any idea to its tasks and back
Anyone answering "where are we / what's left": navigate the whole tree in one surface, not five. How the tree works →
- 7
An evidence trail for auditing an agent-run sprint
An engineering manager: every assignment, hand-off, and decision recorded by default, with the reason it closed. See the record →
- 8
Define "done" for every item
An owner who wants acceptance enforced: each item carries its definition of done and a link to the parent intent. See the loop →
- 9
Feed the next work automatically
A team keeping momentum: finish and clear an item, and the next ready item is released. See the loop →
- 10
Survive a crash
Any team that can't afford to lose the plan: a durable plain-text mirror of the record, generated one-way. See the surfaces →
- 11
Read the same truth, read-only, on the Roadmap
Anyone who needs a view without edit risk: the Roadmap renders the same data one-way — never a second source of truth. See the Roadmap view →
- 12
Adopt it bundled with the Agent Platform
A team adopting Agent Engine: RoadWork tracks the work, the Execution Manager runs it — designed, not yet built. How it fits →
All the use cases
Grounded in the product map (§11) and the draft business requirements. Each carries an honest state today: built, partial, or designed.
A sprint board that doesn't assume humans do the work
A five-level tree — Idea → Initiative → Epic → Feature → Task — built for agent-heavy teams.
Built · 4 of 5 levelsA lane-status view for a PM coordinating agents
See every work lane at a glance. (Watching the live terminals themselves is Agent Engine's job, not RoadWork's.)
BuiltAn evidence trail for auditing an agent-run sprint
Every assignment, hand-off, and decision is recorded by default — with the reason it closed.
Partial · unifyingOrchestration for a team adopting the Agent Platform
Adopted alongside Agent Engine as the bundled work surface.
DesignedA team runs it on its own work
AIU does — 221 real items live on it right now. This page's claims are its own dogfood.
BuiltCapture everything decided — even mid-work
Any finding that surfaces in the middle of a task can be written down durably.
BuiltNever let planned work be dropped
The no-drop guarantee: warn loud, hold safe, never silent, never freeze you out.
Built · coreDrill through, idea to task and back
Navigate the whole tree to answer "where are we" and "what's left."
BuiltShow what's in flight
The Active-flow lens is the live board of what's planned versus what's being worked.
BuiltDefine "done" for every item
Each item carries its acceptance criteria and a link to the parent intent it serves.
PartialSurvive a crash
A durable plain-text mirror of the record, generated one-way, so nothing is lost.
BuiltFeed the next work automatically
Finish and clear an item, and the next ready item is released.
Partial · saving gatedThe surfaces
RoadWork's honest reference work is that the company already runs on it. These are the real surfaces — with honest state.
The Work Board
The editable board: three lenses (Active flow · Plan outline · Backlog), a persistent detail panel, edit + move + add-child, and a read-only API for agents.
✓ Built · live board (durable saving is the gated next step)The Roadmap view
A read-only view of the same data — what just executed, what's queued, and the milestones. One-way: it cannot be edited, and it never becomes a second source of truth.
◐ Built · freshness stamp being made honestBundled as Agent Engine
RoadWork tracks the work; the Execution Manager runs it across many agent terminals. Sold together or separately.
○ Designed · customer surface still to buildA read API for agents
Agents query the board directly — board, nodes, and schema — so the work record is machine-readable, not just human-readable.
✓ BuiltHonest gaps
- Partial
Durable saving is off on the live deploy. Edits show in your session but don't persist yet — the durable, signed-in save is the gated database step, and it rides next.
- Partial
The Task level is empty today. The board holds real Ideas, Initiatives, Epics, and Features; the atomic Task rows are still being authored in.
- Partial
The board reads a generated snapshot, not a live feed. It refreshes when the generator runs; auto-refresh + one reconciled source of truth are in progress.
- By design
Watching live terminals is not RoadWork's job. RoadWork shows the work; the Execution Manager (in Agent Engine) shows the terminals doing it. That absence is deliberate, not a miss.
- Designed
The customer-facing product surface is designed, not built. No pricing appears anywhere until full release.
Decide → track → execute
RoadWork is the middle of the ratified product flow. It owns everything from "decided" onward — the durable record of the work — and hands execution to the engine.
Blueprint
Turns a plan into numbered, ratified decisions.
RoadWork
The one durable record of every decided piece of work — nothing dropped.
Agent Engine
Runs the work to done across many agent terminals.
This landing page is the destination for the RoadWork product row on the homepage. Wire the homepage's RoadWork hero/tile (the Rw monogram · green #4B7E66 · status "Live board") to /products/roadwork. Keep the status chip register-honest: the board is live; durable saving and the customer surface are not — mirror the honest state shown above, never round up.