Nine agents work on this server, and most of them start themselves. Each one writes down what it ran, what it decided, and what it cost. The numbers you read below are counts of things that happened, not claims about what these agents could do. A tenth agent is on the list as a design nobody has built yet.
Coordinates the others, approves their work, and never writes any of it itself.
130 runs since 27 June. Holds a chat line open all day for questions, and files a written brief every morning at seven.
The separation is deliberate: the agent that decides is not the agent that produces, so nothing here marks its own homework.
Reads the server's own health every morning and writes up what it finds.
Runs unattended at 06:20 every day since 25 July.
It proposes and never applies. Every fix is a written recommendation a person has to accept — which is also why its findings can sit unresolved, visibly, until someone acts.
Asks what this server hands out to a stranger — the one question the morning health check is not built to ask.
Specified 6 August, the day an audit found the Studio serving a private repository's git directory to anyone who requested it.
The sysadmin agent had run every morning for nearly two weeks and never saw it. That isn't a failure: all six of its checks look inward, at whether the server matches what was declared about it. None of them asks what an outsider can reach. That gap is why this is a second agent rather than a seventh check — and it isn't built yet, so it has found nothing on its own.
Answers visitors' questions about a solution, on that solution's own page.
Five of them so far, one for each solution page that has one. Each is built from the same facts that built the page it sits on.
Each one knows a single solution and refuses every other subject, so it cannot answer questions it has no facts about.
The agents that turn the server's own written record into stories.
finds → sorts → writes → publishes · 248 story leads filed · 2 notes published
See the newsroom →
