Validate demand across three segments
Unlocks 1 task
Launch Atlas to general availability with support, billing and escalation live before the first customer arrives — not after.
Paused at Go-to-market — is waiting on Juno Prieto. Approve the locked positioning and the asset set built from it.
Prove there is a market before anybody builds for it.
It exists, it works, and it carries launch load.
Confirm the platform holds at 3x forecast load.
Held by Probe
Approved. Held to 3.4x before degradation, well past the bar.
Positioning, assets and the launch narrative.
Approve the locked positioning and the asset set built from it.
Held by Juno Prieto
Not reached — the asset set is still in production.
The field can sell it on day one, not week six.
Support, billing and escalation live before customers are.
Confirm support, billing and escalation are live and staffed.
Held by Vale Ordonez
One irreversible call, made once, by the person accountable.
Authorise general availability. Irreversible once announced.
Held by CEO
Validate demand across three segments
Unlocks 1 task
Map the competitive field
Unlocks 1 task
Set the pricing hypothesis
Unlocks 1 task
joins from Market validation
Close the launch blockers
Unlocks 1 task
Capacity test to 3x forecast
Unlocks 1 task
Finalise the support runbook
Unlocks 1 task
joins from Product readiness
Lock the positioning
Unlocks 2 tasks
Produce the launch asset set
Ready — every dependency closed
Unlocks 1 task
Brief the analysts under embargo
Ready — every dependency closed
Unlocks 1 task
joins from Go-to-market
Build the pitch deck
Waiting on 2: Produce the launch asset set; Brief the analysts under embargo
Unlocks 1 task
Train the pipeline on the new motion
Ready — every dependency closed
Unlocks 1 task
Set the launch quota
Ready — every dependency closed
Unlocks 1 task
joins from Sales enablement
Staff the support rota
Waiting on 3: Build the pitch deck; Train the pipeline on the new motion; Set the launch quota
Unlocks 1 task
Verify billing paths end to end
Ready — every dependency closed
Unlocks 1 task
Rehearse the escalation chain
Ready — every dependency closed
Unlocks 1 task
joins from Operational readiness
Present the readiness review
Waiting on 3: Staff the support rota; Verify billing paths end to end; Rehearse the escalation chain
Unlocks 1 task
Execute the launch
Waiting on 1: Present the readiness review
One column per stage, in routing order. Tasks inside a stage run in parallel; the first task of each stage joins from every task of the one before it, which is the hand-off between departments made explicit.
Build the pitch deck
Train the pipeline on the new motion
Set the launch quota
Staff the support rota
Verify billing paths end to end
Rehearse the escalation chain
Present the readiness review
Execute the launch
Brief the analysts under embargo
Produce the launch asset set
Empty
Empty
Validate demand across three segments
Map the competitive field
Set the pricing hypothesis
Close the launch blockers
Capacity test to 3x forecast
Finalise the support runbook
Lock the positioning
Confirm the platform holds at 3x forecast load.
Approved. Held to 3.4x before degradation, well past the bar.
Approve the locked positioning and the asset set built from it.
Not reached — the asset set is still in production.
Confirm support, billing and escalation are live and staffed.
Authorise general availability. Irreversible once announced.
Deciding a gate writes the decision and nothing else. The status change, the release of downstream stages and the “ready to close” state are all derived from it on the next render — which is why an approval here is one field rather than a transaction.
Positioning is locked. Everything downstream builds on it now, so changes cost days rather than hours.
Open in the Hub →3.4x before degradation. The bar was 3x. Signed.
Open in the Hub →Launch date is a Friday. Portfolio rule blocks Friday deploys — we move it or we get an exception in writing.
Open in the Hub →Task-weighted, not stage-weighted. A two-hour approval stage and a two-hundred-hour build stage are not half the work each, and treating them as such is the usual way a project dashboard reports 50% before anything has been built.
Closed when the CEO approves launch. Outstanding tasks are reported, not blocking.
The named gate is approved. Outstanding tasks are reported, not blocking.
Held at Juno Prieto's manager gate.
Computed by engine.peekAdvance(), which returns the next stage rather than moving to it. The Task Orchestrator owns the write; keeping this side pure is what lets a card show “next: Engineering” with no risk that rendering a page advances a workflow.
Nothing here executes. There is no scheduler, no queue and no writer — these are evaluations of the current state, refreshed on every render. Adding a trigger is one row in AUTOMATION_TRIGGERS; it appears on every workflow immediately so a rule can be checked against real data before anything is built to act on it.
Pica Launch asset set moved into production.
Mira Halvorsen Raised the Friday deploy conflict against the launch date.
Wren Odalys Locked the positioning.
Workflow Engine Routed from Product readiness to Go-to-market.
Probe Cleared the QA gate at 3.4x forecast load.
CEO Opened from the Product Launch template — 6 stages, 4 approval gates.