Framework
One tracker item per widget becomes a ticket for the Software Factory. The agent follows the migrate-afl-widget skill (parity track) or the redesign-afl-widget skill (redesign track) and builds the widget against Optimizely content types. The parity harness proves a migrated widget matches the live site; a redesigned widget is checked against the design system in Figma. Then a pull request is raised.
Redesign track
A widget moves here with Rebuild from designs, or is created by combining overlapping widgets. The Software Factory finds the component in the AFL design system in Figma, builds it from design system tokens and publishes Figma, accessibility and behaviour checks. The agent opens a pull request and a designer approves it in the tracker.
Parity harness
Live pages are recorded once into git. Every run replays them offline and renders the build from fixtures captured from the same recording, so both sides see identical data and images. Pixels, computed styles, interactions and club theme tokens are compared.