We built a product configurator, then built the suite that refuses to let it regress.
Every change a buyer makes re-renders the boot in place. The interesting engineering is not the picker. It is keeping the render honest while seven independent axes move.
A configurator with seven axes has a large surface to break. The build carries an end-to-end suite against real Chromium, and the gate is binary: the configurator does not ship unless the suite is fully green.
Configurator changes ship with a fully green regression suite.
Proof that names its own boundaries is worth more than proof that does not. So here is the boundary.
No boots exist. There is no supplier, no inventory, no order you can place. Birch & RIG Boots is the brand the demo depicts, not a business with a supply chain behind it.
It holds an architecture diagram and the render above. The configurator and its suite are described by those artifacts rather than published as runnable source.
Internal notes have described this project both ways. The render is the authority on what was actually built, and the render is a lace-up work boot.
17/21 and 21/21 come from the project's own architecture record. There is no traffic figure, conversion rate, or client attached to this work, so none is claimed.
The repository is public. It is small, and reading it takes about a minute.
The configurator is a small piece of work. The habit behind it is the point: a change does not ship until the suite that guards it is green, and the limits get published next to the result.