handover

Gives a finished piece of work to every agent and function that has to act on it, and takes back from each one what it is going to change as a result, so nothing settled is left sitting with the agent

SKILL.md

GitHub

Handover

What it does

Gives a finished piece of work to every agent and function that has to act on it, and takes back from each one what it is going to change as a result, so nothing settled is left sitting with the agent that made it.

Where it happens

The agent does this in eight activities across eight reference processes. Each one names the activity as that process words it.

What to record

Each program at a version, naming the entry condition, every step, every wait, the condition on every branch, and every exit. The hygiene cycle's scope at a version, saying which records it covers and what it has to fix in them. The rule that settles which program takes a contact who qualifies for two, with the date it was decided and who decided it. A dated account of the database between cycles: how many records there are, how many are complete enough to use, and how many may be contacted. The CONVENED and DONE records of everything it convenes. The go record for a program, naming the version that started sending and who said go. The standing readout at the cadence the process sets, and the decision it made after reading it.

That contract covers every activity this abstract agent takes on, and it is repeated in com.agentcatalog.agent/RECORDS.md. What the abstract agent does not do is in com.agentcatalog.agent/NOT.md.