nature-polishing

1# Nature-Style Academic Polishing — Router
2 
3## Routing protocol
4 
5For a new polishing 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 (`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, failure-mode diagnosis, ethics, and output format that apply to every polish 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- `paper_type` — research / methods / hypothesis / algorithmic / review. Default: research.
18- `section` — abstract / intro / results / discussion / conclusion / title / methods. May be multiple. Ask the user if it is ambiguous and matters for the polish.
19- `language` — en or zh-to-en. Detect from the draft itself.
20- `journal` — nature / nat-comms / nat-mach-intell / generic. Default:
21  generic. Use `nature` only for flagship Nature, `nat-comms` for Nature
22  Communications and `nat-mach-intell` for Nature Machine Intelligence (NMI).
23  Do not route another Nature Portfolio title through flagship Nature rules.
24…