Birch & RIG Boots

A configurator that cannot ship broken.

We built a product configurator, then built the suite that refuses to let it regress.

Wireframe render of a lace-up boot on a plinth, annotated with the configurator's seven adjustable axes: material, color, sole, laces, hardware, stitching, accent.

Seven axes, one live render

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.

The suite is the product

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.

17/21Before
21/21After

Configurator changes ship with a fully green regression suite.

Published limits

What this is not

Proof that names its own boundaries is worth more than proof that does not. So here is the boundary.

This is not a boot company.

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.

The repository is two assets, not an application.

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.

The boot in the render is a lace-up, not a western boot.

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.

The numbers are the only numbers.

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.

Inspect it yourself

The repository is public. It is small, and reading it takes about a minute.

Repositorymrodgersjs-web/birch-rig-boots
Created5 August 2026
Last push6 August 2026

If the gate is what you want

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.