write-the-plan-at-a-version

# Write the plan at a version ## What it does Puts one named owner and one date on every milestone and writes the plan at a version both sides read from the same place, with every blank filled or marked open. ## Where it happens The agent does this in two activities across one reference process. Each one names the activity as that process words it. - **Draft the Plan** - `ref/prt/write-a-joint-plan`, activity 12 - [Write a Joint Plan](../../../../processes/partners/write-a-joint-plan.md) - **Set the Milestones and the Dates** - `ref/prt/write-a-joint-plan`, activity 10 - [Write a Joint Plan](../../../../processes/partners/write-a-joint-plan.md) ## What to record The targets at a version, with the person on each side who confirmed them. The account list with the reason written on each one, and every account removed with the conflict or the owner behind it. The inputs per side with a name against each line, and what our side costs against the budget line it comes from. The milestones with one owner and one date each. The plan at a version, with every blank filled or marked open. At review, the gaps with the reason and the person closest to each, the decision as both sponsors announced it, and the amendment with the changed lines marked against the version they replace. Anybody auditing a run can read what each side promised, what it cost, and what changed since. 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`.