๐Ÿš€Shippingscore 93.3May 15, 2026ยท2605.16194cs.DLcs.AIcs.IRcs.MA

paper.json: A Coordination Convention for LLM-Agent-Actionable Papers

Arquimedes Canedo

Narrative

A companion JSON schema for academic papers that gives LLM agents stable, citable anchors for sub-claims (C1), an explicit list of what the paper does *not* claim (C2), exact shell commands to reproduce each figure (C3), and stable definition IDs (C5). The core bet is that current prose PDFs cause systematic agent failures โ€” scope hallucination, non-reproducible figures, un-citable sub-claims โ€” and a lightweight sidecar file costing under an hour to write fixes all of them without changing the PDF itself.

Zero citations and no production traction yet. The referenced repos are all arXiv digest aggregators, not implementations. The paper's own validator (`uv run validator.py paper.json --against paper.typ`) exists at the author's GitHub, but adoption depends on whether authors voluntarily ship `paper.json` alongside PDFs โ€” a coordination problem the convention itself can't solve unilaterally.

Abstract

LLM agents routinely serve as first (and sometimes only) readers of academic papers, skimming for sub-claims, extracting reproducibility steps, and generalizing scope. Standard prose papers produce recurring failures in this role: sub-claims that cannot be cited at sub-paper granularity, scope overextension beyond what the paper tests, and figure commands buried in codebases rather than the paper itself. We propose `paper.json`, a companion JSON file that travels with the PDF and addresses each failure with a lightweight convention: stable claim IDs (C1), an explicit does-not-claim list (C2), exact per-figure shell commands (C3), and stable definition IDs (C5). A fifth convention (C4) holds that minimum viable compliance, hand-written JSON alongside the PDF, is achievable in under an hour for a finished paper without touching the human-readable output. C1, C2, C3, and C5 are open invitations: an agent that reads a compliant paper and acts on it produces evidence for or against them. This paper is itself compliant: `uv run validator.py paper.json --against paper.typ` passes. Repo: https://github.com/arquicanedo/paper-json

Citation timeline
Not enough citation snapshots yet to plot a timeline. Come back after a few cron runs.