Complete paper — HTML
The full manuscript rendered for the browser, including figures, tables, limitations, and supplementary navigation.
Read the work in the format that fits.
The publication shelf keeps the complete paper, browser edition, benchmark audit, and editable presentation together. Every item is built or checked from the same repository evidence.
Publication shelf
One study, four useful views.
Start with the HTML article for searchable reading, use the PDF for archival circulation, inspect the benchmark explorer for denominators and claim boundaries, or download the editable deck for a technical presentation.
Complete paper — PDF
The long-form article PDF used as the primary distribution artifact and validated against the shared manuscript body.
Benchmark explorer
Search every named benchmark and multidomain source with its substrate, execution status, retained records, and licensed claim.
Editable technical deck
A 26-slide technical review on the maintained seminar design system, with the current paper title and evidence boundary.
Artifact provenance
The Pages workflow copies the tracked paper PDF and technical deck into its download area, materializes the benchmark explorer from its checked-in source, and copies the authored site pages. The article page carries a digest of paper/tex/; the Pages builder refuses deployment when that digest, the generated benchmark explorer, or the generated quantitative method page drifts.
Evidence boundary: the headline efficiency results are research-prototype measurements on pinned public GitHub records and live provider calls. They do not establish production certification, semantic equivalence, full-workflow cross-repository or time-forward generalization, or superiority to hand-written code. A narrower two-read extension does carry cross-repository, time-forward evidence; see the research page for its separate claim boundary.
Source and reproducibility
- Paper artifact README — builds, evidence classes, and reproducibility commands
- Benchmark README — acquisition, preflight, and gated study commands
- Raw results — retained result files, manifests, and checksums
- Experiment verification — claim-by-claim recomputation and residual threats
The standard verification path makes no provider calls:
.venv/bin/python scripts/verify_release.py
.venv/bin/python paper/scripts/validate_artifacts.py
.venv/bin/python scripts/build_pages.py --output _site
.venv/bin/python -m pytest