work-through-the-markup

# Work through the markup ## What it does Sends the draft out at a version, gathers every markup into one numbered list, and marks each requested change give, trade or refuse with the reason and the internal approval that cleared it. ## Where it happens The agent does this in three activities across one reference process. Each one names the activity as that process words it. - **List Every Change They Ask For** - `ref/prt/sign-a-partner-agreement`, activity 9 - [Sign a Partner Agreement](../../../../processes/partners/sign-a-partner-agreement.md) - **Price and Sort the Changes** - `ref/prt/sign-a-partner-agreement`, activity 10 - [Sign a Partner Agreement](../../../../processes/partners/sign-a-partner-agreement.md) - **Send the Draft and Take the Markup** - `ref/prt/sign-a-partner-agreement`, activity 8 - [Sign a Partner Agreement](../../../../processes/partners/sign-a-partner-agreement.md) ## What to record Every draft at a version, with what changed from the version before it. The numbered change list, each change marked give, trade or refuse, with the reason and the internal approval that cleared it. The departures from the standard terms listed apart from the standard terms, so a reader can see in one place what this partner got that others did not. Each qualification condition traced to the term that carries it, or to the person who decided to drop it. The final read of the text against the agreed list, term by term. The executed copy with its date and the people it went to. 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`.