Back to research

Research / Paper Schema

Living paper
structure.

Every paper is treated as an editable knowledge object. The PDF is only a render. The source, figures, math, checkpoints, references, implementation anchors, and evidence manifests are the actual structure that lets another agent reproduce and verify the chain.

source

Editable Source

Canonical LaTeX or Markdown manuscript. The source remains the truth while the paper is live.

pdf

Rendered PDF

Generated artifact from the editable source. Draft PDFs can be public, but final PDFs require a release gate.

math

Math Blocks

Formal definitions, equations, objectives, and invariants that can be audited separately from prose.

figures

Figures and Graphs

Generated plots, diagrams, and graph artifacts. Figures should have source data or render commands.

evidence

Evidence Manifest

Run IDs, packet IDs, datasets, commits, logs, and review status. Evidence should survive outside the prose.

implementation

Implementation Anchors

Code paths and system components that make the paper executable rather than only conceptual.

intersections

Intersection Tags

Tags used by daily ingest to decide whether an external paper touches this paper's claims or methods.

Skeleton

Standard paper sections

01

Central Claim

required

One falsifiable sentence stating what the paper proves, proposes, or measures.

02

Abstract

required

Problem, method, evidence, result, and implication in compressed form.

03

Problem Statement

required

The precise failure mode in existing systems or measurements.

04

Related Work

required

External papers grouped by technique family, not a generic citation dump.

05

Method

required

The architecture, algorithm, governance rule, or representational move being introduced.

06

Math and Formalism

required

Definitions, operators, objective functions, invariants, and survival criteria.

07

Implementation Map

required

The code paths, harnesses, schemas, scripts, services, or devices that embody the method.

08

Data and Evidence

required

Admissible data, rejected data, provenance, leakage boundaries, and review gates.

09

Evaluation

required

The tests that decide whether the claim survives, including negative results.

10

Results

required

Measured outcomes tied to exact runs, commits, snapshots, or packet IDs.

11

Limitations

required

What has not been proven, what is blocked, and what would falsify the paper.

12

Release Gate

required

The condition that must be satisfied before the PDF becomes citation-ready.

13

References

required

External papers and internal companion papers linked to the claim they support or challenge.

14

Appendix

Schemas, equations, figure sources, reproducibility commands, and extra tables.

problem

What failure mode or missing primitive does this paper isolate?

method

What method, architecture, or governance rule is proposed?

implementation

What concrete system, code path, harness, or protocol embodies the method?

data

What data or evidence is admissible, and what is explicitly excluded?

evaluation

What tests decide whether the claim survives?

references

What external literature families should be compared against?

openQuestions

What remains unresolved before release or citation?

Rendering

LaTeX and graphs

Every paper has a canonical source type: LaTeX first when math or formal claims matter, Markdown allowed for early drafts.

Every PDF is a render from source, not an independently edited artifact.

Every figure or graph has a source slot: script, data manifest, diagram file, or explicit manual-render note.

Every rendered PDF carries a lifecycle label: draft, working draft, release candidate, or published.

Every final release needs a clean build, reviewed claims, checked references, and a frozen evidence manifest.

Checkpoints

Proof chain

paperpending

Claim checkpoint

Every central claim must point to a proof anchor or remain labeled as speculative.

implementationpending

Implementation checkpoint

Every method should identify the code path, harness, schema, or protocol that embodies it.

experimentpending

Evidence checkpoint

Every reported result should point to run IDs, packet IDs, data snapshots, commits, or review artifacts.

external-referencepending

Reference checkpoint

Every external claim should resolve to a cited paper, benchmark, standard, or documented prior system.

paperpending

Release checkpoint

Every PDF needs a named condition before it can move from draft to citation-ready.

Daily ingest

Intersection protocol

01

Extract external paper technique tags, task domains, data assumptions, evaluation methods, and claimed contribution.

02

Compare those tags against each internal paper's intersection tags and reference families.

03

Classify the relationship: supports, challenges, replaces, extends, evaluates, or unrelated.

04

If the external paper intersects, attach it to the internal paper as a reference candidate with a reason.

05

If the external paper changes a method or release gate, create a revision note rather than silently editing the claim.