AFL

Pipeline stages

Reference: the status each widget moves through on the parity and redesign tracks, and the evidence for each.

Each item has one status at a time. Pick the track from the item's track field.

Parity track

A widget's tracker status moves discovered → audited → stubbed → built → verified → live. Widgets ported before this framework existed start at migrated_unverified and are reused only once they pass parity.

StatusMeansEvidence
discoveredSeen on a live pageTracker row with page, region, legacy source
migrated_unverifiedA prior port exists, never checked against liveAudit verdict (reuse, rework, discard)
auditedLive widget inspected: DOM, styles, breakpoints, theming, behaviour, data sourceParity spec (widget.ts) and inspect dumps
stubbedLive traffic recorded and fixtures extractedlive.har.zip, fixture JSON, tracker artifacts
builtComponent consumes the Optimizely block and renders the fixturesComponent, schema, story, test
verifiedParity passes the whole matrixTracker test runs all green, PR open
liveMerged and serving

Redesign track

discovered → designed → built → reviewed → approved → live. An item moves here with "Rebuild from designs" on its tracker page, or is created by selecting widgets on the dashboard and choosing "Combine into redesign". Combined widgets move to merged, pointing at the new item, and their pages, Pulse widgets, features and dependencies roll up to it.

StatusMeansEvidence
designedThe AFLDS-Web-Library component is found and exported per breakpointdesignComponent, figmaUrl, widgets/<id>/figma/*.png
builtBuilt from design system primitives and ds- tokens on the default scaleComponent, schema, story, test
reviewedFigma comparison, axe and behaviour checks publishedTracker review grid, PR open
approvedA designer signed it off in the trackerapproved_by, approved_at