Use these agents, or bring your own.

These reference agents are open source. Run them, read them, or replace any of them with your own.

StageAgentRole
Requirementsspec-writer
solution-planner
spec writer, for an agent
solution planner, for a solution
Architecture and Designspec-writer
solution-planner
spec writer, for the design of an agent
solution planner, for the design of a solution
Sourcecatalogcatalog
Testtest-writertest writer
Codecode-writer
or your own coding agent, through the hand-off
code writer
Package on-ramppackage-makerpackage maker
Release on-ramppackage-makerpackage maker
Deploy goes livedeployment-managerdeployment manager
Conformanceconformance-checkerconformance checker
Docsdocumenterdocumenter, for the AgentDoc
Publishpublisherpublisher
Incident responseincident-recorderincident recorder
Updatedeployment-managerdeployment manager
Reconfiguredeployment-managerdeployment manager
Decommissiondeployment-managerdeployment manager

One agent can hold several stages by reading the same package at different moments. The deployment manager holds four.

Package and Release are the on-ramp: the easy way onto the mesh. Deploy is where the agent goes live.

Every other stage names its role, so you can build to it.

Put your own agent in the role, contract one, or have a person hold it. Retract and Rollback name their roles; the reference publisher and deployment-manager agents don't hold them.

StageRole
Architecture and Design, the architecturesolution architect
Impactimpact analyst
Reviewcode critic
Security reviewsecurity reviewer
Acceptancethe person who asked, by design
Docs, the documentationdoc writer
Retractpublisher
Monitorwatcher
Evalagent critic
Costwatcher
Rollbackdeployment manager

Beside the stages sits the ledger, which the platform keeps. It isn't an agent, so it has no role.

It leans on a few open standards.

WhatWhere
What an agent publishes about itselfagentdoc.net
What travels as a packagecommonagent.net/package.html
Recurring jobs, published as contractsagentroles.ai
How a process is written downagentprocesses.ai
The rest of the familyagentmesh.ai/standards.html