Nature Reviewer Response, Router

Routing protocol

For a new task, load the core and matching resources below. Reuse already loaded guidance on follow-ups; load more only when the task needs it.

1. Load the manifest and the core layer

Read manifest.yaml. Then read every file listed under always_load:

• static/core/stance.md, the editor-facing purpose, the default stance, the red lines, and the source hierarchy that apply to every response job.
• static/core/workflow.md, accepted inputs, the revision correspondence workflow, and the output package format.

2. No content axis, identify mode and language inline

Unlike nature-writing or nature-figure, nature-response has no fragment axis. Its variation is identified at runtime, not by loading different content bodies:

• task mode, draft / audit / revise / triage-only / cover-letter / revision-package / latex-template / appeal-like.
• decision type, minor revision, major revision, revise-and-resubmit, transfer after review, or unclear.
• user language, if the user writes Chinese, also produce the 中文核对 block.

Decision type is required for a new package-level revision strategy or complete response package. First extract it from the editor letter or task context. If it remains unclear, ask whether this is a Major Revision or Minor Revision and pause only decision-dependent work. A local wording edit, audit of an existing reply, or comment-level triage may proceed with decision type marked unknown. Do not infer the decision from the number, tone, or difficulty of reviewer comments.

Use references/intake-and-routing.md to fix the task mode, minimum inputs, and readiness state before drafting. Route appeal-like cases separately; do not draft an appeal as the default path.