AI Agent Policy Pages
Our policy wireframes still used old-style data like where data is stored, when the real risk is now AI agents reading secrets and running destructive commands.
The policy wireframes now tell an AI agent story: six agent policies, and one real incident traced second by second. Good enough for demos.
What changed
The two changes that matter most, in plain words. Open any one to see it.
- 1
The wireframes follow one real incident from the first secret read to the blocked connection.
One incident, second by second
- 2
Policies now say when they check (reading a file, connecting out, running a command) and what they do.
Policies that fit agents
- A trust score sits on every policy and violation, and agents get permission levels. 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.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
The wireframes follow one real incident from the first secret read to the blocked connection.
From the record: no recorded conversation behind this one.
No ruling needed: the work itself is the change.
Policies now say when they check (reading a file, connecting out, running a command) and what they do.
Thanks to
People outside Qpoint first. Every thank-you points at something they said or made.
All images
Every picture from this cycle. Click any one to step through them all.
The pairs
Everything captured · 1
The full record 0 decisions · 4 key-change entries · 428 words · 0 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 c45 →