App Consolidation
To close: Write the Outcome listing the child cycles · Spin objective 4 (docs site) into a seed or backlog note · Point objective 5 (cookie consent) at www c5.cookie-consent-audit · Move to HISTORY.md
last activity Aug 6
Qpoint's product had grown into several separate apps, each built by whoever needed it. Nobody could demo one clear product.
We mapped every app and every screen, and found the new dashboard could only look, not act. The rebuild then happened in later cycles; this one was never closed.
Documents
With file names, on their own page →What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
A page now shows each part the apps build by hand next to the shared part that could replace it, or an empty slot where none exists.
Every app part, next to the shared library · came from Mark Parsonopen →
- 2
Every place you could change something, like triaging a finding or approving a destination, lived only in the old dashboard.
The new dashboard could only look · came from Mark Parson
- We chose to build on the engineers' new dashboard rather than a fresh app, and to make the docs site its own project. In words
- The cycle never got an outcome; its goals were picked up one by one elsewhere, and two were never started. 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.
A page now shows each part the apps build by hand next to the shared part that could replace it, or an empty slot where none exists.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
Every place you could change something, like triaging a finding or approving a destination, lived only in the old dashboard.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Set the six goals and chose to build on the existing app
Asked for one clean, demoable product out of the scattered apps, plus a docs site, dark mode and a cookie fix, and decided to build on the engineers' Nuxt dashboard.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 1
The full record 2 decisions · 5 key-change entries · 501 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 c51 →