law-write

LAW Write

Write or edit LaTeX paper sections following Li's Academic Writing conventions. Every output must conform to the 26 writing rules defined in references/writing-rules.md.

For the owner' + chr(39) + 's inline % comments in tex sources, run the law-issues cycle (capture verbatim into the paper' + chr(39) + 's ISSUES.md, fix, describe, generalize, verify, commit); do not process them inline here.

Before writing

Read these files to understand the paper's context:

1. CLAUDE.md — the paper's narrative (challenges, design decisions, key results) at the bottom
2. AGENTS.md — paper macros (\sys), venue, page limit, section structure
3. main.tex preamble — document class, loaded packages, defined macros
4. Existing sections in sections/ — labels already used, cross-references to maintain

If CLAUDE.md has an unfilled "Paper Narrative" section, warn the user: "The paper narrative in CLAUDE.md is not filled in. I can write without it, but the content may not align with the paper's story. Fill it in for best results."

Writing rules (summary)

Core rules (see references/writing-rules.md for full details with examples):

1. Active voice, present tense, first person ("We find that..."); our own work takes we/our/ours as the sentence subject wherever grammatical (rule 25), and attack-enabling conditions get negative verbs, never "cheap" framing
2. Lead every paragraph with its main claim
3. Quantify every claim with specific numbers in normal weight
4. Name your discoveries with \emph{}
5. Never hedge — "This exposes a gap" not "This may suggest a gap"
6. Ground mechanisms in expert behavior: "Operators do X. Our system does Y."
7. One idea per sentence; no stacked subordinate clauses
8. No long dashes (--- or --); hyphens in compound words are fine; never begin a sentence with a number (rule 24), and no number or A/An opens any title, paragraph, or sentence (rule 26)
9. No \textbf{} mid-paragraph (bold numbers are OK); \noindent\textbf{Label.} for run-in heads
10. Code names in \texttt{}, system name as \sys
11. \resizebox for all tables; algorithm/algpseudocode only for algorithms
12. Leave \textcolor{red}{##?} for missing numbers, \textcolor{red}{TODO:} for unfinished work
13. Macro entities act through the authors: "We build a prototype that..." never "A prototype ...s" — only functions/processes/classes/contracts may be active subjects of their own mechanics
14. Never use "X, not Y" contrastive apposition (nor "not X but Y" / rhetorical "rather than") — state the positive claim; give the contrast its own sentence
15. Sentence-level coherence: every pair of adjacent sentences must connect — transition, elaboration, contrast, or consequence. Never change subject abruptly between neighboring sentences; rebuild the paragraph's spine so one idea develops in sequence
16. No one-sentence paragraphs, ever — expand with reasoning, merge with a neighbor, or cut entirely
17. Scope extraordinary claims: sweeping universals ("nothing reproduces", "no tool survives X") require inline evidence or an explicit scope ("in the systems we examined"); rule 5 forbids weak hedging verbs, never evidence-scoping of strong claims