Research / Explainers / 8 of 8

The rebuild that refuses to ship

A store's fitment index is rebuilt from its catalog on a schedule, with nobody watching. The danger is not a rebuild that fails loudly. It is one that succeeds at publishing something wrong: a bulk tag edit that stripped fitment overnight, or an export that stopped early. This illustration runs four invented mornings through the order of steps the production rebuild follows and shows where each one ships or stops.

  • StatusIllustration
  • Published2026-10-11
  • Example textInvented
  • Embedded onFitment Search Engine
  • State in the address?day=
  • Codelib/explainers/gate.ts
  • Protocolv1.0

IllustrationExplainer

The rebuild that refuses to ship

A scheduled rebuild publishes only when its change looks like an ordinary day.

one square per productchange against liveordinaryinsideexport completecompletethe runExport the catalogdoneCompile the indexdoneCompare with livedoneBack up what is livedonePublishdoneVerify the uploaddoneShoppers get today's fitment.
The morning

Products exported120 of 120

Fitment entries changed6

Shoppers seetoday's index

A person is toldno

A handful of new and retagged parts. The change looks like an ordinary day, so it ships, and the upload reads back identical.

Illustration. The catalog, the mornings and the width of the ordinary band are invented. The production gate's limits are set per store and are not shown.

The sentence it teaches

A scheduled rebuild publishes only when its change looks like an ordinary day.

Method

  1. Export and compile. The whole catalog is exported and compiled into the index the storefront reads. An export that comes back missing products stops the run.
  2. Compare with live. The new index is compared, product by product, with the one shoppers are using now. A change far outside an ordinary day holds the run for a person, who can release it when a large change was intended.
  3. Back up, then publish. What is live is copied aside before anything is replaced, so the previous index can go back in one step.
  4. Verify the upload. The published file is read back and compared with what was built. A mismatch puts the backup back and alerts a person.

What this does not show

  • It does not show the production limits, the schedule or how often a run has held.
  • It does not show the file formats or how the rebuild connects to the store.

State in the address

The figure keeps its state in the query string, so a particular view can be linked and the page still renders completely without it.

  • ?day= the morning selected, by name

The same figure is embedded on the Fitment Search Engine tool page.

Cite this explainer

OptiVis AI Labs. The rebuild that refuses to ship (explainer). 2026. https://optivisai.org/research/explainers/rebuild-gate

@misc{optivislabs2026explainerrebuildgate,
  title = {The rebuild that refuses to ship (explainer)},
  author = {{OptiVis AI Labs}},
  year = {2026},
  month = oct,
  howpublished = {\url{https://optivisai.org/research/explainers/rebuild-gate}},
  note = {A scheduled rebuild publishes only when its change looks like an ordinary day. Illustration with invented example text.}
}