Lang Rebuttal

---
name: lang-rebuttal
description: Use when responding to a Language (LSA) decision — a revise-and-resubmit response letter, or an author Rejoinder in the Perspectives target-article-and-commentaries format. Turns reviewer objections into a point-by-point revision plan that engages rival frameworks and firms up evidence. Structures the response; it does not fabricate new results.
---

# Rebuttal & Response (lang-rebuttal)

Two *Language* situations call for a structured reply: an **R&R response letter** answering referees on
a research article, and an author **Rejoinder** replying to invited Commentaries in the **Perspectives**
format. Both reward the same posture — engage every point fairly, concede what is right, and defend what
you keep with **data and predictions**, not tone. This skill turns the letter into a plan; it does not
invent results.

## When to trigger

- You received a **revise-and-resubmit** or **major/minor revisions** decision
- You are writing a **Rejoinder** to Commentaries on a Perspectives target article
- You need to convert a stack of referee comments into a tracked, point-by-point response
- Reviewers disagree with each other and you must reconcile the paths

## R&R response letter (structure)

1. **Open with the through-line.** One short paragraph: what changed, and how the revision strengthens
   the central claim. Thank the reviewers without flattery.
2. **Point-by-point, verbatim.** Quote each comment, then respond: *Change made* (with the new
   example/model/section and where it now lives) or *Respectful pushback* (with the reason and
   evidence). Number responses to match the letter.
3. **Show the new evidence.** If a referee doubted the statistics, present the refit **mixed-effects
   model** and effect sizes; if they doubted a gloss, show the corrected, sourced example.
4. **Engage the rival framework.** Where a referee raised a competing analysis, add the adjudicating
   prediction and test it — do not wave it away.
5. **Reconcile conflicting reviewers.** State the trade-off openly and justify the path you took; the
   editor arbitrates.

## Perspectives Rejoinder (structure)

- Group the Commentaries by the issue they raise, not one-by-one, so the reply reads as an argument.
- **Concede the strong points** — a Rejoinder that yields nothing reads as defensive; the format expects
  genuine dialogue.
- Defend the core thesis on the **evidence and its predictions**; restate scope conditions where a
  Commentary over-extended your claim.
- Close with what the exchange settled and what remains open for the field.

## Referee-response patterns and the venue-specific move

| Referee wrote… | The Language-specific response move |
|----------------|-------------------------------------|
| "Ignored the rival account." | add the adjudicating prediction; report the test result |
| "Statistics inadequate." | refit the justified mixed model; report estimates + intervals |
| "Data can't be checked." | source the glosses; post analysis data/code; cite the repo |
| "Overgeneralizes." | narrow the scope to the evidence; keep the mechanism |
| "Too framework-internal." | give the theory-neutral generalization; engage across traditions |

## Calibration (Language revision culture, hedged)

Reflects the journal's collaborative revision norm, not a guarantee; confirm process on the author pages.
A *Language* R&R usually asks you to **broaden framework engagement**, **firm up the evidence**, and
**scope the claim**, and reviewers reward a revision that visibly does the work over one that argues it
was already fine. Illustrative: a syntax R&R draws "engage the HPSG alternative and fix the acceptability
stats." The productive letter adds an HPSG-vs-Minimalist prediction the author's judgments adjudicate,
refits a mixed-effects model on the rating data with by-item random slopes, and narrows one universal
claim to a well-supported tendency — quoting each comment and pointing to the changed section.

## Anti-patterns

- Rebutting tone instead of substance; defensiveness in a Rejoinder the format expects to be a dialogue
- Waving away a rival framework a reviewer raised, rather than testing the deciding prediction
- Claiming a statistical fix without actually refitting the model
- Silent changes not mapped to the comment that prompted them
- Conceding so much the contribution dissolves, or so little the revision looks cosmetic

## Output format

```
【Decision】minor / major-R&R / Perspectives Rejoinder
【Through-line】one sentence on how the revision strengthens the claim
【Point-by-point】each comment → change made / respectful pushback + where it now lives
【New evidence】refit model / corrected glosses / added rival test
【Framework engagement】rival account adjudicated? [Y/N]
【Conflicts reconciled】path chosen + justification for the editor
【Next】resubmit via ScholarOne (lang-submission for the clean-file recheck)
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — modeling and glossing tooling to close reviewer gaps
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — Language review, Perspectives, and revision policy