Draft structured responses to peer review feedback
Reads review files and drafts structured, polite responses with evidence.
Read all review files from paper/review/reviews/:
review_YYYYMMDD_PERSPECTIVE.mdsynthesis_YYYYMMDD.md (if available)For each reviewer, extract every criticism and classify:
| Classification | Meaning | Action |
|---|---|---|
| must-fix | Valid criticism requiring paper changes | Make the change, cite evidence |
| should-fix | Valid improvement suggestion | Make the change or explain why not |
| optional |
| Nice-to-have, low priority |
| Address if easy, defer otherwise |
| disagree | Criticism based on misunderstanding | Politely correct with evidence |
For each criticism, draft a response following academic conventions:
**Reviewer [N] Comment [M]**: [Paraphrase the concern]
**Response**: [Our response]
**Action**: [What we changed, with specific section/line references]
Key principles:
Write to paper/response_to_reviewers.md:
# Response to Reviewers — QCML Geometric SDE Paper
Date: YYYY-MM-DD
## Summary of Changes
[Bullet list of all changes made in response to reviews]
## Reviewer 1 (Statistician)
[Responses to each comment]
## Reviewer 2 (Physicist)
[Responses to each comment]
## Reviewer 3 (Quant)
[Responses to each comment]
## Reviewer 4 (Hostile)
[Responses to each comment]
memory/results_registry.yaml for paper claimspaper/review/reviews/python -m experiments.registry canonical listpaper/qcml_geometric_sde.texmemory/results_registry.yaml