contract-playbook-review

1# Contract playbook review
2 
3How a contract reviewer applies a structured deviation policy to a contract, clause by clause, and emits a structured review.
4 
5## The general workflow
6 
7A playbook is a list of clause rules. Each rule names a clause, describes the policy in prose, and encodes the policy as machine-checkable fields (e.g. `max_years`, `acceptable_jurisdictions`, `must_be_present`). Review is a four-step loop, repeated once per clause:
8 
91. **Locate** the corresponding provision in the contract (it may not be present at all).
102. **Apply** the rule — check the contract's position against the policy fields.
113. **Classify** the outcome as `ok`, `risk`, or `reject`.
124. **Record** the finding: a verbatim excerpt that grounds it, a rationale, and the playbook's prescribed action.
13 
14Walk the playbook in order. Don't skip clauses just because the contract is silent on them — silence is itself a finding (`found = false`) and may trigger an action (e.g. "request_addition").
15 
16## Rule types you will see
17 
18A handful of rule shapes cover almost every playbook entry. Recognise them and you can apply them mechanically:
19 
20| Rule shape | Field example | "ok" means |
21|---|---|---|
22| Numeric ceiling | `max_years: 3`, `max_months: 24` | Contract value ≤ ceiling |
23| Numeric floor | `min_years: 1` | Contract value ≥ floor |
24| Must be present | `must_be_present: true` | Provision exists |
25| Must be absent | `must_be_absent: true` | Provision (or specific phrasing) does NOT exist |
26…