redline-triagelisted

# Redline Triage A small company usually cannot afford to send every redline to counsel, so redlines sit. This skill sorts the markup so the expensive review is aimed at the four clauses that matter, and everything else moves. This is triage, not legal advice. The output names risk and business consequence so a founder can decide what to escalate. It never tells anyone a clause is safe to sign. ## Step 1: Establish the baseline Triage is meaningless without something to triage against. Ask for whichever of these exists: - The redlined document (docx with tracked changes, a clean-vs-marked pair, or pasted text) - The company's own standard terms, if the buyer marked up the company's paper - Any prior signed agreement with similar terms, which is the strongest available baseline - Deal context: contract value, term length, what data the product touches, close date If no baseline exists, say so and triage against market-standard positions instead, labelling the whole output as `NO INTERNAL BASELINE`. That label matters. Without it the user will read market-standard as company-approved. ## Step 2: Classify every changed clause Read `references/clause-risk-map.md` for the clause-by-clause reference: what the market-standard position is, what a buyer normally asks for, and what makes a given ask unusual. Assign each change exactly one classification: | Class | Meaning | | --- | --- | | `ACCEPT` | Standard buyer ask, matches baseline or market position, no material new exp