current plan critical path ◆ gate {{ cmdBaselineLabel }}

{{ cmdCaption }} · click a shaded block to open that task.

{{ cmdCaption }} — turn on Baseline (top-right) to overlay where each task moved from.

{{ ch.title }}

{{ ch.why }}

{{ cn.title }}{{ cn.tag }}

{{ cn.recommend }}

{{ cn.btn1 }}

Nothing needs a human right now. Everything is planned, sequenced and inside slack.

{{ cw.title }} {{ cw.prob }} {{ cw.trend }}

{{ cc.name }} {{ cc.fte }}

{{ cc.loadTxt }}

{{ bannerLead }} {{ bannerBody }}

{{ g.label }} {{ g.stateTxt }}

{{ g.sub }}

{{ n.title }} {{ n.tag }}

What happened. {{ n.what }}
Already tried. {{ n.tried }}
Recommendation. {{ n.recommend }}

{{ n.impact }}

{{ n.btn1 }} {{ n.btn2 }}

Nothing needs you. The system is self-managing — {{ handledCount }} adjustments this week.

TACTICAL — {{ weekLabel }}

{{ wc.head }} {{ wc.count }}

{{ ti.title }} {{ ti.chip }}

{{ ti.meta }}

{{ ti.desc }}

Exactly what is being worked on, day by day — who is on it, and what each task needs before it can finish. Click a task to edit it. Toggle Detail for definitions of done.

Target outcomes

Stage-by-stage timeline

{{ bc2.head }}{{ bc2.days }}

{{ bc2.intent }}

·{{ bl.text }}

{{ bc2.more }}

Outputs. {{ bc2.outputs }}

Gate. {{ bc2.gateText }} {{ bc2.gateDay }}

{{ bc2.note }}

+ Add task

done in progress scheduled — not started on the critical path blocked held / awaiting decision gate / milestone

Each bar spans a task's scheduled working days; a short task shows its name in the space beside it. Hover any bar for slack, dates & confidence — or zoom from the 90-day overview down to a day-by-day view, where every bar carries its date window and on-time confidence.

{{ gr.name }}

{{ gr.sub }}

{{ b.label }}

{{ wsNote }}

{{ wt.title }}auto

{{ wt.desc }}

{{ wt.owner }} {{ wt.window }} {{ wt.slack }} {{ wt.state }} blocker

Capacity — next three weeks 7.5h workdays · no weekend or overtime assumptions

{{ cr.name }} {{ cr.fte }} {{ cr.loadTxt }}

critical-path work scheduled work idle — system will fill or escalate

Start guards — preventing waste

{{ rh.h }}

{{ ce.tag }}

{{ ce.title }}

{{ ce.sub }}

{{ cm.tag }}

{{ cm.title }}

{{ cm.why }}

{{ cm.move }}

{{ dgSvg }}

{{ dh.label }}

{{ dn.label }}

The line rises gently as labour is earned day by day; payroll settles on calendar month-ends (Days 27 / 55 / 86, plus a small Day-90 run for the days after 31 Mar), so each run differs by the working days in that month. Guarded lump costs — vendor config, security, the optional add-on — only step in on or after the readiness gate (shaded band), so no discretionary cash leaves ahead of a releasable product. Dashed is the unguarded plan, for comparison.

{{ yl.label }}

{{ bt.label }}

Spend pace vs schedule {{ budPace.verdict }}

{{ budPace.note }}

SPEND LINEAMOUNTSTATUS · RELEASE DAYRELEASE LOGIC

How the system protects spend. {{ budNote }}

MORNING BRIEFING · {{ briefRole }} {{ dayChip }} · {{ dayDate }}

{{ briefHeadline }}

Reader-ready status pack — what's going well, where we're falling short, and what changed against the approved baseline.

{{ gw.text }}

{{ fs.text }}

{{ rw.name }} {{ rw.prog }} {{ rw.flag }} {{ rw.note }}

Inject a realistic problem and watch the system re-plan: it re-levels resources, pulls safe work forward, protects gates — and escalates only when it runs out of moves. Everything here also updates the overview, timeline, briefing and portfolio.