Component Cleanup
Next: Phase 0 on Mark's word: the scorecard script and the annotation standard; then the census and its review stop.
Our shared parts box grew fast while we built, and nobody has checked it for doubles, missing labels or thin instructions.
Every part gets a scorecard against five checks, doubles are merged or retired, and the parts the dashboard built for itself move into the box, so the next app starts with a full one.
Documents
With file names, on their own page →Start here
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
Every shared part gets one line with five checks, so we can see what is clean and what needs work before touching anything.
The scorecard · came from Mark Parson and Tyler Flintopen →
- When two parts do the same job, there are six set ways to settle it, and each pair gets one. In words
How we got here
Each change, traced back to the conversation it came from. A solid mark means the record names the source; a dashed one was matched by the draft and waits for review.
“let's strip the data model out, and let's put the new data model in... it would be packaged up into a single Docker file that includes the UI and the Golang app.”
market-analyst /calls/1b21a3ce… (local)c135-D1 Groups are cleaned in order of use: ux, then data, then filter, nav and layout, then form, then the domain groups, then icon, typography and prose. — Mark Parson
c135-D2 A duplicate is two components a consumer could swap without the page meaning something else (the 5-question framework's "is it necessary?"). — Mark Parson
c135-D8 The two waiting lists merge into one in the layer repo at Phase 1 and are extracted during Phase 2, each ahead of its group, so the control plane web app (c134) finds them in the layer from its first page. Revised the same day: the consumer to keep green is app.qpoint.io's successor, which starts from a blank slate. — Mark Parson
Every shared part gets one line with five checks, so we can see what is clean and what needs work before touching anything.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Named the five checks and ruled the eight defaults
Set the cleanup in motion from c130 ("clean up our components and tighten up our documentation"), gave the five checks in his order, and ruled D1–D8 on 2026-11-09, revising D8 so the waiting-list extractions happen now for the blank-slate successor app.
Set the control plane the layer must be ready for
His 2026-11-05 decision that the control plane ships as SaaS and self-hosted on a new data model is why the web app starts from a blank slate and why the layer must already hold what it needs (D8).
“let's strip the data model out, and let's put the new data model in... it would be packaged up into a single Docker file that includes the UI and the Golang app.” internal
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 1
The full record 8 decisions · 3 key-change entries · 908 words · 1 captures
The record stays as written, for agents and for audit: Key Changes, every decision, the artifacts and the visual record.
Open the record for c135 →