04 — Scene
Security · governance
Agent control plane
Keep a ledger of the keys before you hand them to an agent.
When an agent starts changing data, sending messages, triggering payment or opening access, security does not ask about accuracy. They ask who authorised it, what it may do, and how it stops. Spreading a pilot without a control plane is a bet against the company’s service accounts.
We treat each agent as an identity that has to be managed: tool allow-lists, action-level approval, context isolation, output filters, full traces. Widening capability and tightening the boundary ship on the same train — not in two separate meetings.
In the work
Identity before the model
Every agent has a service identity and an owner. It does not share the ops login.
Action policy
Reads can be wide. Writes stay narrow. Payment, deletion, outbound send escalate to a person by default.
Revocation
Key rotation, tools taken offline, sessions voided. Governance needs a stop, not only a report afterwards.