Control-Center v2
To close: Move the existing Outcome to HISTORY.md · Add a line that the framework research feeds c123
last activity Aug 12
Every control had to be hand-built from rules, conditions and actions. That was more setup than an operator should ever have to face.
A catalog of 17 ready-made policies, each switched on with a toggle and driven by the compliance frameworks you choose. It replaced the controls page in the product.
Documents
With file names, on their own page →Start here
Pages
- /pages/compliance-frameworks
- /pages/control-verification
- /pages/policy-catalog-v2
- /pages/policy-catalog-v3
- /pages/policy-config-agent-registration
- /pages/policy-config-credential-protection
- /pages/policy-config-data-redaction
- /pages/policy-config-egress-allowlist
- /pages/policy-config-mcp-allowlist
- /pages/policy-config-no-root-execution
- /pages/policy-config-org-backed-identity
- /pages/policy-config-output-validation
- /pages/policy-config-posture-floor
- /pages/policy-config-prompt-inspection
- /pages/policy-config-provenance-pinning
- /pages/policy-config-quota-compliance
- /pages/policy-config-require-tool-approval
- /pages/policy-config-sandbox-required
- /pages/policy-config-spend-ceiling
- /pages/policy-config-tls-floor
- /pages/policy-config-tool-allowlist
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
You choose the frameworks you must meet; the page shows which ready-made policies they need, and you switch those on.
Frameworks pick the policies · came from Mark Peterson and Mark Parsonopen →
- 2
Each policy has a focused settings page; the egress one lets you approve or block new destinations.
A settings page per policy · came from Mark Parsonopen →
- Each framework was read for what it asks of AI agents while they run, and mapped to policies. In words
- The dashboard's controls page became the policy catalog, and the old policy page was removed. 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.
“Intuitive and yep. I've seen similar patterns.”
market-analyst /calls/2100ac03… (local)Advisor reacted positively to MCP server allowlist and other agent-specific controls being pre-mapped into a control center.
market-analyst /calls/2100ac03… (local)c65-D1 The ready-made units are called Policies; the flexible Controls engine sits beneath them. — Mark Parson
c65-D2 The framework catalog is the union of twelve: the backend's packs plus the frontend's list. — Mark Parson
c65-D4 Keep the custom-control builder as a quiet escape hatch. — Mark Parson
You choose the frameworks you must meet; the page shows which ready-made policies they need, and you switch those on.
From the record: no recorded conversation behind this one.
c65-D3 One settings page per policy, built on about five shared shapes. — Mark Parson
Each policy has a focused settings page; the egress one lets you approve or block new destinations.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
Found the framework-first catalog intuitive
On the Aug 20 product review, eight days after it shipped, he called the framework toggles intuitive and familiar, and welcomed agent-specific policies such as the MCP server allow-list being pre-mapped.
“Intuitive and yep. I've seen similar patterns.” first-hand
Made compliance frameworks the driver
His prompt asked for narrow policies you switch on and configure in context, with frameworks toggled globally deciding health and posture; he set the kick-off choices and renamed the compliance column.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 22
The full record 4 decisions · 16 key-change entries · 1,985 words · 21 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 c65 →