Reference · Delivery Phases

Delivery Phases

The ten-phase event lifecycle and its visual communications toolkit — the formats and variants used to show the lifecycle across product, marketing and documentation. One geometry engine; every format is a switch on it.

Engine: wds-wheel-engine_v1_3.js (shared)Colours: Notion · Colour RegistryPhase data: matches registry

Phases are drawn in the canonical phase colours. This page is the toolkit for how the lifecycle is communicated, not where its colours are defined — for phase tokens, hex values and on-fill pairings, the authority is the Wavecast Master Colour Palette (the single colour reference). The formats below render those colours; they never redefine them.

Badge format

Canonical

The most-used format: a single phase as a status chip — each with its Material icon and a one-line remit, read top-to-bottom in lifecycle order.

1Ideation

Define concept, scope, budget, and feasibility.

IdeationIdeation

2Setup

Build hub, brand, plan, roles, and kick off playbook.

SetupSetup

3Launch

Publish registration and onboard client operators.

LaunchLaunch

4Promotion

Run campaigns and lock promo assets.

PromotionPromotion

5Finalising

Lock agenda, assets, rehearsals, and go/no-go.

FinalisingFinalising

6Pre-Live

Execute preflight checks and confirm readiness.

Pre-LivePre-Live

7Live

Run show, monitor quality, capture incidents.

LiveLive

8Replay

Process recordings and publish replay assets.

ReplayReplay

9Insight

Report outcomes, debrief, and capture improvements.

InsightInsight

10Archive

Store assets, close out, and decommission resources.

ArchiveArchive

Notes

Two forms per phase: tinted (13% fill, 30% border, hue dot, tuned text) is the in-product default; solid (hue fill + on-fill text) is for emphasis and validates the on-fill pairing.
Used across the app (table rows, status pills), documentation, and product marketing — anywhere a single phase needs to read at a glance.
On-fill text is per-phase, never assumed white — Live, Replay and the light Pre steps carry black; see the Master Colour Palette for each pairing.
Hue alone never carries meaning: the badge always pairs colour with the phase label.

Ring format

Canonical

The primary format: a weighted ring of all ten phases.

Full lifecycle — heroAll ten lit, Replay band, labels, centre caption. The canonical overview.

You-Are-Here — SetupOne phase lit, rest dimmed, phase caption. The section-cover state.

You-Are-Here — LiveLive lit. The band reads lit because Live and Replay drive it.

You-Are-Here — ReplayReplay lit — the long-tail slice plus its concentric band.

Gradient spectrumSame segments and gaps as the flat ring — gradient applied per container, graduating within each act; the Replay band stays flat.

No labelsLit ring, numbers only — for tight compositions.

Notes

Arc length follows rough relative duration — Replay is the long tail; momentary phases (Launch, Pre-Live, Live) sit near the FLOOR minimum.
The You-Are-Here state (active + dim) is the section-cover hero; the overview state (active:null) is the explainer.
The inner Replay band starts staggered under Live and runs to Replay's end; it reads lit whenever Live or Replay is the active phase. This is the device's core idea — Replay begins while you are still Live.
The gradient spectrum variant keeps the exact same segments and gaps as the flat ring — the gradient is applied per segment-container, so each phase tile graduates toward the next within its act (Pre, Live, Post), while the gaps keep all ten phases distinct. The inner Replay band stays a flat Replay fill — its position under Live carries the bridge, no blend needed. Gradient is an overview treatment; single-phase focus states stay flat.
Phase fills and on-segment number colours come from the phase tokens in the Master Colour Palette — not a lightness heuristic.

Corner marker format

Canonical

A stripped ring used as a small position indicator on content pages.

Corner marker — SetupSmall position indicator: no labels, no caption, numbers off.

Corner marker — LiveSame marker, Live position.

Corner marker — ReplaySame marker, Replay position.

Notes

Same geometry as the hero ring with labels, caption and numbers off (nums:false) and a small maxW.
Brand presence stays on the cover; the marker is a wayfinding aid, not a branded element.
Open: the canonical marker size should become an explicit token rather than a per-call maxW.

Metro line format

Canonical

A transit line: equal-spaced stations showing sequence and position.

Full lifecycle — overviewAll ten stations on one track, evenly spaced by sequence.

Full lifecycle — you-are-hereCurrent station carries the sonar halo; travelled track coloured, ahead greyed.

Notes

Unlike the linear strip (which weights by duration), the metro line is equal-spaced — it communicates sequence and position, not how long each phase lasts.
Station states: done (solid), current (solid with a soft same-hue rim and a concentric sonar halo), upcoming (hollow, phase-coloured outline). Travelled track is phase-coloured; track ahead is grey.
The current station uses no white outline — emphasis comes from the halo's depth, in the phase's own colour at low opacity.

Metro line — slide footer

Canonical

A windowed slice — previous · current · next — at the standard metro scale.

Footer window — mid-line (at Live)Sonar halo throbs on the current station; continuation tails both sides.

Footer window — at the startClamped to three; tail only trails right. No false 'previous'.

Static fallback (motion:false)For decks and PDF — fixed concentric rings, no animation.

Notes

Shows a three-station window around the current phase, tagged done · you are here · next · later; sized identically to the full metro line — same station and node size, just three stations.
Motion is a switch (motion:true by default). On: the halo expands outward in a repeating sonar ripple. Off: it renders fixed concentric rings — the same frame, frozen — for decks, PDF and any context that won't animate.
Animation is SMIL inside the SVG, so it survives as a standalone asset with no external CSS, and honours prefers-reduced-motion.
Fading tails with continuation dots signal the window is a slice of the full line — present only where more line exists, so the true start and end read as edges.
The window clamps at the ends: at phase 1 it shows current + next two; at phase 10, previous two + current. Always three stations.

Phase navigator

Canonical

An interactive in-product control: click a phase to load its content.

Notes

A live product component, not a static asset — three states: resting (calm tab, subtle phase-colour accent at the bottom edge), rollover (surface lifts, accent strengthens, name brightens), active (fills with the phase colour, raised, on-fill text).
Colour is recessive at rest, dominant when active — so a row of ten phases reads as a calm control, and the selected phase commits to full colour. Active on-fill follows the per-phase rule (Live and Replay carry black).
The accent bar sits flush to the bottom edge per WDS convention — a straight bar clipped by the card rounding, never curved.
Clicking a phase emits the selection; the product renders the phase-specific view. This is the interactive replacement for the static linear strip.

Engine switches

Reference

Every format above is one engine with these switches.

Switch	Type	Default	Effect
`active`	int \| null	null	Phase 1–10 to light; null lights all (overview).
`dim`	bool	false	Dim non-active phases to Zinc. Pairs with active.
`band`	bool	false	Draw the inner Replay band beneath Live→Replay.
`grad`	bool	false	buildRing only: blend arcs phase-to-phase (spectrum overview).
`labels`	bool	true	Phase name labels outside the ring.
`caption`	bool	true	Centre caption (overview title or phase name).
`nums`	bool	true	Phase numbers on each segment.
`rOut / rIn`	px	168 / 108	Outer / inner ring radius.
`vb / maxW`	px	460 / 430	SVG viewBox and rendered max width.
`mode`	str	'full'	buildMetro only: 'full' line or 'window' footer slice.
`motion`	bool	true	buildMetro only: sonar ripple on; off renders static rings.

Notes

There is one geometry engine; formats and variants are switch combinations, never separate drawings.
Consuming decks inline a copy of the engine — when the engine bumps, those copies must be re-synced or they drift.
buildLinear and buildMetro take their own switches (active, dim, mode); the radius switches above are specific to buildRing.

Delivery Phases — Reference v1.0
Ported into the WDS References shell and re-pointed to the shared canonical engine (wds-wheel-engine_v1_3.js) — the page no longer carries its own engine copy. Phase data mirrors the Notion Colour Registry.