Control-Center Consolidation
To close: Write the Outcome (F1–F10 map, ranked plan, V5 shipped in qcontrol 376baabb) · Point the deep pass at c65 and the governance cycles (c114, c121) · Move to HISTORY.md
last activity Aug 11
Several people had built overlapping dashboard pages for controls, policy and compliance at the same time. The numbers disagreed and the same table appeared twice.
A clear map of the overlap, a ranked list of quick fixes, and an edit-in-place card for controls that shipped to the product. The deeper redesign went to the next cycle.
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
Click a control and a card opens beneath it: what it is on top, how to change it below.
Read and edit a control in place · came from Mark Parsonopen →
- 2
Ten numbered findings explain where the controls, policy and compliance pages overlap.
The overlap, written down
- Four rough ideas for merging the pages, side by side on one page. New in this cycle
- The big grid of framework cards became a short row of chips with an add button. New in this cycle
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.
c64-D1 Start from the existing controls table and iterate on a faithful copy of it. — Mark Parson
c64-D2 Extend the scope to product code: the framework picker and the control card go into qdash. — Mark Parson
c64-D3 Keep the actions column in the controls table. — Mark Parson
Click a control and a card opens beneath it: what it is on top, how to change it below.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
Ten numbered findings explain where the controls, policy and compliance pages overlap.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Picked the starting point and pulled the work into the product
Chose to iterate on a faithful copy of the live controls table, extended the cycle to change product code, and kept the actions column. The control detail page follows his screenshot.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 7
The full record 3 decisions · 18 key-change entries · 1,642 words · 7 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 c64 →