Unified Component Pantry
The shared library already held product-specific parts, and the urge to 'keep it pure' cost more than it saved. The product also ran an old copy of the demo tools.
Settled: every visual part lives in the shared library, and only parts wired to live data stay in a project. The product dropped its six old demo-tool copies.
Documents
With file names, on their own page →Documents
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
If it draws something on screen, it goes in the shared library; if it talks to an app's live data, it stays in that app.
One pantry for every visual part · came from Mark Parson
- The product's six old copies of the demo tools were deleted, so it now uses the shared ones. In words
- Of 101 product demos, 46 show parts that already live in the shared library, a backlog for the docs site. 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.
From the record: no recorded conversation behind this one.
c23-D1 The boundary test: if it renders UI, it goes in the shared library; if it is wired to app state or APIs, it stays local. — Mark Parson
If it draws something on screen, it goes in the shared library; if it talks to an app's live data, it stays in that app.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Settled where components live
Set the pantry rule and asked for the product's demo pages to be scanned for parts the docs site should cover.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 0
The full record 0 decisions · 4 key-change entries · 750 words · 0 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 c23 →