A process is a lifecycle you can run.

A map says what ought to happen. A process says who holds each step, what passes between them, and what happens when a step goes wrong. Copy one of these, put your own holders in it, and run it.

Each is written in the open Agent Processes format, so an orchestrator can run it.

Make a new agent

A request in words becomes a running agent. The owner says yes at three gates, and agents hold the rest.

  1. Write the specthe statement of the job drafted, with its open questionsspec writer, with the owner
  2. Approve the spec a personthe owner answers the open questions and says yesthe owner
  3. Write the suitetests from the statement alone, shown to fail against nothingtest writer
  4. Write the scriptsthe programs the statement names, passing the suitecode writer
  5. Make the package on-rampthe package made from the statement and the programs, then signed at Releasepackage maker
  6. Approve the deploy a personthe owner reads the signed build record and says yesthe owner
  7. Deploy the agent goes livethe package installed with its credentials and limits in place, or the running agent updateddeployment manager
  8. Check conformancethe package's own declarations tested on the agentconformance checker
  9. Publish the agent a personthe owner reads the AgentDoc and says it may be listed in the catalogthe owner

To change an agent, start at Impact, then Update.

Read Make a new agent at agentprocesses.ai

Make a new process

A request in words becomes a running process. The owner says yes at three gates, agents hold the rest, and a step that needs an agent nobody has built runs Make a new agent first.

  1. Write the processthe process document drafted: its steps, who holds each, what a run is handed and where a person signs, with its open questionsspec writer, with the owner
  2. Approve the process a personthe owner answers the open questions and says yesthe owner
  3. Find the holderseach step given an agent that already does it, or a new agent made by Make a new agentcatalog
  4. Write the test casesfrom the document alone: what each run is handed, how each approval is answered, and what must be true at the endtest writer
  5. Wire itthe holders bound, and each handoff fitted to the step that receives itcode writer
  6. Run the suiteevery test case run as a test run, with nothing reaching outsidethe process runner
  7. Sign the process on-rampthe document and its test cases pinned by digest, then signed at Releasepackage maker
  8. Approve the install a personthe owner reads the signed record and says yesthe owner
  9. Install the process goes livethe process filed with the organization's processes and bound to its triggerdeployment manager
  10. Check conformancethe document checked against the specification, and the suite passedconformance checker
  11. Publish the process a personthe owner says it may be listed in the catalog as a process entrythe owner

To change a process, start at Impact, then Update. Why the same stages serve both is on What it builds.

Record an incident

An agent goes quiet, or a job fails. The process builds a timeline from the records, marks the gaps, and never guesses a cause. Deciding what to do stays with a person.

  1. Notice the failurethe quiet agent or failed job, and the timewatcher, or a person
  2. Gather the records a personthe platform's and the agent's records, attachedthe incident owner
  3. Record the incidenta timeline naming every fact's source and every gapincident recorder
  4. Decide what happens a personleave it, restart it, retire it, or change itthe incident owner

Read Record an incident at agentprocesses.ai

Retire an agent

Stopping an agent is easy. Retiring one means the address stops answering cleanly, the records outlive the agent, and someone decides what happens to the name.

  1. Say what goes a personthe agent, the reason, and who must be told firstthe owner
  2. Retract the listingthe listing taken out of the catalog by whoever listed it, on the owner's decisionpublisher
  3. Approve the removal a personthe owner reads what will be removed and says yesthe owner
  4. Remove the agentthe deployment manager instructed to remove it allthe owner and the deployment manager
  5. Close the AgentDoc a personthe AgentDoc marked retired, with date and reasonthe owner

Read Retire an agent at agentprocesses.ai