decide-the-conflict

# Decide the conflict ## What it does Applies the rule to the facts, names the clause that decides it, sets the answer against earlier decisions under the same clause, and puts it to a named person to sign with the reason as written. ## Where it happens The agent does this in three activities across one reference process. Each one names the activity as that process words it. - **Apply the Rule to the Facts** - `ref/prt/resolve-a-channel-conflict`, activity 9 - [Resolve a Channel Conflict](../../../../processes/partners/resolve-a-channel-conflict.md) - **Check It Against Earlier Decisions** - `ref/prt/resolve-a-channel-conflict`, activity 10 - [Resolve a Channel Conflict](../../../../processes/partners/resolve-a-channel-conflict.md) - **Have the Decision Signed** - `ref/prt/resolve-a-channel-conflict`, activity 11 - [Resolve a Channel Conflict](../../../../processes/partners/resolve-a-channel-conflict.md) ## What to record Who raised it, on which deal, and what they said the rule gives them. The stop, with the time each side confirmed it rather than being assumed to have. The single account both deals point at, or the finding that they are two customers. The rule at the version in force on the claim date, and the clauses the case turns on. Who was first on the dated record, and by how much. The introduction marked evidenced, asserted or absent. Each side's account as given, and every place it disagrees with the record. The decision with the clause behind it and every fact it cites, the earlier decisions checked, any departure said in writing, and the signer. The one text both sides received and the date they received it. Which side picked the deal up, and what the customer was told. 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`.