Absent means unknown
Each design’s facts live in a Markdown file with strictly validated fields. A missing field means the fact is not known, and nothing is invented to fill it. A misspelled field is a build error rather than a silent gap.
Facts decide what is shown
A price appears only once it is marked as verified against the shop. A buy button exists only for a valid shop link; without one, the design says it is not yet available to order. Drafts never reach the live site: no page, link, sitemap entry or image.
Structured data says only what the page says
The machine-readable description of each product matches the visible page, and the build checks that it does. An offer is described only when there is a valid shop link and a verified price. There are no ratings, reviews, availability, shipping costs or FAQ markup.
Check every build
Every pull request is built, audited and HTML-validated before it can deploy. Search and AI-discovery choices are recorded with the strength of their evidence, from established practice to untested hypothesis, and nothing is presented as an optimisation unless it also helps a person reading the page.
What we take from it
Make “unknown” a real value, let verified facts switch features on, and audit the output, not just the input. Accuracy then stops depending on remembering to check.