Most teams already know their positions. The liability cap, the renewal term, the data-use language, the fallback they will accept if the other side pushes. That knowledge usually lives in a partner's head or in a document nobody opens during the review.
Teams can keep the clauses they actually use as playbooks. A playbook is the set of positions for that kind of agreement, saved so the next review starts from them instead of from a blank page.
During a redline turn, AI review sits beside the contract. It points at issues against that playbook, in a sidebar next to the draft, while the turn is open. The reviewer sees the clause in the document and the playbook issue next to it, and can decide what to do with the markup from there.
The playbook is yours. The review compares the draft to the clauses the team saved, not to a generic list of contract topics.
