Manuscript Review Triage

4. Classify each comment with evidence.

• VALID - ACTION NEEDED: real defect or omission that needs revision.
• ALREADY ADDRESSED: only when the manuscript already resolves the issue and you can point to the exact section.
• BEYOND SCOPE: valid point deferred for explicit reasons.
• INVALID: reviewer misunderstanding or claim contradicted by the manuscript or code.
• Use Validity Assessment to separate the status from the strength of the critique. PARTIALLY VALID is appropriate when the manuscript gestures at the issue but does not resolve it.

5. Update the tracker in the parseable format.

• Use the exact section pattern in references/tracker-format.md.
• Keep source_type semantically correct.
  • Use synthetic for AI-generated, prompted, or manually generated internal reviews.
  • Use actual for real external or journal reviews.
• Preserve unified review numbering already in the tracker unless the user explicitly asks to reset it.

6. Turn triage into execution.

• When the user asks for next steps, create doc/reviews/<manuscript>/REVISION_PLAN.md.
• Order work by credibility risk, not by ease.
• Put design defects, model contradictions, and data provenance ahead of stylistic cleanup.
• When drafting manuscript text from the plan, keep revision logic out of the manuscript itself.
• Use trackers, memos, and response letters for process narration; use article-facing prose in the manuscript.

7. Refresh derived review artifacts.

• Run python src/pipeline.py review_response --manuscript <key> after meaningful tracker updates.
• Run python src/pipeline.py review_verify --manuscript <key> to update checklist progress.

Repo Conventions

• Do not claim a review is actual if it was AI-generated.
• Do not mark a point ALREADY ADDRESSED without a file or section citation.
• Prefer Quarto source files for edits; treat DOCX files as source artifacts unless the user explicitly wants Word-first editing.
• For Kaifa work, keep the manuscript archived and clearly separate from the active manuscript_quarto/ manuscript.
• Preserve parseability for review_response and review_verify.
• Do not let tracker language leak into the manuscript body. A completed revision should read like a submission-ready paper, not like a changelog.

References

• Read references/tracker-format.md before editing a tracker by hand.