Layer Separation & Project Identity
The style guide was doing three jobs at once: shared parts, brand notes and a website. Its settings needed special switches to know which job it was doing.
The shared parts moved into their own project. The design site now uses them like any other project does, so it feels the same problems everyone else would.
What changed
The change that matters most, in plain words. Open any one to see it.
- 1
Shared parts live in one project; the brand notes and the showcase site live in another.
Two projects, two clear jobs · came from Mark Parson
- The kit's settings no longer need to ask which job they're doing. In words
- The kit got its own package name, keeping the word "design" free for later. 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.
Shared parts live in one project; the brand notes and the showcase site live in another.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Split the kit from the site
The record names no one; the work is in commits authored by Mark Parson, and the split repo's history is his.
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 · 5 key-change entries · 160 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 c2 →