nature-writing

1# Nature-Style Scientific Writing — Router
2 
3## Routing protocol
4 
5For a new drafting task, follow the routing below. For follow-up edits, reuse established task choices and already loaded guidance; read additional fragments only when the requested scope changes.
6 
7### 1. Load the manifest and the core layer
8 
9Read [manifest.yaml](manifest.yaml). It declares the axes (`task`, `paper_type`, `section`, `language`, `journal`), the allowed values, and the file paths each value maps to.
10 
11Also read every file listed under `always_load`. These hold the default stance, writing workflow, and output format that apply to every drafting job.
12 
13### 2. Detect the axis values for this request
14 
15For each axis in the manifest, decide the value using the manifest's `detect:` hint and the user's input:
16 
17- `task` — manuscript / submission-package. Use `submission-package` for first-submission materials, never for revision correspondence.
18- `paper_type` — research / methods / hypothesis / algorithmic / review. Default: research.
19- `section` — abstract / intro / related-work / method / experiments / discussion / conclusion / title. May be multiple. Ask the user if it is ambiguous and matters for the draft.
20- `language` — en or zh-to-en. Detect from the user's notes themselves.
21- `journal` — nature / nature-family / nat-comms / nat-mach-intell / generic.
22  Default: generic. Use `nature` only for the flagship journal Nature,
23  `nat-comms` for Nature Communications, `nat-mach-intell` for Nature Machine
24…