Writing from Katie Kearns and Structured Ink about technical communication, documentation systems, and the human work behind sustainable delivery.
This is the permanent home for Structured Ink articles, field notes, and practical guidance. Search by question, browse by topic, or follow related reading from one Insight to the next.
Structured Ink helps technical teams diagnose the workflows, sources, terminology, ownership, and publishing systems behind documentation problems, then build information people can trust and maintain.
Multi-agent systems create a second security surface: the communication paths, shared state, delegated work, and persistent context that let agents coordinate. Those coordination mechanisms need explicit permissions, logging, attribution, monitoring, and kill controls.
Private companies entering offensive cyber operations face the same boundary problem penetration testers already know, but with harder attribution, third-party infrastructure, changing conditions, and the risk of retaliation. Scope, stop conditions, and evidence have to contain both the action and what comes back.
Enterprise AI needs two kinds of governance: a knowledge control plane that defines what the system may trust and an action control plane that defines what it may reach and do.
The UK AI Security Institute’s cyber evaluation revealed a gap between the boundaries described to AI agents and the controls the technical environment actually enforced. Organizations should constrain agents at least as carefully as they constrain human users.
Structured Ink helps technical teams diagnose the workflows, sources, terminology, ownership, and publishing systems behind documentation problems, then build information people can trust and maintain.