← Cycles
design · c65activestarted Aug 12Auto draft — not yet reviewed

Control-Center v2

Looks done — ready to closeIts own Outcome already says the full arc shipped in one cycle (research, P1–P17, mocks, layer v0.9.8, qdash); it was just never moved.· high confidence

To close: Move the existing Outcome to HISTORY.md · Add a line that the framework research feeds c123

last activity Aug 12

Why we did this

Every control had to be hand-built from rules, conditions and actions. That was more setup than an operator should ever have to face.

What happened

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.

Before → afterYou choose the frameworks you must meet; the page shows which ready-made policies they need, and you switch those on.

Start here

At a glance
4
changes
1
conversation
4
decisions
1
outside helpers

What changed

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

  1. 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. 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 →

Also in this cycle
  • 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.

Someone said
MPMark PetersonAug 20matched · review

“Intuitive and yep. I've seen similar patterns.”

market-analyst /calls/2100ac03… (local)
MPMark PetersonAug 20matched · review

Advisor reacted positively to MCP server allowlist and other agent-specific controls being pre-mapped into a control center.

market-analyst /calls/2100ac03… (local)
We decided

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

So now

You choose the frameworks you must meet; the page shows which ready-made policies they need, and you switch those on.

Someone said

From the record: no recorded conversation behind this one.

We decided

c65-D3 One settings page per policy, built on about five shared shapes. — Mark Parson

So now

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.

MP
Mark Peterson
Advisor · Moto

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
MP
Mark Parson
Qpoint team

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

Frameworks pick the policiesBefore → after
→
A settings page per policyNew in this cycle

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 →

Qpoint Brand Style Guide