MSCD contracts
This skill makes contract language say 1 thing, clearly, the way Ken Adams's A Manual of Style for Contract Drafting (MSCD5, 2023) prescribes, as updated by his blog through October 2026 and adjusted by Blake's house style. It works in 4 modes: Review (a findings report), Redline (tracked changes in the .docx), Comment (Word comments), and Draft (a new contract). Every mode runs the same analysis and cites the MSCD paragraph or blog post behind every change.
2 principles drive everything:
- Ambiguity is never acceptable; vagueness stays only on purpose. Ambiguity is text that can express 2 or more inconsistent meanings (MSCD 7.5). It causes disputes, so the skill removes every instance it finds. MSCD concedes that a drafter can't realistically eliminate every ambiguity of the part versus the whole (7.5); where you can't remove one, flag it. Vagueness (a standard that depends on circumstances, such as reasonable) is sometimes the right tool, so the skill flags it and keeps it only for a stated reason.
- Annotate first; never change meaning silently. Adams doubts that technology can turn a traditional contract into an MSCD-compliant draft unaided, and suggests "explanatory annotations," leaving fixes to the user ("Could You Use Artificial Intelligence to Check Whether a Contract Complies with MSCD?", mid-2023). So every change comes with its reason. A redline changes only wording whose meaning is certain; anything that needs a choice of meaning or a business term becomes a comment for Blake's decision.
Blake wants to understand the mechanics of every fix, so every internal finding explains the grammar or reasoning behind it, not just the replacement wording. A finding counts only if its fix is right: the fix solves the problem, follows MSCD and the house rules, keeps the deal's meaning, and creates no new problem.
Precedence: which source wins
When sources conflict, follow the 1st one that addresses the point, and say in the finding which one you followed.
- Blake's instruction for the matter.
- Law that requires specific wording: when Blake identifies it, or when it is a common case listed under Hard cases (merchantability in a UCC disclaimer; a negotiable note's promises to pay to the order of; work made for hire). Wording a statute or rule requires isn't a drafting choice, so keep it even where a house rule would change it, and flag it. Don't research or decide law.
- Blake's house style (
references/house-style.md). Blake's rule: his way always prevails over MSCD. - Adopted riders (
references/riders.md): blog posts in which Adams changes MSCD5. - MSCD5 (
data/rules.jsonland the reference files). - Blog elaborations that extend MSCD5 without changing it.
- Proposals Adams only floats (language of inaction, language of state of mind, human for individual, afterwards, descriptive headings instead of Miscellaneous): note them; don't apply them.
- Standard English per The Chicago Manual of Style, where everything above is silent.
What's in the skill
Run the scripts by their full path inside this skill's folder (for example, python3 <skill folder>/scripts/mscd_lint.py), because the working folder usually isn't the skill's. They run on Python 3.11 to 3.13 (tested). The lint uses python-docx when it is installed and falls back to a plain reader without it.
The MSCD Project's knowledge files hold the same 1,338 rule records and the same blog sweep as data/rules.jsonl. Use this skill's scripts and references instead of searching those files; open a Project file only for a passage the rule database doesn't cover.
| File | Read it when |
|---|---|
references/house-style.md |
Always, first. Blake's rules and how to apply them in hard cases |
references/verbs.md |
Pass 3, and any question about shall, will, may, must, hereby, states, or conditions |
references/ambiguity-catalog.md |
Pass 4: every cause of ambiguity, with its signal, test, and fix |
references/vagueness.md |
Pass 5 |
references/words-to-avoid.md |
Pass 6; the usage table (1 verdict per MSCD chapter 13 entry) |
references/attachments.md |
Every contract: the schedule-versus-exhibit procedure |
references/defined-terms.md |
Pass 2 |
data/terms-of-art.json |
Passes 2 and 6, and drafting: each contract-law term of art, its legal meaning, how to spot another sense, and the replacement (house rule 13) |
references/time-and-numbers.md, standard-english.md, structure.md, active-voice.md, efforts-material.md |
time-and-numbers.md pass 7; standard-english.md pass 9; structure.md pass 1 and Draft step 2; active-voice.md pass 3; efforts-material.md pass 5 |
references/look-alikes.md |
Before you flag text that only resembles a problem: about 300 correct sentences that look wrong, by type, each with why it is correct (search it with grep). The lookalikes lists inside data/phrase-variants.json are not that: each shows only that 1 check must not fire on it |
references/riders.md |
Pass 4 (its 3 ambiguity causes), pass 6 (ampersands; once and when), and before you cite a paragraph its table lists |
references/comment-templates.md |
Before writing any comment or report |
references/docx-mechanics.md |
Redline steps 3, 6, and 7, and Comment mode: the tracked-change markup, the validate and accept commands, and the comment markers and line breaks |
references/fix-check.md |
Stage 2b: the 6 tests for every fix, and the brief for the independent check under 'Then get the fixes checked independently' |
references/fix-patterns.md |
Stage 2, before you write the Fix field of any finding: the 8 ways fixes failed in blind rounds 7 and 8 (122 failures), most frequent first, each with the original, the failed fix, the test it failed, and a fix that passes |
references/practice.md |
When MSCD's own review advice matters (the other side's draft; caselaw) |
references/rule-database.md |
When you query a record or refresh the knowledge |
scripts/mscd_lint.py |
Pass 0, on every document, and on every fix you write (Stage 2b, test 1). --inventory adds the defined-term inventory |
scripts/coverage.py |
Before delivering a review, redline, or comment set: lists every lint direct finding your work doesn't account for (Stage 2b) |
scripts/rules_query.py |
To pull a rule's full record (test, fix, exceptions, verified book examples) by id, word, or paragraph |
The reference files list every rule as 1 entry with its id; pull the full record with rules_query.py --id when you need the test, exceptions, or the book's own example. Reading the rule record is how you avoid citing a rule wrongly. The reference files are large (words-to-avoid.md and verbs.md are over 100 KB): read each file's header, then search it (grep, or rules_query.py --word) for the words in front of you rather than reading it whole. Book examples, fixes, and rule statements are in MSCD style; restate them in house style before you use them (digits, active voice, Schedule A, no article before a party name).
Stage 1: Intake
Ask only what you can't infer; if Blake isn't there to answer, use the default and state it at the top of the output, but only a default that changes the answer.
| Question | Default |
|---|---|
| Whose draft is it: Blake's, or the other side's? | Either way, full MSCD conformance (Blake's rule: "We need to start educating people"), with 1 exception: on the other side's draft, keep their represents and warrants and suggest the remedies-neutral sentence in a comment (3.459-3.463); on Blake's draft, use states for every statement of fact, a statement of future fact included, and conform every represents and warrants to it, a stray one included (house rule 10). On the other side's draft, separate changes that affect meaning from style changes, so the other side sees what matters first. If nobody knows whose draft it is, treat it as the other side's and pass --whose other-side to the lint (it is the more cautious choice: it doesn't rewrite a verb the drafter may have chosen on purpose), and say so |
| Which mode, and what output? | Review → a report in a Claude doc; if no Docs tool is available, or if Blake names a file, a .md or .docx file in the working folder; Redline or Comment → the .docx; Draft → .docx. A pasted clause or a short question → answer in the reply, with no file, and keep the answer in proportion to the question: the rewritten clause first, then 1 short entry per change (what changed and the grammar or rule behind it, with its source), then any decision Blake must make. Leave out severity labels and the rest of the finding fields unless he asks for a full review. For a short question, run the lint on the clause (no --inventory), read the rule record of each change, lint your fixed wording, and run the 6 tests in fix-check.md yourself; skip findings.json, coverage.py, and the subagent check |
| Governing law, and kind of deal | Ask; if unknown, U.S. law, general commercial, and say so. English or Commonwealth law changes the advice on represents and warrants, efforts, and calendar month (3.416-3.450; 8.50-8.63; 10.102); the house rules still apply |
| Who reads the comments? | Blake (internal form). Use the external form when Blake says the comments go to the other side (comment-templates.md) |
| Tracked-change author | Blake's AI Agent, with comment initials BAR-AI (Blake Alan Reagan's AI agent; never BAA, which in healthcare law means a business associate agreement) |
Then read the whole document before changing anything: the meaning of 1 provision often depends on another.
Stage 2: Analysis
Run these passes in order; later passes use what earlier ones learn. A sentence can hold several problems: after you record a finding, run the remaining passes on the same sentence and on your fix's wording (5% of the overdue installment keeps the money-formula problem; located in the Territory keeps the reach problem; a new cap that is Blake's business call still gets the each-or-aggregate check). When 2 findings change the same words, write 1 combined wording that fixes both and put it in the finding with the higher severity (if equal, the earlier pass). The other finding keeps its own Why and Source; its Fix reads wording: see finding N. Both stay in findings.json.
Before you flag anything under an MSCD rule, read its record (rules_query.py --id) and confirm the text matches the rule's own pattern and example: may ... only if is MSCD's approved form (3.363-3.364), though 3.222 warns about may ... only; MSCD 16.34 targets a party's acknowledgment, not every sentence near a disclaimer. If both readings give the same result, there is no ambiguity, so don't flag it.
- Lint.
- Run it. Run
python3 <skill folder>/scripts/mscd_lint.py <file> --inventory --whose <blake|other-side> --json lint.json. It reads .docx, .txt, and .md: save pasted text to a .txt file first. For a PDF with a text layer, extract its text withpdftotext -layoutto a .txt; extraction can collapse 2 spaces into 1 and loses fonts and alignment, so don't report spacing or typography from extracted text: check it on the rendered page, or say it wasn't checked. For a single clause or a fragment, leave out--inventory(a fragment has no definitions), review only what Blake asked about, and say that the rest of the contract wasn't reviewed. - What the report lists. Read the report's notes at the top: they say what the lint couldn't read (an encoding, Word's numbering, text it decoded badly). The report lists candidates in 2 groups: direct findings (house rules, MSCD's signature phrases such as and/or, best efforts, within 30 days of, the outline, and the defined-term inventory), which are usually right and carry their fix, and rule triggers, which point you at sentences to check in passes 3 to 9 and are often not problems in a clean draft (the attachments note, 1 per document, sits with them: it asks you to run the schedule-versus-exhibit procedure; it names no problem). Broad triggers (every shall, every may) appear once as counts. The lint reads a .docx with tracked changes as if the reader had accepted them; the report says so and lists each change with its author and text (deleted text isn't in the paragraphs, so review it from that list).
- Judge each candidate. Confirm or reject each candidate in context; the script can't read meaning. For a candidate that may be correct text that only looks wrong, search
references/look-alikes.md. On a traditional template expect hundreds of candidates, most of them real. - Read the text from lint.json. Read the contract's text from the lint's paragraphs (
paragraphsin lint.json), not from a python-docx dump: the lint reads tracked insertions as accepted, and a dump drops them. The paragraph numbers count every paragraph in order: body, table cells, text boxes, then headers, footers, and notes. The lint skips a harness note at the top of a test file (Draft of ...; Blake's client: ...), so its paragraph reads as blank.coverage.pycounts each place a direct finding fires (a finding repeated in 12 paragraphs is 12 places); it doesn't count rule triggers.
- Run it. Run
- Structure. Front of the contract, body, back, attachments (a document with its own signature blocks is an Exhibit, house rule 6); enumeration in the house scheme, which governs the outline only (house rule 3); headings; cross-references (house rule 4: avoid them, and refer by heading: under the section titled "Payment", never as stated in the section titled "Payment").
structure.md,attachments.md. An operative provision in a schedule moves into the body (attachments.md, step 6 says where). - Defined terms. From the inventory: terms defined twice, unused, undefined (role labels such as the Receiving Party included), used in 2 forms, circular, stuffed with obligations, or defined with shall mean; this Agreement defined as a term (2.123); party names take no article (house rule 11). Check every defined term against the terms of art of contract law (
data/terms-of-art.json; house rule 13): a term of art keeps its legal meaning, so an Assignment that means a work order, a software Release, or an Uptime Guarantee needs a new name (severity 1 when the contract also uses the word in its legal sense).defined-terms.md. - Categories, sentence by sentence. Assign every sentence in the body a category of contract language and check its verb (
verbs.md): the has a duty test on every shall; must only for a duty on someone other than the subject; may only for discretion; never shall with a negative subject, and for a nonparty subject restructure onto a party, never No Authorized User may (house rule 8); active voice in every clause. Pick the tense of every policy you write or keep: in force on signing or at a fixed date, the present tense; tied to an event that may not happen or whose timing is uncertain, or in a matrix clause after if, when, or unless, will (MSCD 3.334; 3.361); that includes a notice's effectiveness (A notice will be effective when the recipient receives it, MSCD's own form; 13.209), an amendment's or waiver's (will not be effective unless, 3.369), and the agreement's own on signing (will become effective when all parties have signed it, 5.25), while a standing allocation keeps the present (No Member is liable for the Company's debts). Recitals take no category: will there states the future, not a duty, and isn't a finding (MSCD 2.130-2.132); a purpose recital's verb is wants, never intends to (2.146-2.147). A correct category stays even when another would serve the client better: is not required to (3.292) isn't a prohibition in disguise, and wanting a prohibition is a deal point for Blake. - Ambiguity. Check every sentence against every cause in
ambiguity-catalog.md, including the riders (right-node-raising pivot ambiguity; each or in the aggregate; the specific versus the general). For each ambiguity, list every candidate before you propose a fix: for a pronoun, every singular noun in its sentence and the sentence before; for a modifier, each noun it can reach; for within N days of, before and after. N meanings listed means N wordings offered. A meaning drops out only when you name the provision that excludes it, never because it reads less naturally or the context favors the other. Then the fix must either give wording for each meaning and ask Blake which he intends, or name the provision that rules a meaning out. A fix that quietly adopts 1 meaning is wrong, even when that meaning is the likelier one ("each laptop and desktop that Provider leases" silently settles whether leased reaches desktops). A period that runs from a notice or demand must say whether it runs from giving it or from receiving it; a period that runs from a request doesn't get that choice (Blake's decision). - Vagueness. Flag each vague standard (reasonable, prompt, adequate, material, substantial, satisfactory) and classify it: keep on purpose, replace, or ask (
vagueness.md). Keeping it is Blake's call, not yours: offer the measure the contract already supplies (a period it states elsewhere, a manual's levels, the Documentation, the sections of a deliverable) or a bracketed number, and ask. Rule keep only when no measure exists (reasonable efforts, substantially all), and say why none does; a reason that a measure would hurt a party is a business judgment and isn't yours to make. - Words to avoid. Every hit in
words-to-avoid.md, judged in context. Never should, in any sense (house rule 12): give the replacement for its sense (shall, may, the present tense in a condition, a duty or fact for an expectation, a defined Knowledge term for should have known). Every term of art used as an ordinary word in another sense (work assignment, marketing collateral, new release): replace it with the plain word (house rule 13). Covenant for an obligation becomes obligation, grouped obligations included (Financial Covenants; MSCD 3.186-3.188), but covenant not to sue and restrictive covenant are terms of art and stay, and a reference that quotes a heading (the section titled "Financial Covenants") follows the heading: fix the heading. - Time, numbers, money.
time-and-numbers.md; house rules: digits for every number (fraction words such as half and a document's name such as Second Amendment keep their words, house rule 2), January 1, 2027. Blake's deadline rules (house-style.md section 7): a no later than [date] deadline that decides a right states a time of day and a time zone; every backward-counted period (no later than 30 days before) gets a finding, fixed as the 30th day before or a stated date; every from [date] through [date] gets a finding, fixed as starting on ... and ending on .... Check the arithmetic: installments against the total, percentages against amounts, each table row against the body, every date against its weekday and against the date of the agreement (a deadline that falls before signing is impossible, not a count question). A money formula takes an amount equal to and minus (14.22-14.24). An amount stated twice (a body fee and a schedule total; $84,000 ($7,000 per month); a rate beside its dollar figure, $6,650 a month ($28.50 per rentable square foot)) is a finding even when the copies agree (severity 3; Blake's decision): each option keeps 1 copy (MSCD 1.56), and when the copies disagree it is a conflict, and each option both reconciles and deletes 1 copy. - Consistency. 1 word for 1 meaning across the whole document, attachments included (1.57-1.60). Compare each provision with every other provision on the same subject, however far apart: a payment term in the body against a schedule, a definition against its use in an exhibit, an order-of-precedence clause against a specific provision.
- Standard English and typography.
standard-english.md; the serial comma (12.59); house rules: 2 spaces between sentences, 1 after a colon, 12-point Aptos, ragged right, clean visual lines, and a clause that must be conspicuous in bold 14-point type, never capitals, with an initial line for each party under it (house rule 9). The front: title centered in capitals (2.2), party names in capitals in the introductory clause (2.51), the lead-in (2.159), defined terms in bold where defined (16.20). A .txt file carries no font, alignment, or bold, and a .md file carries only bold (**...**): say once in the report which typography wasn't checked, and don't guess. Leave date and day alone unless 1 causes confusion (10.16). MSCD lets you omit the concluding clause (5.5), so a contract without one has no problem to report. A letter agreement has no introductory clause or lead-in: apply MSCD chapter 19 to its front and back instead (rules_query.py --para 19.3).
Before you write any fix, read references/fix-patterns.md. In blind tests, most failed fixes changed the deal, rewrote correct text, answered a different problem, or dropped a reading; the file shows each mistake with a fix that passes, and ends with 8 questions to ask of every fix along with the 6 tests in fix-check.md.
Record each finding in this form (it feeds every mode):
| Field | Content |
|---|---|
| Location | The section's heading (and number, if the document has one) and the quoted words |
| Kind and severity | 1 must fix (ambiguity, or a category or usage error that can change meaning); 2 fix (vagueness, dispute risk); 3 style. See the severity policy below |
| Meanings | For an ambiguity, each possible meaning in plain words |
| Fix | The replacement wording, in house style |
| Why | The mechanism (grammar, category, or risk) in 1 or 2 sentences |
| Source | Rule id and MSCD paragraph, rider post, or house rule (noting where MSCD differs) |
| Decision needed | Yes, with options, when the fix needs a business term or a choice of meaning |
Severity policy. Apply the policy in house-style.md under 'Severity of a house-rule finding' (the lint applies the same policy: for a lint finding use the lint's severity unless the context changes it, and say why). rules_query.py --id, which gives a rule record's severity, also accepts a paragraph number, such as --id 3.358.
- Context: if the context removes the problem (the 2nd reading can't arise here), the candidate isn't a finding; reject it with the reason. Lower a severity only when the lint's or the rule's severity assumes a fact that is false here (2 possible actors, when only 1 party could act; 2 copies that disagree, when they agree), and name that fact in the finding. A finding with 2 surviving readings stays 1; a house-rule breach keeps its rule's severity however minor it looks.
- A defined term used in lowercase is a 2nd form (severity 1) only when the drafter intends the defined meaning. A common word in its ordinary sense (business hours beside a defined Business) isn't a finding (MSCD 6.11), and neither is a party's common-noun term used in its ordinary sense (a company that acquires Company beside the defined Company; rider R-rider-lowercase-party-noun).
Stage 2b: Check the fixes
Account for every lint finding before you deliver. Keep your findings in findings.json as you work (a list of {"quote": exact contract words, "type", "severity", "fix", "source"}; a finding that repeats with 1 fix everywhere can add "check": "<lint check>", "all": true instead of 1 object per place), and put each lint direct finding whose text you checked and found correct in rejected.json ({"para", "match", "check", "reason"}). The fix field holds the proposed wording first, then the explanation and any question to Blake. The checker rules on all of it, so the explanation follows the house writing rules too. rejected.json holds lint direct findings only. A rule trigger you reject needs no entry: coverage.py ignores triggers and says so in its summary line. Mention a rejected trigger only in the report's list of checks that found nothing, with the reason when the call was close. Then run python3 <skill folder>/scripts/coverage.py lint.json findings.json --rejected rejected.json. It lists every direct finding that no finding or rejection accounts for. Long reviews drop real lint findings while the reader works on harder problems, so resolve each one listed and run it again until it reports 0 missing. When 1 decision covers every place a check fires (a serial comma added in every list), 1 entry with "check": "<lint check>", "all": true and its fix or reason accounts for all of them; list the places in the report. For a 1-clause question, skip this step.
Check every fix before you deliver it. Run every proposed wording (each fix, option, redline insertion, and suggested sentence) through the 6 tests in references/fix-check.md, 'The 6 tests': Rules, Whole problem, The deal, No new problem, Options, In place. Lint each wording first (a .txt, 1 paragraph per wording, no --inventory).
Then get the fixes checked independently. For a review, redline, or comment set (not a 1-clause question), if you can start a subagent, give it references/fix-check.md and the paths it names (the contract, findings.json, references/house-style.md, scripts/rules_query.py) and this skill's folder path, so it can open look-alikes.md, terms-of-art.json, and the lint. It rules each finding pass, fail (with the test), or keep (the finding proposes changing text that is correct). Fix every fail; drop every keep you agree with (move it to rejected.json with the reason; for a finding the lint never fired on, set "check" to "pass-N", which coverage.py ignores and the report keeps); then, on each changed fix, lint the new wording again (a .txt, 1 paragraph per wording, no --inventory) before the other 5 tests, because a reworded fix that no lint has read is an unchecked fix; then run coverage.py again until it reports 0 missing. A flag whose fix is already keep (a legal question for Blake, wording a statute requires) stays in the findings: it passes when the flag is accurate. Where you disagree with a ruling, say why in the finding. Without subagents, do the same check yourself, cold, after you draft the findings: read fix-check.md and rule on each finding in turn.
Stage 3: Output by mode
Review
Write the report in the form in comment-templates.md: a short summary, then findings sorted by severity and location, with wording cleanup, ambiguity fixes, and substantive changes kept apart. Group a repeated finding into 1 row with all its locations.
Redline
Use the docx skill's workflow for editing an existing document (read its SKILL.md: "Editing existing documents", "Tracked changes" and "Comments"; find its folder from the skill listing; on claude.ai it is usually /mnt/skills/public/docx).
- Work on a copy; never modify Blake's original. Unzip it, strip symlinks, and run the docx skill's
merge_runs.py, as that workflow says. - Make only changes whose meaning is certain. Where a fix needs a choice of meaning or a business term, leave the text, insert a bracketed blank if needed, and put the options in a comment.
- Track every change as Blake's AI Agent and change only the words that differ; the markup rules are in
references/docx-mechanics.md. Put each clause that must be conspicuous in the house form (house rule 9: bold, 14-point, never capitals, an initial line for each party under it) as a tracked change. - Leave the other side's tracked changes alone: don't edit inside their
<w:ins>or<w:del>. Put your change beside theirs, and say so in a comment, or comment instead of editing. - Carry each change through: a renamed defined term changes at every use; a moved provision updates every heading reference to it. Keep an old-to-new numbering map when converting to the I., A., 1., (a), (i) scheme, and deliver it with the redline. Keep the document's typed or native numbering: convert to native Word numbering only in a document Blake drafts, and flag typed numbering once, at severity 3 (house rule 3). When typed numbers must take the house markers, don't track every renumbered paragraph; say so in 1 comment, and deliver the map. A font set in a style doesn't show as a tracked change: flag it in 1 comment.
- Zip the folder and validate it as a redline, then make the clean copy from it and validate that too; the commands and the fallback when validation fails are in
references/docx-mechanics.md. The clean copy accepts every tracked change, the other side's too; comments already in the file stay in it. - Add your comments to
tracked.docxto make the redline (see Comment, below), and validate it again as a redline (references/docx-mechanics.md). - Read both files back: run the lint on the clean copy and confirm that each edited sentence reads as you intended, with no new direct finding in an edited paragraph. Render both to images and look at them: the validator checks text, not numbering or formatting.
- Deliver the redline, the clean copy, and the findings report. If the file arrived with the other side's tracked changes, say that the clean copy accepts theirs and yours alike, and list their changes in the report with a recommendation on each.
Comment
Anchor 1 comment to the exact words of each finding with the docx skill's scripts/comment.py, as Blake's AI Agent with initials BAR-AI (never BAA); the command's flags, the markers, and line breaks inside a comment are in references/docx-mechanics.md. Start each comment as comment-templates.md shows for the reader: use the internal form for Blake and the external form for the other side, and never mix the 2 forms in 1 file; when a file with internal comments is going to the other side, deliver a 2nd copy with external comments instead. Comments can accompany a redline: put the reason for each tracked change in its comment. Validate the file afterward.
Draft
- Take in the term sheet, notes, or old form. List every deal point you can't find as a question for Blake; never invent a deal term, number, date, or party detail.
- Outline to
structure.md: title; introductory clause; recitals only if there's a back story; the lead-in The parties agree as follows: (with recitals, The parties therefore agree as follows:, 2.159); the body in the house enumeration with a bold heading for every section; definitions where chapter 6 places them; concluding clause; signature blocks; Schedules, then Exhibits. - Write each provision by choosing its category first, then its verb (
verbs.md), in the active voice, with digits. Never write should (house rule 12), and never use a term of art for anything but its legal meaning, as a defined term or otherwise (house rule 13;data/terms-of-art.json). - Run all 10 passes (0 to 9) on your own draft and fix every finding; list any severity 2 or 3 candidate you reject, with the reason, under the open questions.
- Get an independent review. If you can start a subagent, give it the draft,
references/house-style.md, and this file's Stage 2, and ask it to check every sentence and return findings; it hasn't seen your drafting, so it won't share your blind spots. Without subagents, reread the whole draft cold, pass by pass. Fix what the review finds, then rerun the lint. - Build the .docx with the docx skill (12-point Aptos, native multilevel numbering, ragged right; each clause that must be conspicuous in bold 14-point type with an initial line for each party under it, house rule 9), render it, look at it, and deliver it with the open questions.
Hard cases
| Situation | What to do |
|---|---|
| Must states what a nonparty or a thing must do or be (The arbitrator must issue the award ...; The Escrow Agent must release ... when the escrow agent doesn't sign) | Correct must. Correct when no party can do the act itself (MSCD 3.154; 3.166): keep it. If the party relying on the nonparty has no remedy when it doesn't act, say so with fix keep, and offer, for Blake to choose, what happens then (MSCD 3.166).A party could act. If a party could do the act itself (Each Acme employee must sign a confidentiality agreement), the fix is the restructure: Acme shall enter into a confidentiality agreement with each of its employees (MSCD 3.165).The banned verbs. Never shall cause, shall ensure, shall require, shall procure, shall see to it, shall have [the nonparty] [act], shall not permit, shall not allow, or shall prevent for a nonparty the party doesn't control (MSCD 3.162-3.163; 3.176-3.177); control means an instrumentality such as a subsidiary, and a counterparty the party picks (a contractor, an insurer, a subcontractor) is still a nonparty. A body the party acts through is not a nonparty: The Board shall review the Base Salary and Company shall cause the Board to approve are both correct for Company's own board (MSCD 3.160-3.161; Blake's decision). Leave them, or offer Company, acting through the Board, shall approve (the acting through form of MSCD 2.80) as a style option.Shall obtain. Shall obtain or shall secure [a nonparty's consent, approval, or document] is different: MSCD 8.5 treats it as a valid unqualified duty of result whose risk sits on the obligated party. Don't call it a category error; flag it (severity 3) when Blake's client bears it, and offer the efforts standard (shall use reasonable efforts to obtain) or a condition as the alternative for Blake to choose.Lead with the minimal fix (must on the nonparty, 3.166, or a limited-control duty such as shall request or shall include the deadline in the engagement letter, 3.165), and offer a risk-allocation term only as an added bracketed option. A nonparty's prohibition (No Authorized User shall ...) is the exception: it gets the restructure onto the party, never No Authorized User may (house rule 8; Blake's decision): Customer shall use reasonable efforts to prevent any Authorized User from sharing credentials[, and Customer is liable for any loss that results from an Authorized User's sharing them] (MSCD 3.180; 8.5); shall cause only for the party's instrumentality, such as its subsidiary or its own board (3.160-3.161), with the liability bracketed for Blake; never weaken it silently to shall instruct or a narrower duty.Never delete the provision: the requirement survives, on the party (the Receiving Party shall ensure that each Permitted Recipient ... is also wrong; write shall not disclose ... to any Permitted Recipient unless that recipient has agreed in writing to ...) |
| Text that looks wrong but is correct | Leave it alone; a flag on correct text is a false alarm, and a fix to it changes the deal. Before you flag text that matches a pattern, search references/look-alikes.md, and read its 'Recurring cases from blind tests'. When a sentence has a real problem and a correct feature, change only the problem's words |
| Fixing an ambiguity requires choosing a meaning | State each meaning; ask which meaning Blake intends; in a redline, comment with 1 wording per meaning |
| 2 provisions say the same thing in different words, and 1 of them is correct (section 6.1 indemnify from claims, section 6.2 indemnify against claims arising out of) | Fix the one that departs from MSCD and conform it to the correct one; leave the correct one alone. When the 2 provisions state the same amount (a fee in the body and a schedule total), each option also states it once (MSCD 1.56): delete the body figure or the schedule total |
| Words and digits, or 2 provisions, disagree on an amount, date, or period | Severity 1. Don't pick 1: state both, say which provisions conflict (with their headings), and ask Blake which governs |
| Replacing shall in language of policy (The Term shall automatically renew ... unless; This Addendum shall terminate when the Subscription Agreement terminates) | Run MSCD 3.334's test (pass 3; verbs.md, procedure step 6). The present tense for every policy is wrong 50% of the time |
| A house rule and an MSCD verb structure collide | Apply the house rule if a clean active form keeps the meaning; otherwise flag the sentence and ask Blake. Blake has settled 3 cases: is not required to stays (3.292); is dated stays (2.21); recast a reduced passive only when a clean active form exists (house-style.md section 1) |
| Recasting a passive would narrow or change who can act | Keep the meaning, flag it, and ask |
| The .docx already has tracked changes or comments | Ask whether to accept them first or redline on top. If Blake isn't there, redline on top under your own author name, leave their changes and comments in the redline, and say so; the clean copy accepts every change, and their comments stay in it. The lint lists the comments already in the file: read them, and tell Blake which ones to remove before the file goes to the other side (a comment can reveal a side's position) |
| Responding to the other side's markup of an agreed draft | Scope: review their changes and anything their changes affect. Default: full MSCD conformance on their new text; list separately any fix to text both sides had already agreed, so Blake can decide whether to reopen it. For each of their changes, recommend accept, reject, or counter on drafting grounds only (the wording's category, clarity, and house-rule conformance); whether to take a business term they inserted (a higher bonus, a new cap) is Blake's call, so put it as a question, not a recommendation, and still run the full drafting check on the term's wording (a new cap is each or in the aggregate, its lookback date, its verb) |
| A mostly well-drafted contract | Report only real problems. Don't pad the report; say briefly that the rest conforms, and list the checks that found nothing |
| Blake asks for a playbook or checklist rather than a review | Build it from the rule records and house rules (cite each), not from memory, and mark which items the lint checks automatically |
| Standard terms and conditions, or another form with no introductory clause, lead-in, or signatures | Skip the front-of-contract checks that can't apply; say so once |
| An amendment, or a reference to another agreement's provisions | Provisional default until Blake decides: keep the other agreement's own numbering, and add its heading when it has one (Section 4 (Payment) of the Original Agreement); house rule 4 governs references inside the amendment itself |
| A joinder (MSCD 13.480-13.484: in effect an amendment; rule R-13.480-joinder, severity 3) | Rename it amendment only if the amendment clause doesn't require every party's signature. If it does, the rename makes a joinder the new party signs alone conflict with that clause, so keep joinder, flag it (severity 3), and offer Blake the rename plus a carve-out (other than an amendment that adds a party) |
| A scanned or image-only PDF | Warn that text recognition may misread words; offer a report or a rebuilt .docx, not a redline |
| A PDF with a text layer, or pasted text, when Blake wants a redline | Rebuild it as a .docx first, say that the redline compares against the rebuilt copy, and keep the original's numbering in the map |
| A statute or court rule requires specific wording | Keep it; flag it; never remove the required words or make a required-conspicuous clause inconspicuous (16.24-16.31). Set a conspicuous clause in the house form (house rule 9) unless Blake identifies a statute that requires capitals or another form. Common cases: merchantability in a UCC disclaimer (MSCD 16.23 cites UCC 2-316(2)); a ne |
…(truncated)