Writing Style (jet-writing-style)

When to trigger

• Drafting or polishing a JET theory manuscript
• Converting a working paper into JET's elsarticle theorem-proof format
• Tightening notation and statements before submission

JET house style

• Typeset in LaTeX, Elsevier `elsarticle` class. Source must be editable .tex; PDF is not

accepted as a source file. Use proper theorem environments (amsthm): Definition, Assumption, Proposition, Lemma, Theorem, Corollary, Proof.

• Theorem-proof structure, not narrative-empirical. Set up the environment and primitives, state

assumptions, then results, then proofs (heavy ones to an appendix). The reader should be able to read every formal statement without hunting through prose.

• Notation discipline. Introduce each symbol once, never reuse a symbol for two objects, keep the

body and proofs identical. A notation table helps in long papers.

• References. First submission can use any complete, consistent reference format. JET's proof-stage

style is name-year / author-year; elsarticle-harv is the safest LaTeX default. References cited in the abstract must be given in full. Keep unpublished results / personal communications out of the reference list.

• Abstract / keywords / Highlights. Keep the abstract to 250 words or fewer, supply **1-7

English keywords, and include Highlights only if you can make 3-5 bullets of 85 characters or fewer** each. JEL codes are optional metadata rather than a substitute for clear keywords.

• Generative-AI disclosure belongs in the submission, not the prose; reviewers/editors are barred

from using such tools — write so a human expert can follow every step.

Prose targets

• State each theorem so it is self-contained — readable without the surrounding paragraph.
• Give a one-line intuition before a long proof; do not let intuition substitute for rigor.
• Prefer "We prove that …" over hedged "essentially / roughly" phrasing the theorem does not support.

Notation audit

Before submission, create a notation pass:

• Every primitive is introduced before first use.
• Every assumption label is referenced in at least one theorem or lemma.
• Every theorem statement can be read without searching the previous paragraph.
• Symbols in figures, proofs, and appendices match the body exactly.
• Appendix proof numbering preserves the main theorem dependency order.

Notation consistency is not cosmetic in JET; it is how referees verify the argument.

amsthm scaffold for a JET manuscript

% Body carries statements + a sketch; the appendix carries full proofs with restatements.
\begin{assumption}\label{a:sc}
Each type's utility satisfies strict single crossing in (action, type).
\end{assumption}

\begin{theorem}\label{thm:main}
Under Assumptions \ref{a:sc}--\ref{a:compact}, an optimal mechanism exists and is deterministic.
\end{theorem}

\begin{proof}[Sketch] % ≤ 1 paragraph in the body: name the key step, point to the appendix
The allocation is pinned down by Lemma~\ref{lem:mono}; a duality argument then delivers the
transfers. Full details are in Appendix~B.
\end{proof}

The pattern to copy: the theorem cites its assumptions by label, the sketch names the key argument in one sentence, and nothing in the body forces a referee to page-flip mid-statement.

Sentence-level register for theory prose

• Statements quantify ("for every", "there exists") rather than gesture ("in general",

"typically").

• The body says what each lemma buys economically ("Lemma 2 rules out pooling at the top"); the

appendix carries the epsilon-management.

• "It is easy to see" is banned wherever a referee could disagree — replace it with the one-line

reason or a pointer to the appendix step.

• Intuition paragraphs are labeled as intuition and are never load-bearing: deleting them must

leave the proof intact.

Hedged-claim rewrite (micro-example)

• Before: "Our results show that ambiguity essentially eliminates the gains from screening."
• After: "Theorem 3 shows that for maxmin bidders with full-support prior sets, the optimal

mechanism is a posted price; screening gains are zero in this class — and only in this class (Example 4)."

The rewrite replaces "essentially" with the exact class where the claim holds and the example that bounds it. Run this transformation on every hedge word in the abstract and introduction.

Anti-patterns

• Submitting PDF source instead of .tex
• Mixed reference styles, or abstract citations abbreviated to "et al."
• Symbol reuse and notation drift between statement and proof
• An empirical-paper voice (data-story framing) imposed on a theory result

Output format

【Format】elsarticle .tex, amsthm environments? [Y/N]
【Notation】one symbol ↔ one object, body=proof? [Y/N]
【References】author-year ready; abstract refs in full; no personal comms? [Y/N]
【Metadata】≤250-word abstract; 1-7 keywords; Highlights compliant if used? [Y/N]
【Disclosures】AI declared at submission? [Y/N]
【Next】jet-tables-figures / jet-submission