Milestone Health | Zyeon UI

status="ready" · six milestones on one date axis. Each bar runs from the committed baseline (upright tick) to today's forecast (dot); its length is the slip. Beta feature freeze was promised for Mar 25 and is now forecast for Apr 13 — +19 days, collected over three reviews, which is what the faded rings behind it are. API contract freeze landed five days late and is still amber, while Pilot rollout sits on its baseline and is green: RAG is a judgement the review recorded, not a function of the arithmetic. Point at a row or Tab to it to move the big number; press to pin.

Milestone health · Atlas

Plan rev 4 · reviewed fortnightly · steering group

Worst open slip

+19days late

Beta feature freeze · Mar 25 → Apr 13 · off track · 45% confidence

3 on track 50% · 2 at risk 33% · 1 off track 17%

Milestone health · Atlas: every milestone with its committed baseline, the current forecast, the slip between them in calendar days, how far the forecast moved at the last review, the review status, the confidence in the forecast and the earlier forecasts on record.
Milestone	Baseline	Forecast	Slip	Last move	Status	Confidence	Owner	Earlier forecasts
Spec sign-off	Feb 13	Feb 13 (landed)	on plan	held	On track	not given	Jovany	Jan 16 said Feb 13
API contract freeze	Feb 27	Mar 4 (landed)	5 days late	moved out 2 days	At risk	not given	Heidi	Jan 16 said Feb 27, Feb 13 said Mar 2
Beta feature freeze	Mar 25	Apr 13	19 days late	moved out 7 days	Off track	45%	Allene	Jan 16 said Mar 25, Feb 13 said Mar 30, Mar 6 said Apr 6
Pilot rollout · 3 teams	Apr 8	Apr 8	on plan	held	On track	70%	Sharon	Feb 13 said Apr 8, Mar 6 said Apr 8
Perf budget met	Apr 22	Apr 17	5 days early	pulled in 5 days	On track	60%	Abel	Mar 6 said Apr 22
GA launch	May 6	May 20	14 days late	moved out 7 days	At risk	50%	Sally	Jan 16 said May 6, Mar 6 said May 13

6 milestones: 3 late, 2 on plan, 1 early. 2 already landed. Last review: 3 moved out, 1 pulled in. Median confidence 55%.

The bar spans a milestone's committed baseline (the upright tick) and today's forecast (the dot); its length is the slip. Faded rings are earlier forecasts, so a row of them walking right is a date that keeps moving. A diamond marks a date that has already landed. The dashed line is today, Mar 24.

Point at a milestone or Tab to it to read its slip above; press to pin it.

onSelectMilestone → null (nothing pinned)

status="empty" · a valid payload with no milestones at all — told apart from "loading" and from "the fetch failed".

Milestone health · Atlas

Plan rev 4 · reviewed fortnightly · steering group

No milestones to track yet

Slip is the distance between a committed date and today's forecast, so this card needs at least one milestone carrying both.

status="loading" · a skeleton shaped like the card it replaces (headline, mix bar, four rows), aria-hidden plus an sr-only role=status. No timers involved, and the pulse stops under prefers-reduced-motion.

Milestone health · Atlas

Plan rev 4 · reviewed fortnightly · steering group

status="error" · the fetch failed. "Try again" appears only when onRetry is passed, and pressing it switches this card to ready.

Milestone health · Atlas

Plan rev 4 · reviewed fortnightly · steering group

Couldn’t load this chart

The data source didn’t respond.

Nothing is late: two milestones sit exactly on their baseline and two were pulled in. The headline still has a number to print — the worst open milestone is on plan, so it reads 0 rather than going blank — and the mix bar is a single 100% band.

Milestone health · Kestrel

Plan rev 2 · every milestone on or ahead of its committed date

Worst open slip

0days of slip

Design lock · Apr 3 → Apr 3 · on track · 80% confidence

4 on track 100%

Milestone health · Kestrel: every milestone with its committed baseline, the current forecast, the slip between them in calendar days, how far the forecast moved at the last review, the review status, the confidence in the forecast and the earlier forecasts on record.
Milestone	Baseline	Forecast	Slip	Last move	Status	Confidence	Owner	Earlier forecasts
Design lock	Apr 3	Apr 3	on plan	held	On track	80%	Tatyana	Mar 6 said Apr 3
Content freeze	Apr 17	Apr 15	2 days early	pulled in 2 days	On track	75%	Mabelle	Mar 6 said Apr 17
Store review submitted	May 1	May 1	on plan	held	On track	70%	Orlando	Mar 6 said May 1
Launch	May 15	May 11	4 days early	pulled in 4 days	On track	65%	Breana	Mar 6 said May 15

4 milestones: 0 late, 2 on plan, 2 early. Last review: 0 moved out, 2 pulled in. Median confidence 73%.

The bar spans a milestone's committed baseline (the upright tick) and today's forecast (the dot); its length is the slip. Faded rings are earlier forecasts, so a row of them walking right is a date that keeps moving. The dashed line is today, Mar 24.

Point at a milestone or Tab to it to read its slip above; press to pin it.

Every milestone has landed, so there is no open work for the headline to be about: the eyebrow says so out loud and falls back to the largest slip in the set (Data migration complete, +9 days). None of these rows carries a confidence — a date that has already happened is not a forecast — so they read "no confidence" and the median is left out of the tally instead of being printed as 0%.

Milestone health · Ledger migration

Closed out · retrospective view

Worst slip · everything has landed

+9days late

Data migration complete · Feb 20 → Mar 1 · off track · no confidence given · landed

2 on track 50% · 1 at risk 25% · 1 off track 25%

Milestone health · Ledger migration: every milestone with its committed baseline, the current forecast, the slip between them in calendar days, how far the forecast moved at the last review, the review status, the confidence in the forecast and the earlier forecasts on record.
Milestone	Baseline	Forecast	Slip	Last move	Status	Confidence	Owner	Earlier forecasts
Kick-off	Jan 9	Jan 12 (landed)	3 days late	moved out 3 days	On track	not given	Wilhelm	Dec 5 said Jan 9
Vendor contract signed	Jan 30	Jan 30 (landed)	on plan	held	On track	not given	Loraine	Dec 5 said Jan 30
Data migration complete	Feb 20	Mar 1 (landed)	9 days late	moved out 5 days	Off track	not given	Jany	Dec 5 said Feb 20, Feb 6 said Feb 24
Cutover	Mar 13	Mar 12 (landed)	1 day early	pulled in 1 day	At risk	not given	Valerie	Feb 6 said Mar 13

4 milestones: 2 late, 1 on plan, 1 early. 4 already landed. Last review: 2 moved out, 1 pulled in.

The bar spans a milestone's committed baseline (the upright tick) and today's forecast (the dot); its length is the slip. Faded rings are earlier forecasts, so a row of them walking right is a date that keeps moving. A diamond marks a date that has already landed. The dashed line is today, Mar 24.

Point at a milestone or Tab to it to read its slip above; press to pin it.

Degenerate case: one milestone whose baseline, forecast and "today" are all Jun 1. Every date in the payload is the same day, so the axis span would be zero and every position a division by zero; the domain is padded by a day on each side and the single marker sits in the middle of a four-day window.

Milestone health · single gate

One milestone, no revisions on record

Worst open slip

0days of slip

Security audit closed · Jun 1 → Jun 1 · on track · 90% confidence

1 on track 100%

Milestone health · single gate: every milestone with its committed baseline, the current forecast, the slip between them in calendar days, how far the forecast moved at the last review, the review status, the confidence in the forecast and the earlier forecasts on record.
Milestone	Baseline	Forecast	Slip	Last move	Status	Confidence	Owner	Earlier forecasts
Security audit closed	Jun 1	Jun 1	on plan	no earlier forecast	On track	90%	Tristian	no earlier forecast

1 milestone: 0 late, 1 on plan, 0 early. Median confidence 90%.

The bar spans a milestone's committed baseline (the upright tick) and today's forecast (the dot); its length is the slip. The dashed line is today, Jun 1.

Point at a milestone or Tab to it to read its slip above; press to pin it.

A feed with holes. Pilot rollout's forecast is the string "TBC", so it cannot be placed and is named in the footnote instead of vanishing; GA launch has one revision with no review date, which is counted rather than dropped in silence — otherwise "the forecast moved twice" quietly becomes "it moved once". Five rows are still drawn, and the mix re-apportions across them.

Milestone health · Atlas

Plan rev 4 · imported from the tracker

Worst open slip

+19days late

Beta feature freeze · Mar 25 → Apr 13 · off track · 45% confidence

2 on track 40% · 2 at risk 40% · 1 off track 20%

Milestone health · Atlas: every milestone with its committed baseline, the current forecast, the slip between them in calendar days, how far the forecast moved at the last review, the review status, the confidence in the forecast and the earlier forecasts on record.
Milestone	Baseline	Forecast	Slip	Last move	Status	Confidence	Owner	Earlier forecasts
Spec sign-off	Feb 13	Feb 13 (landed)	on plan	held	On track	not given	Jovany	Jan 16 said Feb 13
API contract freeze	Feb 27	Mar 4 (landed)	5 days late	moved out 2 days	At risk	not given	Heidi	Jan 16 said Feb 27, Feb 13 said Mar 2
Beta feature freeze	Mar 25	Apr 13	19 days late	moved out 7 days	Off track	45%	Allene	Jan 16 said Mar 25, Feb 13 said Mar 30, Mar 6 said Apr 6
Perf budget met	Apr 22	Apr 17	5 days early	pulled in 5 days	On track	60%	Abel	Mar 6 said Apr 22
GA launch	May 6	May 20	14 days late	moved out 7 days	At risk	50%	Sally	Jan 16 said May 6, Mar 6 said May 13

5 milestones: 3 late, 1 on plan, 1 early. 2 already landed. Last review: 3 moved out, 1 pulled in. Median confidence 50%.

The bar spans a milestone's committed baseline (the upright tick) and today's forecast (the dot); its length is the slip. Faded rings are earlier forecasts, so a row of them walking right is a date that keeps moving. A diamond marks a date that has already landed. The dashed line is today, Mar 24.

Point at a milestone or Tab to it to read its slip above; press to pin it.

1 milestone is missing from the chart: Pilot rollout · 3 teams — the forecast date is not readable. 1 earlier forecast is missing from the trail: the review date could not be read.

Nothing in this payload can be placed — every date came out of the tracker as "Q2 2026" or "TBD". Better to route to the error branch and say how many milestones there were than to draw an empty axis that still looks like a working chart.

Milestone health · Atlas

Plan rev 4 · dates exported in an unknown format

This plan can’t be drawn

None of the 6 milestones carry a readable baseline and forecast date, so there is no slip to measure.

Contract refusal: two rows were merged during import and now share an id. An id selects a row and keys its reading, so a duplicate would pin two milestones at once and mis-attribute every number after it.

Milestone health · Atlas

Plan rev 4 · two rows merged during import

This plan can’t be drawn

Two milestones share the id "beta-freeze". An id selects a row and keys its reading, so a duplicate would pin two milestones at once.

order="slip" · nine gates across eight months, with names far longer than the column. Sorted by damage the top row is +14 days — but it has already landed, so the headline is the 13-day slip below it. The plan crosses a New Year, so the axis prints the year; the mix bar apportions 3/3/3 as 34% / 33% / 33%, which adds up to 100 instead of the 33/33/33 that independent rounding would print.

Milestone health · Meridian programme

Nine gates across eight months · programme board

Worst open slip

+13days late

Load test sustained at 4× peak traffic · Mar 30, 2026 → Apr 12, 2026 · on track · 44% confidence

3 on track 34% · 3 at risk 33% · 3 off track 33%

Milestone health · Meridian programme: every milestone with its committed baseline, the current forecast, the slip between them in calendar days, how far the forecast moved at the last review, the review status, the confidence in the forecast and the earlier forecasts on record.
Milestone	Baseline	Forecast	Slip	Last move	Status	Confidence	Owner	Earlier forecasts
Regulatory pre-submission accepted	Nov 10, 2025	Nov 24, 2025 (landed)	14 days late	moved out 6 days	On track	93%	Reba	Oct 20, 2025 said Nov 10, 2025, Oct 27, 2025 said Nov 18, 2025
Load test sustained at 4× peak traffic	Mar 30, 2026	Apr 12, 2026	13 days late	moved out 1 day	On track	44%	Catherine	Oct 20, 2025 said Mar 30, 2026, Mar 16, 2026 said Apr 11, 2026
General availability across all regions	Jun 22, 2026	Jul 2, 2026	10 days late	held	Off track	28%	Jamar	Oct 20, 2025 said Jun 22, 2026, Jun 8, 2026 said Jul 2, 2026
Reference architecture signed off by security	Dec 8, 2025	Dec 17, 2025 (landed)	9 days late	moved out 6 days	At risk	68%	Leatha	Oct 20, 2025 said Dec 8, 2025, Nov 24, 2025 said Dec 11, 2025
Support runbooks handed to the 24/7 desk	Apr 27, 2026	May 4, 2026	7 days late	moved out 1 day	Off track	92%	Selena	Oct 20, 2025 said Apr 27, 2026, Apr 13, 2026 said May 3, 2026
Partner sandbox open to external developers	Feb 2, 2026	Feb 6, 2026	4 days late	moved out 1 day	On track	95%	Terrell	Oct 20, 2025 said Feb 2, 2026, Jan 19, 2026 said Feb 5, 2026
Data processing agreement countersigned	Jan 5, 2026	Jan 2, 2026	3 days early	moved out 2 days	Off track	22%	Emery	Oct 20, 2025 said Jan 5, 2026, Dec 22, 2025 said Dec 31, 2025
Marketing site and pricing page frozen	May 25, 2026	May 20, 2026	5 days early	moved out 4 days	At risk	88%	Vicky	Oct 20, 2025 said May 25, 2026, May 11, 2026 said May 16, 2026
Localisation complete for all launch markets	Mar 2, 2026	Feb 24, 2026	6 days early	moved out 9 days	At risk	88%	Omar	Oct 20, 2025 said Mar 2, 2026, Feb 16, 2026 said Feb 15, 2026

9 milestones: 6 late, 0 on plan, 3 early. 2 already landed. Last review: 8 moved out, 0 pulled in. Median confidence 88%.

The bar spans a milestone's committed baseline (the upright tick) and today's forecast (the dot); its length is the slip. Faded rings are earlier forecasts, so a row of them walking right is a date that keeps moving. A diamond marks a date that has already landed. The dashed line is today, Apr 6, 2026.

Point at a milestone or Tab to it to read its slip above; press to pin it.