App Migration & Component Documentation
The app still kept its own copies of parts already in the shared kit, and only 12 of the kit's 43 parts had a working demo.
The app dropped 51 copied files and now uses the shared kit. The design site gained 20 demos, so 32 of 43 parts can be tried live.
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
The app now gets 51 of its parts from the shared kit instead of its own copies.
The app uses the shared kit · came from Mark Parson
- 2
The design site gained live demos for 20 more parts, including a new Table group.
Twenty more parts you can try · came from Mark Parsonopen →
- Plugging the app in exposed two bugs in the kit, and both were fixed. 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.
No ruling needed: the work itself is the change.
The app now gets 51 of its parts from the shared kit instead of its own copies.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
The design site gained live demos for 20 more parts, including a new Table group.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Moved the app onto the kit
The record names no one. The app's layer-integration commits and the design commits are authored by Mark Parson.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 2
The full record 0 decisions · 5 key-change entries · 173 words · 2 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 c3 →