01 · Content
Every asset has a page, an original description and a runnable demo
133 components, 74 prompts, 33 backgrounds — each with a detail page and a demo that mounts in place.
the catalog →Brand · launch
The list we actually ran
Launch checklists are usually advice. This one is a record: 12 items, each honestly labelled — 7 shipped, 3 left out on purpose, 2 still open. Every shipped item links to the page that proves it, so nothing here has to be taken on faith.
Shipped
7
Deliberately out
3
Still open
2
Shipped
02 · Content
Copy passes the tone lint with no live overclaim hits
The voice guide's banned list is the same dictionary the harness scans the public prose with.
voice guide →03 · Trust
No number on the site is invented
Counters come from the data file, sizes from the build report, and gaps say 'not measured' instead of borrowing a score.
open metrics →04 · Trust
The admin console is labelled a demo
It runs on localStorage, feeds nothing, and says so on every panel that could be mistaken for live data.
05 · Access
Keyboard walk: every interactive surface reachable, focus always visible
Audited per asset; the catalog's banded scores are published rather than summarised.
audit register →06 · Access
Reduced-motion handling is global and cannot be forgotten
A stylesheet-level rule with 0.001ms rather than animation:none, so end states are preserved.
craft notes →07 · Crawl
Sitemap, robots and canonicals agree with the catalog
The export harness compares the sitemap's component count against the catalog at build time.
crawl surface →08 · Deliberately out
No accounts, no newsletter, no waitlist
A demo signup would need fake data behind it. Until there is a reason and a backend, the button is the honest thing to omit.
09 · Deliberately out
No analytics, no cookies, no third-party tags
Nothing here counts visitors, which is also why no page-view number appears on the metrics page.
why →10 · Deliberately out
No paid tier pretending to exist
The Pro pages describe what is built and mark the rest as not built; nothing takes a card.
11 · Open
A Lighthouse run on a real machine, published with its config
No browser runtime was available to produce one; the speed page prints kilobytes and names the gap.
speed story →12 · Open
A second measurement series to make the deltas a trend
The changelog records size deltas per build; a weekly series would turn those into evidence rather than snapshots.
Why the “left out” column is the useful one
A checklist that only lists what shipped is a marketing page. The three deliberate omissions are decisions a reader can disagree with: no accounts (so no real favourites), no analytics (so no public page-view number), no paid tier (so no revenue). Each of those would have been easy to fake with a mock, and each would have made every other number on the site cheaper.
The two open items are the honest remainder: a Lighthouse run needs a browser this build never had, and a trend needs a second measurement. They stay on the list until they are done, not quietly dropped.
Social preview checklist
- ☐ every /og route answers 200 and image/* (harness-checked)
- ☐ each card under the recorded weight cap (checked)
- ☐ run the URL through one chat platform's preview validator env
- ☐ one feed-reader check for the JSON and RSS variants env
the env-tagged rows need a live domain; everything above them is verified offline