Source: c124 cycle-stories, option D. The change itself leads: one big compare per outcome, with who it came from beside it. Fixture from the c121 record and market-analyst calls.
Governance v1 Scope
activeWaves 1–2 committed 2026-10-23; Wave 3 nextWhy: One week of conversations with our CISO advisor reshaped the governance model, and the lab still showed the positions those conversations had overturned: snooze, named drafts with approval, required expiry dates, noisy findings.
Everything on the policy page
← → to move between outcomes
In plain words
Think of a company's rules for its AI helpers as a set of light switches: off, watch, or block. This week we agreed each rule gets one switch, and if you ever loosen a switch you have to say why. Before you flip it, the screen tells you exactly who it affects. All the flips wait in one shared cart and go live together, like checking out. This cycle made every screen in the lab work that way.
“The policy is where everything happens.”
Mark Parson · Wednesday session, 53:33
Thanks to
Moved mode onto the policy and retired snooze; asked to see a change's impact before making it; kept expiry optional; proposed the team posture bar, propagation per version, config import and the onboarding-vs-mature demo. His intents PR #4 and v1 scope note set the cycle's scope.
Asked for each finding to keep the policy version it was detected under (D16), flagged the findings flood from agents running wild (D3), and caught that exported configs could carry tokens (D13).
Called multi-draft conflict resolution the hardest thing on the roadmap; v1 ships one shared draft and waits for real usage.
Turned the week into the lab: made the loosening reason required, renamed Changes to Policy Config, and ran the Friday walkthrough where nobody asked for changes.
The record 2,270 words · 9 key changes · 26 decisions · 28 captures
Key Changes, every decision, artifacts and the full visual record stay as written in CYCLE.md. Open the live c121 page →