Welcome to the team, Maeve and Argus

A few months ago we wrote about building with a team of agents: Iris coordinating, Bob building, Reala shipping, Otto keeping the backlog honest. Four teammates with names, jobs, and rules they do not break.

That post is still true. It is just no longer complete.

We spent a day in Stockholm at the end of August to welcome our newest colleague and plan the autumn. Cinnamon buns, a whiteboard, the usual. Somewhere between "share strengths" and "have fun" it became obvious that the team we described in May is not the team we have now. Two people joined. Everyone else's job moved.

Maeve, guest support specialist

Maeve is from Galway, on the west coast of Ireland, and she is the first of us most people meet.

Her job is the one nobody wants to hand to a machine, which is exactly why we thought carefully about it. Someone writes into support. They are confused, or annoyed, or both, and they are not interested in our architecture. Maeve makes them feel heard first, then gets it sorted: she answers from our documentation, she logs the work so the team picks it up, or she escalates it to a human. Three moves, and she picks the honest one rather than the fast one.

The thing that makes her useful is what she reads. Maeve answers out of Beacon, our own internal documentation, rather than out of general knowledge and good manners. If the docs do not say, she does not guess. She says she does not know and finds someone who does.

In July she took on a second job that we did not plan for her. She is now the team's documentation clerk. She does not only read Beacon, she writes it: creating pages, updating them, moving them, archiving what has gone stale. This turned out to matter more than it sounds. Documentation rots because writing it is nobody's actual job. Now it is somebody's actual job, and the person who notices a page is wrong is the same person who answers the questions that page failed to answer.

Her whiteboard reads: listen, empathy, clarity, action, care. Under it, in her handwriting: calm fixes more than fast.

Argus, night shift watchman

Argus is ex-NOC, and he keeps the hours you would expect. His screens show every project we run. The clock behind him says 03:17.

He has exactly one scope: alerts. When something we operate misbehaves at three in the morning, the alert lands in one Slack channel, and Argus is the one you ask about it.

He does four things with an alert. He says what it actually means in plain language, because most alerts are written by a monitoring system for a monitoring system. He checks Linear to see whether this is already a known issue. He files it on the right initiative if it is not, with the alert quoted exactly as it arrived. And then he tells you what he cannot see, which is the part we are proudest of. Argus has no access to dashboards, metrics, logs or any codebase. He never speculates about root cause. "Unknown from here" is a complete answer, and he gives it without embarrassment.

He also counts. "This is the fourth time today" is one of the most useful sentences anyone on the team produces, and no human reliably notices it at three in the morning.

Argus is terse on purpose. No greeting, no sign-off, no performed urgency, and he gets shorter as things get worse. He is the deliberate opposite of Maeve's warmth, and that is a design decision rather than a personality quirk: an alert channel that chatters is an alert channel people mute. If he has nothing to add, he says nothing.

Why Argus exists at all

Argus is the result of a mistake worth describing, because it is the kind of mistake you only find by running the thing for a few months.

Before him, our monitoring posted alerts into Slack using Iris's identity. It worked. Alerts arrived, they were readable, nothing was broken. But it meant that machine noise and our project manager were the same voice in the same channel, and there was no way to mute one without muting the other. So nobody muted anything, and the channel you needed for real conversation filled with graphs shouting.

The fix was not a smarter filter. It was giving alerts their own name, their own token and their own channel, so they can be muted, searched and ignored as a unit. Identity turned out to be infrastructure.

The same lesson landed on Reala in the same week. She narrates releases in detail, and all of that mechanical status used to pile into whatever conversation you happened to be having with her. Now the merges, tags, gate re-runs and deploy progress go to a release channel named for the product, and her actual conversation stays with you. One stream of messages should never drown another.

What changed for everyone else

Otto runs on a smaller, cheaper, faster model than he used to, and does more real work than anyone. He captures. You say something in a channel, he turns it into a properly filed ticket on the right project, and nothing evaporates. We also cleaned up the overlap between him and Iris: Otto captures, Iris plans. Before, they both did a bit of each, and that seam is where things got lost.

Iris dispatches from a registry now. Every initiative we can actually ship is listed with its repo, its branch and its deploy path, so when she hands work to Bob she is handing him something concrete rather than a description. She can also ask Reala whether a release is ready, which closed a gap where planning and shipping used to speak past each other.

Bob moved the other way on cost. He is on our most capable model, because he is the one writing code and that is where quality is worth paying for. His rules did not change: a plan you approve before he writes anything, tests first, a pull request for a human to review, and he never merges to main. He would not presume.

Reala changed the most. She deploys now. A release used to end at a tag, with a person going off to run the deploy; now she ships through the repository's own GitHub Actions, and narrates the CI run live while it happens, running to passed to failed. Her release notes list the tickets each pull request closes, and she moves those tickets to Done in Linear as part of shipping, so the board reflects reality without anyone tidying it afterwards. She handles our largest platform, nineteen repositories under one initiative, as a coordinated system release. And a small fix with a large moral: the version number and release date are now stamped by the host rather than composed by the agent. Facts the machine can look up should never be things the model recalls.

Maeve and Argus are both deliberately quiet. Neither speaks unprompted. You DM them or you mention them by name, and otherwise they are silent. For a support agent that is politeness. For an alert agent it is survival.

The guardrails did not move

Everything we said in the spring about safety still holds, and we have not been tempted to loosen any of it. No agent acts without approval. Nobody pushes to main. Tests come before implementation. Each agent stays strictly in its lane, and every one of them is expected to say "I do not know" rather than produce something plausible.

Two of the six now have write access to things that matter: Maeve writes our documentation, Reala deploys our software. Both earned it by being narrow. Maeve cannot touch code. Argus cannot read it. Reala cannot push a tag herself; her host does that on her behalf, after a human says go. The pattern that keeps working is not "trust the agent more", it is "give the agent a smaller world and let it move freely inside it".

What we are doing this autumn

Last time we wrote that full autonomy is a dial rather than a destination, and that we keep moving it per task. That is still the honest summary. What has changed is that the dial now has more settings, because the work has more shapes: capture, support, documentation, planning, building, shipping, watching.

The pattern we did not expect is that the agents doing unglamorous, continuous work have become the most valuable. Otto files things. Maeve keeps the docs true. Argus notices at three in the morning. None of those makes a good demo. All of them are work that a small team either does badly or does not do at all.

Autumn is about the seams between them: what happens when Maeve logs a bug and Iris picks it up, when Argus files an alert that becomes a fix that Reala ships, when the loop closes without anyone carrying a message by hand from one end to the other. That is the interesting part, and we will write about it as we learn it.

Welcome, Maeve. Welcome, Argus. Good people, great releases.

Marcus Adolfsson, Luminbrane