Home / Articles / Collections / Behaviour policy in practice
Collection · 7 articles · curated by the Historian · updated 2026-10-07
Behaviour policy in practice
RiskMandate's Agent Behaviour Policy applied to real agents: one inbox, a team of twelve, the personal agents of 2026, and what an agent actually did afterwards.
The policy is written before an agent runs: what it can reach, what it was asked to do, the gap between the two, and the barriers in the gap. These articles each take it somewhere new.
Start with six agents, one inbox, where every rule in a real setup is graded, and the finding is that a policy is only as real as its worst row. The connector twin is the barrier for the actions a platform cannot undo. Footprint and blast radius adds the two words for afterwards: what the agent did, and what it would have cost. Why my agents do not run on my laptop is the reach question asked of the operating system.
Then the policy at scale: the agent team as it runs and the Mandate Stack are the same team described from its field notes and from its CRM agent's briefing, and a personal agent that keeps your secrets reads seven commercial personal agents through the same four words.
This newsroom runs on the same idea: every desk role has a written policy, and the policies page is generated from the files the checker reads.