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.
How it works (parity track)
On the parity track, the team sets a priority and the tracker creates the ticket. The Software Factory picks it up, records its job number on the item, records the live widget, builds it and runs the parity harness until every check passes. Results and screenshots land back here, the agent opens a pull request, and the team reviews and merges it.
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.