How to read a paper page

Status badges

Every paper carries a status badge showing where it stands in the publication pipeline:

• Forthcoming — Accepted by the journal; not yet released.
• Online First — Available online ahead of the print issue.
• Published — Formally published in a journal issue.
• Classic — A foundational paper in the field, summarized from the published article.

These are pulled directly from Crossref and OpenAlex metadata, not judged by a model.

The two-layer summary format

Every paper page is built from the same two-layer structure:

Layer 1 — “What this paper finds — and why it matters.” A plain-language preview, 3–6 sentences, written to carry the load-bearing qualifiers: the causal-vs-correlational verb, the scope condition, the magnitude with its uncertainty. Many pages also open with a short In brief box — 60–110 words answering the question, the answer, and why it matters, aimed at a reader with no background in the paper’s subfield.

Layer 2 — “Questions & answers.” A deeper technical Q&A that goes as far as faithful coverage of the paper requires — no length cap, no padding. Pages with more than eight questions group them into collapsible sections so the page stays scannable; expand any question to read the full answer.

Most pages close with a Key terms in this paper glossary, defined in the paper’s own sense rather than a textbook-generic one, and a Record box with the full bibliographic detail (journal, volume, issue, DOI, JEL codes, topics).

How a summary gets made

See the About page for the full pipeline: metadata from APIs, the full working paper (never an abstract alone), a two-layer draft, a claim-grounding review, and a human merge decision before anything goes live.