Referee Response
Answer the objection that was actually raised, using scientific conclusions already established from controlling evidence.
Establish the response contract
- Read the exact referee comment and identify its direct objection, requested evidence or change, and any separate journal-positioning judgment.
- Inspect the current response draft and manuscript locations that the answer depends on. Do not treat a planned revision or stale draft as current source state.
- If support for a substantive response statement remains disputed, compose
$scientific-claim-auditbefore drafting. This skill consumes scientific judgments; it does not establish them by rhetoric. - For a physics-journal response, read physics-journal response practice and apply any more specific editor or journal instructions from the current decision.
Build the answer
- Select the response move that matches the evidence: acknowledge, correct, clarify, provide validation, state a bounded contribution, or leave an unresolved author choice visible.
- Lead with the direct answer. Attach each supporting block to the exact objection and the evidence needed to resolve it.
- Distinguish validation evidence from contribution claims and scientific claims from journal-positioning arguments.
- Map every promised revision to an exact manuscript target. Use past-tense revision language only after the same bounded statement appears in the current source.
Preserve scope and delivery ownership
- The scoped objection and established evidence determine the response and revision map. The map routes new calculations, manuscript edits, submission actions, and external correspondence to their authorized workflows.
- When revisions are authorized, synchronize the response and every affected manuscript claim surface. Compilation verifies the artifact; controlling scientific evidence supports the statement.
- Compose
$structure-documentationfor the response's reading path and professional prose. Route LaTeX, comments, compilation, rendering, and tracked-change mechanics through the repository's build instructions and current artifact tools. - Stop when the scoped objection has a direct evidence-backed answer, each promised revision matches current source, and any unresolved choice is explicit.