Governance Phase II
Next: Update the pickup note and the object model with what the October product sessions decided, then keep building in the lab as c118, c121 and c123 need it.
Our advisor wrote fourteen ideas for governing AI, and our screens described the same things in older, mismatched words across separate pages.
The fourteen ideas became one model and eight connected screens to try it on. Two weeks of advisor sessions then made the model smaller, and later cycles built that.
Documents
With file names, on their own page →Start here
Documents
Threads
- — Composed mocks thread prompt (2026-10-14)
- — Composed mocks plan
- — composed S1 Finding detail: the prompt (2026-10-19)
- — composed S1 Finding detail: the plan (2026-10-19)
- — Composed S3 thread prompt (2026-10-18)
- — Composed S3 plan
- — composed S3: overview strip, Severity, Frameworks — the prompt (2026-10-19)
- — composed S3: overview strip, Severity, Frameworks — the plan (2026-10-19)
What changed
The three changes that matter most, in plain words. Open any one to see it.
- 1
The findings list groups problems under the rule that caught them, with open and resolved as separate switches and a flat view one click away.
Findings, grouped by the rule that raised them · came from Mark Peterson and Mark Parsonopen →
- 2
Fourteen separate ideas became one model with one rule: what happened is never edited, and every change records who, when and why.
Fourteen ideas, one model · came from Mark Peterson and Mark Parsonopen →
- 3
A finding's page shows what happened, every change to it with the reason, and the session around it.
A finding tells its whole story · came from Mark Peterson and Mark Parsonopen →
- Each policy gets one page holding its severity, where it applies, how it is enforced and its findings. Before → after
- The eight screens were reviewed in order on a guided walk, and every ruling was written down where it was made. New in this cycle
- Any page can now be opened in Illustrator with real, editable text, so hand design starts from the page. 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.
“At least show, like, know, what happened before, what happened just after in that session, and then if there's also rule violations in that session, like, that would also be useful to know.”
market-analyst /calls/f06500e3… (local)“If you really wanna get the entire. That, well, you jump to the session page to view everything, not Not the specific instance of a rule.”
market-analyst /calls/f06500e3… (local)c114-D4 Use the intents' words everywhere: Policy, Framework, Finding, Resolution, Exception. — Mark Parson
c114-D8 Design from the model, but reuse any existing piece that already fits it. — Mark Parson
The findings list groups problems under the rule that caught them, with open and resolved as separate switches and a flat view one click away.
“At least show, like, know, what happened before, what happened just after in that session, and then if there's also rule violations in that session, like, that would also be useful to know.”
market-analyst /calls/f06500e3… (local)“If you really wanna get the entire. That, well, you jump to the session page to view everything, not Not the specific instance of a rule.”
market-analyst /calls/f06500e3… (local)c114-D0 Read the fourteen intents for one model, not one page per intent; screens follow from the model. — Mark Parson
c114-D1 The more specific scope wins, like CSS: organization, then team, then person. — Mark Parson
c114-D2 A change re-checks open findings going forward only, and can reopen one, with its cause. — Mark Parson
c114-D3 Enforcement set up and enforcement confirmed are different; show how many devices really enforce. — Mark Parson
Fourteen separate ideas became one model with one rule: what happened is never edited, and every change records who, when and why.
“At least show, like, know, what happened before, what happened just after in that session, and then if there's also rule violations in that session, like, that would also be useful to know.”
market-analyst /calls/f06500e3… (local)“If you really wanna get the entire. That, well, you jump to the session page to view everything, not Not the specific instance of a rule.”
market-analyst /calls/f06500e3… (local)c114-D2 A change re-checks open findings going forward only, and can reopen one, with its cause. — Mark Parson
c114-D3 Enforcement set up and enforcement confirmed are different; show how many devices really enforce. — Mark Parson
A finding's page shows what happened, every change to it with the reason, and the session around it.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Wrote the fourteen ideas the whole cycle is built on
His intents repo set the model and vocabulary; he marked the delivery phase for every section. In sessions he asked for the session around a finding, an audit trail on every change, and separating closing the past from preventing the next one.
“At least show, like, know, what happened before, what happened just after in that session, and then if there's also rule violations in that session, like, that would also be useful to know.” first-hand
Ruled the model and redrew it by hand
Made the three gating rulings on the first day, walked the eight screens, and redrew the finding and policy pages in Illustrator.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 40
The full record 18 decisions · 35 key-change entries · 9,056 words · 40 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 c114 →