design · c121activestarted Oct 23Auto draft — not yet reviewed

Governance v1 Scope

Looks done — ready to closeAll three waves are built and deployed, the Outcome and the session decisions are written, and the next thing (frameworks) is c123's job.· medium confidence

To close: Confirm with Mark that frameworks belong to c123 · Move 'Not done, carried forward' items to c114 or c123 · Retire the Wave 3 PICKUP.md · Move to HISTORY.md

last activity Oct 26 · waiting on c123

Why we did this

Our security advisor showed us how real security teams think about rules, and our screens still showed the old ideas.

What happened

Now every rule has one simple switch, you see who a change affects before you make it, and all changes go live together. Seven screens changed.

Severity, scope and groups as separate sections — Before → afterEach rule has one switch: off, watch, or block. You can set it to change back on a date.

Mode + Until up top; exceptions use the same control — Before → afterEach rule has one switch: off, watch, or block. You can set it to change back on a date.

Documents

With file names, on their own page →

Start here

Documents

Feedback on the intents, from building v1 in the lab

Pages

At a glance

changes

conversations

decisions

outside helpers

Who helped

MPMark PetersonAdvisor RGRob GenovaQpoint team TFTyler FlintQpoint team MPMark ParsonQpoint team

What changed

The three changes that matter most, in plain words. Open any one to see it.

1
Each rule has one switch: off, watch, or block. You can set it to change back on a date.
Everything on the policy page · came from Mark Petersonopen →
2
Before you change a rule, the screen tells you exactly who it will affect.
See who a change affects, first · came from Mark Petersonopen →
3
Changes wait together in one shared list, then go live all at once.
One shared draft, published whole · came from Mark Peterson, Tyler Flint and othersopen →

Also in this cycle

Alerts you were only watching are tucked away, so real problems stand out. Before → after
Each team gets one bar showing how much is blocked, watched or off, next to the whole company. Early → final
You can see which laptops haven't picked up the newest rules yet. New in this cycle
Demos can show a brand-new customer and a mature one, side by side. Before → after

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.

Someone saidWe decidedSo now

Someone said

MPMark PetersonOct 19cited

“Snoozing, not yet. Not polluting the stream...”

market-analyst /calls/154b2679… (local)

MPMark PetersonOct 19cited

“That customer is like, okay. Tell me when. By when. Right?”

market-analyst /calls/154b2679… (local)

→

We decided

D6 Mode is Off · Observe · Enforce with an optional Until, on the policy and on its exceptions. Snooze goes. — Mark Parson

D7 Expiry is optional. Mark Parson proposed requiring an end date when loosening; Mark Peterson kept it optional. — Mark Peterson

D1 A reason is required when an edit loosens and when an exception is revoked. Tightening keeps it optional. — Mark Parson

→

So now

Each rule has one switch: off, watch, or block. You can set it to change back on a date.

Someone said

MPMark PetersonOct 21cited

“I think that's a great feature to communicate why it matters.”

market-analyst /calls/5c8785e2… (local)

MPMark PetersonOct 21cited

Show affected people, teams and the findings a change would resolve or reopen before granting an exception.

market-analyst /calls/5c8785e2… (local)

→

We decided

D19 A change's impact states the facts and stops ("Loosens P-MCP for 3 people in Finance."). "Blast radius" stays out of the UI. — Mark Parson

→

So now

Before you change a rule, the screen tells you exactly who it will affect.

Someone said

MPMark PetersonOct 14cited

“We don't wanna be, like, deploying that. Those two changes live. We sort of wanna, like, stage them.”

market-analyst /calls/04e3d850… (local)

MPMark PetersonOct 14matched · review

“It's super intuitive... everyone has that experience.”

market-analyst /calls/04e3d850… (local)

→

We decided

D4 Local staging stays, in front of one shared draft. Publish makes the whole draft live. No named drafts, approvals or promotes. — Mark Parson

D13 Import validates a pasted or uploaded JSON into the staged edits. A support export strips tokens. — Mark Parson

D26 Changes is renamed Policy Config: Proposed Changes, History and Config File. — Mark Parson

→

So now

Changes wait together in one shared list, then go live all at once.

Thanks to

People outside Qpoint first. Every thank-you points at something they said or made.

Mark Peterson

Advisor · Moto

Shaped the v1 model across four sessions

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.

“You might be able to do sort of, like, a bar that shows proportionally... how special snowflakey are they?” first-hand

Rob Genova

Qpoint team

Kept findings honest and exports safe

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).

“Agents, you know, tend to kinda run wild... there might be a ton of attempts.” internal

Tyler Flint

Qpoint team

Named the hardest problem, so v1 could skip it

Called multi-draft conflict resolution the hardest thing on the roadmap; v1 ships one shared draft and waits for real usage.

“Of all the things that we're doing, this is the hardest, like, without question.” internal

Mark Parson

Qpoint team

Walked the lab and ruled D1–D26

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.