Write the role definition
To do·Ines Marchetti
Ready — every dependency closed
Unlocks 1 task
Hiring ProcessHiring Process template
Principal platform engineer hire
Waiting approvalNormalExecution is paused at a gate until somebody decides.
0progress
progress: 0 out of 100Add one principal-level platform engineer who can own the failover story end to end, without stretching the Q4 headcount line.
Next
Paused at Requisition — is waiting on Dai Okonjo. Fund one principal-level headcount against the Q4 line.
Requisition
Current stage
4
Stages
11
Tasks
0 closed
3
Open gates
6
Ready now
5 waiting
7 weeks
Planned
Ready to start6
5 waiting- Write the role definitionInes Marchetti
- Confirm the Q4 budget lineKai Oyelaran
- Source direct candidatesInes Marchetti
- Screen applicationsPeople
- Run the panel interviewsAris Vandel
- Collect structured scoresPeople
Held behind a dependency
- Publish the role×2
- Run the failover design assessment×3
- Calibrate the level and band×3
- Extend the offer×1
- Plan the first week×1
Assigned teams2
Departments, in routing order
Accountable
Executive Ines MarchettiManagers Talia Brennecke, Aris Vandel
AI agents on this workflow
Stage timeline
- STAGE 1
Requisition
Pending12h plannedEstablish the role is needed and funded.
PeopleManager Talia Brennecke0 of 2 tasks0%Finance approvalPending06 Aug 2026Fund one principal-level headcount against the Q4 line.
Held by Dai Okonjo
- STAGE 2
Sourcing
Pending48h plannedBuild a pipeline worth interviewing.
PeopleManager Talia Brennecke0 of 3 tasks0% - STAGE 3
Assessment
Pending64h plannedTest for the thing the role actually does.
0 of 3 tasks0%Manager approvalPending05 Sep 2026Confirm the assessment bar before candidates see it.
Held by Aris Vandel
Dependencies
Requisition
2Confirm the Q4 budget line
To do·Kai Oyelaran
Ready — every dependency closed
Unlocks 1 task
Sourcing
3joins from Requisition
Publish the role
Backlog·Ines Marchetti
Waiting on 2: Write the role definition; Confirm the Q4 budget line
Unlocks 1 task
Source direct candidates
Backlog·Ines Marchetti
Ready — every dependency closed
Unlocks 1 task
Screen applications
Backlog·People
Ready — every dependency closed
Unlocks 1 task
Assessment
3joins from Sourcing
Run the failover design assessment
Backlog·Halo Rune
Waiting on 3: Publish the role; Source direct candidates; Screen applications
Unlocks 1 task
Run the panel interviews
Backlog·Aris Vandel
Ready — every dependency closed
Unlocks 1 task
Collect structured scores
Backlog·People
Ready — every dependency closed
Unlocks 1 task
Offer
3joins from Assessment
Calibrate the level and band
Backlog·Ines Marchetti
Waiting on 3: Run the failover design assessment; Run the panel interviews; Collect structured scores
Unlocks 1 task
Extend the offer
Backlog·Ines Marchetti
Waiting on 1: Calibrate the level and band
Unlocks 1 task
Plan the first week
Backlog·Aris Vandel
Waiting on 1: Extend the offer
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.
Board11
Backlog
9Publish the role
sourcewaiting ×2
Ines Marchetti12 Aug
Source direct candidates
source
Ines Marchetti26 Aug
Screen applications
Lowsource
People29 Aug
Run the failover design assessment
Highassesswaiting ×3
Halo Rune05 Sep
Run the panel interviews
Highassess
Aris Vandel10 Sep
Collect structured scores
assess
People12 Sep
Calibrate the level and band
Highofferwaiting ×3
Ines Marchetti16 Sep
Extend the offer
Highofferwaiting ×1
Ines Marchetti17 Sep
Plan the first week
offerwaiting ×1
Aris Vandel18 Sep
To do
2Write the role definition
req
Ines Marchetti05 Aug
Confirm the Q4 budget line
Highreq
Kai Oyelaran06 Aug
In progress
0Empty
Review
0Empty
Blocked
0Empty
Completed
0Empty
Approval gates3
3 openFinance approvalPendingHolding work06 Aug 2026
Principal platform engineer hireFund one principal-level headcount against the Q4 line.
Manager approvalPendingNot reached05 Sep 2026
Principal platform engineer hireConfirm the assessment bar before candidates see it.
Executive approvalPendingNot reached16 Sep 2026
Principal platform engineer hireApprove the level, band and offer.
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.
Messages1
- Aris Vandel3d ago
The role is failover ownership. If the assessment does not test that, we will hire the wrong person twice.
Open in the Hub →
Related projects0
Not linked to a department project. Projects appear here when a stage’s work is tracked on a department board as well.
Performance
140h planned · 140h remaining0%
Progress
0 of 11 tasks
0/4
Stages closed
0/3
Gates cleared
0
Blocked tasks
2
Departments
routed through
3
Agents
named on the work
140h
Remaining
from the breakdown
—
Estimate variance
on plan
Task completion0%
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.
Completion rule · Final approval granted
Closed when the offer is approved and extended.
The named gate is approved. Outstanding tasks are reported, not blocking.
Automation7
2 would fire · 0 willNext routing decisionHeld
Held at Dai Okonjo's finance 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.
- Advance stage on completion
- WHEN
- Every task in the active stage reaches a terminal column and the stage carries no pending gate.
- THEN
- Mark the stage complete and route work to the next stage in the chain.
- NOW
- 2 tasks still open in Requisition.
- Notify approver on gate openWould fire
- WHEN
- A stage with a gate becomes active and the gate is still pending.
- THEN
- Raise a workflow notification addressed to the named approver in the Communication Hub.
- NOW
- Dai Okonjo has an open decision.
- Escalate a stale gate
- WHEN
- A gate has been pending longer than its stage's estimate.
- THEN
- Escalate one authority level up and notify the accountable executive.
- NOW
- Needs a real clock. Placeholder timestamps are relative strings.
- Release dependent tasksWould fire
- WHEN
- A task reaches a terminal column and other tasks depend on it.
- THEN
- Move every newly-ready dependent from backlog into to-do.
- NOW
- 4 backlog tasks have all dependencies closed.
- Write outcome to memory
- WHEN
- The completion rule is satisfied.
- THEN
- Write a project-scope memory record summarising the outcome and link it back.
- NOW
- Completion rule is not satisfied yet.
- Auto-approve low-risk gatesHeld for a human
- WHEN
- A QA or manager gate carries no rejection history and sits under the risk threshold.
- THEN
- Nothing. Recorded so the policy is visible and reviewable — a gate an agent can clear is not a gate.
- NOW
- Held for a human by design.
- Stand down a stalled workflowHeld for a human
- WHEN
- No activity for longer than the estimated duration and no open gate explains it.
- THEN
- Nothing automatic. Surfaces the workflow for a human decision.
- NOW
- Held for a human by design.
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.
Activity log2
- 3d ago
Workflow Engine Opened the finance gate on Requisition — Q4 headcount funding.
Requisition - 4d ago
CEO Opened from the Hiring Process template — 4 stages, 3 approval gates. Scheduled to start once funded.