// Kesslernity · Govern Your Agents
A Copilot agent fails governance in two different places: the name it can never change, and the instructions that decide what it does. This bundle fixes both.
$47 for both · $58 bought separately
The first is the name. Get it wrong and the agent disappears into a four-thousand-row inventory of New Agent and cr8a3_copilot1 that no auditor can sort. The schema name locks at creation, so there is no rename later.
The second is the instructions. Get those wrong and the agent drifts off task, answers things it should refuse, or quietly does work nobody approved. A perfectly named agent with sloppy instructions is still a liability.
# the registry export nobody can govern New Agent created by ? · does ? · approved by ? cr8a3_copilot1 name locked at creation — no rename Copilot final (2) instructions: "be helpful" · refusals: none # after both controls copart_finvarrpt001 → Finance Variance Reporter name: sorts + audits cleanly instructions: scoped, refusals set, on-task
The governance-first naming convention for M365 Copilot agents: the two-name model (immutable schema name vs editable display name), the canonical system-name regex, the four enforcement points that make a name right before the agent exists, and the framework to design your own convention if the ready-to-adopt one doesn't fit.
The instruction patterns for agents that actually hold — extracted from building 52 real Copilot Chat agents in production. The patterns for scoping an agent, setting its refusals, keeping it on task, and wiring the description and knowledge sources so generative orchestration reads them correctly.
Together they are the full control surface: the name an auditor sorts on, and the behavior a reviewer can trust.
If you're governing agents, you need both controls, and you need them to agree. The naming convention tells your intake form what to generate; the instruction patterns tell it what to require in the description and refusals. Buying them together gets you the matched pair for less than buying them one at a time, and it's the natural setup for the full rollout in the M365 Copilot Deployment Kit if you go that far.
$47 for both ($58 bought separately). Free updates on both re-deliver through Gumroad when the platform shifts. Team use included inside your org. The bundle delivers two separate downloads — the Naming the Swarm package and the Agent Instruction Block Design Guide.
Yes. The bundle delivers both products: the Naming the Swarm package (book in PDF, EPUB, and HTML, plus the toolkit) and the Agent Instruction Block Design Guide.
Yes — buy the one you're missing standalone (Naming the Swarm or the Agent Instruction Block Design Guide). The bundle is only the discount for getting both at once.
No. Both use neutral, universal examples (the book uses the fictional org Contoso). You map them onto your own org without translation.
No. This bundle is the two governance controls for agents specifically: naming and instructions. The Deployment Kit ($97) is the full Copilot rollout — field guide, 90-day adoption roadmap, governance checklist, ROI template, and agent templates. If you're running a whole deployment, the Kit is the upgrade. If you're governing the agents themselves, start here.
Kesslernity builds governed AI agents and the controls that keep them auditable at enterprise scale.
store.kesslernity.com · kesslernity.com · 2026