Package the account context for delivery
Unlocks 1 task
Take Northwind from signature to a running delivery cadence in three weeks, without losing anything Sales already learned about them.
Paused at Contract review — is waiting on Vale Ordonez. Accept a non-standard data residency clause before provisioning begins.
Move everything Sales knows into Operations without losing it.
Confirm what we actually committed to before we start delivering it.
Accept a non-standard data residency clause before provisioning begins.
Held by Vale Ordonez
Held at the COO rather than the Legal manager on purpose: the clause commits Engineering to a deployment region the company does not operate, which is above Corin Ashgrove's line.
Stand up the environment, access and reporting.
First working session, and the schedule that follows it.
Confirm the delivery cadence is staffable against current load.
Held by Vale Ordonez
Package the account context for delivery
Unlocks 1 task
Confirm the commercial terms in writing
Unlocks 1 task
Introduce the delivery team
Unlocks 1 task
joins from Handover
Review the signed terms against standard
Unlocks 2 tasks
Flag the non-standard data residency clause
Ready — every dependency closed
Unlocks 1 task
joins from Contract review
Provision the workspace
Waiting on 1: Flag the non-standard data residency clause
Unlocks 1 task
Grant scoped access to the delivery crew
Ready — every dependency closed
Unlocks 1 task
Configure reporting against the agreed metrics
Ready — every dependency closed
Unlocks 1 task
joins from Provisioning
Run the kickoff session
Waiting on 3: Provision the workspace; Grant scoped access to the delivery crew; Configure reporting against the agreed metrics
Unlocks 1 task
Agree the delivery cadence
Waiting on 1: Run the kickoff session
Publish the success criteria
Ready — every dependency closed
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.
Provision the workspace
Grant scoped access to the delivery crew
Configure reporting against the agreed metrics
Run the kickoff session
Agree the delivery cadence
Publish the success criteria
Empty
Empty
Flag the non-standard data residency clause
Empty
Package the account context for delivery
Confirm the commercial terms in writing
Introduce the delivery team
Review the signed terms against standard
Accept a non-standard data residency clause before provisioning begins.
Held at the COO rather than the Legal manager on purpose: the clause commits Engineering to a deployment region the company does not operate, which is above Corin Ashgrove's line.
Confirm the delivery cadence is staffable against current load.
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.
Data residency clause is non-standard. I can flag it, I cannot accept it. Needs a named approver.
Open in the Hub →Provisioning is staffed and waiting. The moment the clause clears we are three days from kickoff.
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 Northwind has run one full delivery cycle against the agreed cadence.
Every stage reaches complete or skipped.
Held at Vale Ordonez'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.
Workflow Engine Opened a manager gate on Contract review — non-standard residency clause.
Sentry Flagged the data residency clause for review.
Workflow Engine Routed from Handover to Contract review.
Dara Solheim Closed Handover — account context transferred to Operations.
CEO Opened from the Client Onboarding template — 4 stages, 2 approval gates.