name-what-a-tool-must-connect-to

# Name what a tool must connect to ## What it does Brings the systems either side into the evaluation of a tool, says what that tool would have to connect to, and takes the tool once it has been chosen. ## Where it happens The agent does this in three activities across two reference processes. Each one names the activity as that process words it. - **Brief the Evaluation** - `ref/rev/choose-a-tool`, activity 6 - [Choose a Tool](../../../../processes/revenue-operations/choose-a-tool.md) - **Map What It Must Connect To** - `ref/rev/choose-a-tool`, activity 7 - [Choose a Tool](../../../../processes/revenue-operations/choose-a-tool.md) - **Take in the Chosen Tool** - `ref/rev/integrate-a-tool`, activity 1 - [Integrate a Tool](../../../../processes/revenue-operations/integrate-a-tool.md) ## What to record Per link: the systems either side with the person who owns each, the agreed flows at a version naming every field, its direction, its cadence and what starts the move, and the system of record per field with who decided where the owners could not agree. The known set moved through the link with the counts on both sides, field by field, and every difference. The failure test, saying what the link retried, duplicated, dropped and queued when it was broken on purpose. The cleared review with the date it was signed and every finding accepted rather than fixed. The date and hour it went live, and the way back as it was written down before the switch. The first runs and the reconciled counts, dated, with the reason behind every difference where one is known. The record of what flows where at its version, naming the fields it does not yet cover. When a link stops, what it was carrying and where that now comes from. 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`.