writerlisted

# Writer `writer` is the directory and routing contract for academic and technical writing. It is intentionally compositional: > exactly one primary type + zero or more lenses + zero or more source objects > + zero or more domains + one format for artifacts (zero for chat-only prose) > + optional format integrations The module selected for a task is the canonical home of that rule. Do not copy the same rule into a type, format integration, or reviewer. For maintenance or feedback-driven updates, read `MAINTENANCE.md` before choosing a file to edit. ## Route a request 1. Identify the task: draft, revise, audit, explain, or translate. Compilation and build diagnosis belong to the separate `latex-compile` skill. Also identify whether this is a brief chat answer/local lookup or a substantial persistent artifact. The full source-grounded workflow applies conditionally to substantial explanations; reports and textbooks follow their type contracts. 2. Select exactly one primary type under `references/types/`: `report`, `explanation`, or `textbook`. 3. If the primary type has a bounded variant or component, load it from `references/type-addons/`: `report-experiment` or `textbook-exercises`. An add-on does not become a second primary type. 4. Add zero or more cross-type lenses under `references/lenses/`: `derivation-analysis` for derivation-heavy exposition and `mechanism-analysis` for input/output/state/control-flow depth. Activate a lens when t