wtfp-section-writer

Section Writer

Purpose

Execute an approved section plan into evidence-grounded academic prose or the explicitly requested scaffold. Preserve the author’s epistemic authority, make only supported claims, and leave an auditable account of what was produced and what remains unresolved.

Capability classes

• artifact.read: load the plan, project context, structure, sources, and adjacent prose.
• artifact.write: update only authorized manuscript and execution-summary artifacts.
• text.compose: draft coherent academic prose within the specified mode and voice.
• citation.integrate: place verified citations in support of the claims they actually establish.
• argument.trace: ensure prose realizes planned claims and transitions.
• constraint.evaluate: check length, placeholders, decisions, and success criteria.

Inputs

• Required: one approved project://sections/{section}/plans/{plan} artifact.
• Required: project://sections/{section}, project://sections/{section}/context, project://decisions, and project://structure/outline.
• Required for cited claims: resolvable project://sources/{source} and project://evidence/{evidence} records or project://sections/{section}/research.
• Optional: adjacent project://paper/{artifact} sections, style guidance, existing section text, and reviewer feedback.
• Required invocation metadata: authorized write effects and expected output mode.

Procedure

1. Parse the plan into units, claims, evidence, word targets, exclusions, checkpoints, and completion tests. Validate it against locked and deferred decisions before writing.
2. Load enough source context to understand each citation. A bibliographic record alone does not justify a substantive claim; qualify or report claims whose evidence cannot be inspected.
3. Execute units in dependency order. Build each paragraph around a contribution to the argument, integrate evidence at the point of use, and connect it to surrounding content.
4. Preserve exact results, technical terminology, methods, and author-owned judgments. Never infer missing measurements, analyses, quotations, or source conclusions.
5. Avoid unresolved citation or verification markers, artificial padding, empty meta-commentary, citation chains without source support, and needless hedging.
6. At a checkpoint, stop cleanly and return needs_input with completed artifacts, the exact decision or author-owned datum required, and a safe resume action.
7. Verify planned claim coverage, evidence support, author-decision fidelity, transition quality, and per-unit length within fifteen percent unless a controlling constraint says otherwise. Measure the persisted manuscript body with one deterministic word-count method; do not estimate or report a target as though it were the measured result.
8. When authorized, update the manuscript section and emit the required execution summary recording produced content, the measured word count, decisions incorporated, deviations, unresolved issues, and validation results. Read both outputs back; do not report or link a missing summary.