Nature-Style Scientific Writing, Router

Routing protocol

For 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.

1. Load the manifest and the core layer

Read manifest.yaml. It declares the axes (task, paper_type, section, language, journal), the allowed values, and the file paths each value maps to.

Also read every file listed under always_load. These hold the default stance, writing workflow, and output format that apply to every drafting job.

2. Detect the axis values for this request

For each axis in the manifest, decide the value using the manifest's detect: hint and the user's input:

• task, manuscript / submission-package. Use submission-package for first-submission materials, never for revision correspondence.
• paper_type, research / methods / hypothesis / algorithmic / review. Default: research.
• 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.
• language, en or zh-to-en. Detect from the user's notes themselves.
• journal, nature / nature-family / nat-comms / nat-mach-intell / generic. Default: generic. Use nature only for the flagship journal Nature, nat-comms for Nature Communications, nat-mach-intell for Nature Machine Intelligence (NMI), and nature-family for other Nature Portfolio titles or an unspecified Nature-family request.

State the detected axis values in one short line to the user before drafting, so they can correct you cheaply. This is a progress update, not an approval gate; continue unless a necessary decision remains unresolved.

3. Load the matching fragments