Investigate incidents, prepare release communication, and keep every source, tool call, and proposed change available for review.
Engineering agents should reduce investigation time without becoming an unbounded production operator. d5s gives each run an isolated workspace, scoped connectors, and explicit approval boundaries, so evidence gathering can move quickly while changes remain under accountable human control.
4 ready-made coworkers, each arriving with a persona, standing instructions, a wake-up schedule, and its connectors chosen.
Both work. What changes is how much context a single coworker builds up, and how many separate approvals you give.
One coworker takes on several jobs. Everything it has seen stays with it, so context from last week's work carries into this week's.
Each coworker keeps a narrow scope, its own wake-up schedule, and its own approval boundary. Changing how one works cannot affect the rest.
You are not choosing once. Most engineering teams start with a single coworker and split it later. The usual sign is writing standing instructions that contradict each other, or wanting two different people to sign off on what is currently one coworker's work.
6 systems across this team's agents. Each one reads only the sources it was given.
Each one arrives with a persona, standing instructions, a wake-up schedule, and its connectors chosen. Nothing runs until you add it.
