Publishing Papers
This guide covers the full workflow from experiment results to a published paper on arXiv. Hubify Labs handles drafting, review, compilation, and submission packaging.
Overview
The paper pipeline is agent-assisted at every step, but you maintain full editorial control.
Step 1: Create a Paper
- Go to Papers in the sidebar
- Click New Paper
- Enter title, select template (
prd for Physical Review D)
- The Paper Lead generates an initial outline based on your lab’s completed experiments
Step 2: Build the Claims Table
The claims table is the backbone of your paper. Every scientific assertion must be backed by evidence.
Step 3: Draft Sections
Agents draft sections in parallel. You can direct which experiments feed into which sections:
Step 4: Cross-Model Peer Review
Run a structured peer review using multiple AI models:
The review checks:
- Accuracy, Are claims consistent with the data?
- Completeness, Are there missing analyses or citations?
- Clarity, Is the writing clear and well-structured?
- Overclaiming, Are conclusions justified by the evidence?
- Novelty, Does the paper clearly state what is new?
Review results appear as structured feedback with specific suggestions per section.
Step 5: Revise
Apply review feedback:
Each revision round is logged with a diff showing what changed and the rationale.
Step 6: Compile to PDF
LaTeX compilation requires texlive-publishers (for revtex4-2). This runs on a GPU pod, not locally.
The compiler verifies:
- Zero undefined references
- All figures embedded (PDF size should be 15-25 MB for a paper with 10+ figures)
- Correct page count
- Bibliography completeness
Step 7: Package and Submit
The package includes:
- Compiled PDF
- LaTeX source (
.tex)
- Figures (all PNGs)
- Bibliography (
.bib)
- Supplementary data (if any)
Upload the package to arxiv.org following their submission guidelines.
Tracking Readiness
Monitor paper progress in the readiness dashboard:
Best Practices
- Lock claims before drafting, do not write sections around unverified claims
- Run reviews after every major revision, not just at the end
- Compile frequently to catch LaTeX issues early
- Use
revtex4-2, not aastex631
- Keep figures in the same directory as the
.tex file