Literature Positioning (lang-literature-positioning)

At Language the literature section proves the paper is in dialogue with current linguistics — across frameworks, not only inside your own. Because the journal is generalist and its editors recruit double-anonymous reviewers from across subfields, your positioning is the signal they read to place the paper and to match referees. A section that engages only your framework's in-group tells the editor this belongs at a subfield venue. This skill maps the conversation and locates your contribution in it.

When to trigger

• Drafting or restructuring the literature/positioning section
• A reader said the paper "ignores the obvious competing analysis" or "reinvents a known result"
• Writing a Discussion Note or Perspectives Commentary that must engage a specific published claim precisely and fairly
• Deciding which debates to foreground for a general linguistics readership

How to position for Language

1. Name the question, not the construction. State the live theoretical debate the paper joins (e.g., "is this alternation phonological or morphological?") in terms a linguist outside your area recognizes — not just your subfield's internal dispute.
2. Locate the gap as a tension, not a hole. Language rewards papers that adjudicate or reframe a real disagreement, not ones that fill an empty descriptive cell ("no one has looked at X").
3. Engage the strongest rival account, fairly. Cite the best version of the analysis you challenge; cross-framework reviewers will know it and will punish a straw man.
4. Set up the payoff. Positioning should hand off cleanly to lang-theory-building: the tension you name is the prediction you will adjudicate.

Cross-framework positioning (Language-distinctive)

Language prizes engagement across traditions. If your account is generative, still engage the functionalist or usage-based reading of the same data (and vice versa) where it bears on the claim. The goal is not to referee a framework war but to show your analysis wins on the data and predictions, whatever lens the reader brings.

Discussion Note / Commentary positioning

If you are writing a Discussion Note on a published Language article or a Perspectives Commentary:

• Represent the target claim faithfully — quote or paraphrase it exactly before critiquing.
• Make the critique substantive and general: it should teach the field something, not score a point on notation.
• Anticipate the author's response/Rejoinder — Language publishes both in the Perspectives format; a fair critique survives the reply.

Positioning move table (gap-as-tension, Language-style)

Because editors infer area and method from the blinded manuscript to recruit cross-subfield referees, a narrow literature map invites a poor reviewer match. Illustrative: a paper framed as "OT has not modeled this tone sandhi" reads as gap-filling; reframed as a tension between representational and computational accounts of the sandhi that the author's data adjudicate, it engages a debate the whole phonology community — and interested syntacticians — recognize.

Anti-patterns

• A subfield-only literature wall a cross-framework reviewer cannot follow
• Straw-manning the rival account (double-anonymous reviewers from that tradition will notice)
• "No one has studied X" instead of a genuine theoretical tension
• Citing only your own framework's in-group for coverage
• A Discussion Note that misreads or over-reads the target paper's actual claim

Positioning pass for Language

Treat this skill as an executable review pass, not a prose hint. First lock the empirical generalization, the evidence base, the analysis's predictions, and the theoretical payoff; then judge whether the manuscript answers the venue's real reader: linguists across subfields who value grounded analysis, transparent evidence, and fair engagement across frameworks.

• Do the pass: build a three-column map — incumbent debate, unresolved tension, this manuscript's delta; include one rival framework whose omission would make a referee doubt the fit.
• Return a ledger: give claim / evidence / risk / manuscript location rows so the next agent can edit rather than rediscover the issue.
• Sibling guard: compare against NLLT and Syntax (syntax), Phonology (phonology), Journal of Semantics / Natural Language Semantics (semantics), Diachronica (historical), Language Variation and Change (variation); if a sibling owns the contribution, recommend re-routing before polishing.
• Stop condition: do not give submission-ready advice until resources/official-source-map.md has been checked for volatile rules and the manuscript has one concrete fix for the largest venue risk.

Output format

【Question】the live linguistic debate the paper joins
【Key prior work】the strongest analyses engaged (across frameworks, fairly stated)
【Tension】the unresolved problem (not an empty descriptive cell)
【Our move】how the contribution adjudicates/reframes it → theory-building
【If Note/Commentary】the target claim + the general lesson the critique teaches
【Next】lang-research-design

Supplementary resources

• ../../resources/external_tools.md — reference managers and literature tooling
• ../../resources/official-source-map.md — Language cross-subfield review and dialogue expectations