human-writinglisted

# Human Writing ## Outcome Contract - **Outcome:** natural, source-grounded writing shaped for the requested reader and surface. - **Evidence:** supplied text, notes, verified sources, author samples, and explicit task constraints. - **Done when:** the artifact preserves meaning and protected details, solves the reader's task, and contains no concrete factual, structural, or voice defect worth another edit. - **Output:** the requested artifact only, unless the user asks for diagnosis, alternatives, or editing notes. ## Core Stance - Treat writing patterns as diagnostic signals, not a checklist or banned-word table. - The author's supported voice wins over a generic house style. - Over-editing is failure. Prefer fewer, stronger changes; leave already effective prose alone. - Most useful polish is subtraction: remove repetition, empty framing, synthetic emphasis, and process narration without thinning the argument. - Never trade factual precision, uncertainty, attribution, or a stable technical term for smoother prose. ## Workflow 1. **Lock the source.** Identify authoritative facts, judgments, unknowns, protected text, visibility limits, and claim status across the whole artifact. Apply `references/fact-integrity.md` when the task contains multiple sources, technical claims, external facts, attribution, or disclosures. 2. **Set the target.** Infer the primary operation, reader, purpose, language, length, platform, and genre from the request and source. Ask only about mis