Nothing is published that can't be pointed at in the code

The build refuses to generate the public feature list if any entry is missing its story, its code references, or points at a file that does not exist.

What it is

A validation step between the raw feature inventory and the typed registry the site renders from. A missing name, one-liner, description or reason-it-was-built is an error. An empty code reference list is an error. A code reference pointing at a file that is not in the repo is an error. A category outside the ten is an error. Any error and the registry is not written at all.

Also called: feature accuracy · no vapourware · marketing claims validation

See it
Nothing is published that can't be pointed at in the code
CustomerBuildingAmountStatus
Ronan PetschHobby Shop$5,950Open
Delia YoderHobby Shop$4,620Draft
Marlin HooverRiding Arena$7,280Open
Sutter KlineRiding Arena$17,540Draft
Delia YoderBarndominium$10,320Open
The build output: domain file count, feature count, category breakdown, and a refusal listing a codeRef that does not exist. Sample data — no customer information appears here.
How it works
  1. 1Every inventory file is parsed; both the wrapped and bare array shapes are accepted rather than losing a domain over an envelope.
  2. 2Slugs are normalised and deduped — two domains touching the same feature merge their references rather than producing two pages at one URL.
  3. 3Each code reference is resolved against the repository; a miss is an error.
  4. 4Cross-references and parents that do not resolve are dropped or promoted rather than published as broken links.
  5. 5Named visual replicas are validated against the ones that actually exist, and unknown ones are dropped.
Why we built it

The script states its own role: "this script is the gate between what they found and what the public site claims… Every page this generates is a public promise about what the software does, and the demo that follows will be measured against it." The type definition puts the same rule in one line: "A feature page that describes something the platform does not do is the fastest way to lose a deal in the demo that follows." The replica validation exists for a related reason — "they were lied to and shown UI elements that never existed in the dashboard" is the failure the visual layer exists to prevent.

The problem
  • Marketing pages could describe capabilities the product does not have.
  • Broken cross-links and duplicate URLs would ship silently.
  • Illustrations could depict screens that were never built.
Sound familiar?
What you get
Every public claim traces to a file in the repository
The build fails rather than publishing an unverifiable claim
Cross-links and parents always resolve

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →