
% Auto-generated working paper draft for research.jmp0x1b.com
% Build: pdflatex -interaction=nonstopmode paper-032-researchpack-a-reproducible-pdf-latex-artifact-and-errata-pipeline-for-research-.tex

\documentclass[11pt]{article}
\usepackage[margin=1in]{geometry}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{lmodern}
\usepackage{amsmath,amssymb,amsthm}
\usepackage{array}
\usepackage{hyperref}
\usepackage{enumitem}
\usepackage{verbatim}
\usepackage{fancyhdr}
\usepackage{lastpage}
\hypersetup{colorlinks=true, linkcolor=black, urlcolor=black, citecolor=black}
\setlist[itemize]{leftmargin=1.2em}
\setlist[enumerate]{leftmargin=1.4em}
\newtheorem{proposition}{Proposition}
\newtheorem{definition}{Definition}
\newtheorem{protocol}{Protocol}
\pagestyle{fancy}
\fancyhf{}
\lhead{JMP0X1B Research}
\rhead{Working paper draft}
\cfoot{\thepage\ of \pageref{LastPage}}
\sloppy

\title{\Large Paper 032 / Application 009\\[0.6em]\textbf{ResearchPack: A Reproducible PDF, LaTeX, Artifact, and Errata Pipeline for research.jmp0x1b.com}\\[0.3em]\large Publishing papers as auditable software supply chains}
\author{JMP0X1B Research Group}
\date{Working paper draft / June 13, 2026}
\begin{document}
\maketitle
\begin{abstract}
ResearchPack is a publication pipeline for research.jmp0x1b.com. It treats every paper as a bundle: LaTeX source, PDF build, figures, code, data, build logs, provenance, errata, and revision history. The pipeline is designed for speculative, negative, and engineering papers where auditability matters as much as presentation.
\end{abstract}

\noindent\textbf{Status.} Draft manuscript for review and revision. This paper is not an empirical claim of new physics or field-ready technology. It is a structured proposal, theory note, protocol, or application architecture intended to be auditable, falsifiable, and publishable with source.

\tableofcontents
\newpage

\section{Problem}
A PDF alone cannot carry enough evidence for technical review. Conversely, raw repositories without a stable manuscript surface are hard to cite. The problem is to publish papers as stable documents backed by rebuildable artifacts and revision-controlled errata.

\section{Model}
Each paper has a manifest, source tree, build recipe, artifact digests, PDF, optional data/code, review state, and errata log. The web index links PDF and TeX, while the manifest maps claims to supporting artifacts.


\[
  \mathrm{PaperBundle}=\{\mathrm{tex},\mathrm{pdf},\mathrm{figures},\mathrm{code},\mathrm{data},\mathrm{manifest},\mathrm{errata}\}.
\]
\[
  \mathrm{RebuildOK}\Rightarrow H(\mathrm{pdf}_{\mathrm{rebuilt}})=H(\mathrm{pdf}_{\mathrm{published}})\;\text{or documented drift}.
\]


\section{Claims}
\begin{enumerate}
\item \textbf{Claim 1.} Every JMP0X1B paper should publish source next to the reader-facing PDF.
\item \textbf{Claim 2.} Claim-to-artifact mapping makes review faster and errata more precise.
\item \textbf{Claim 3.} Negative results need the same publication dignity and artifact structure as positive results.
\item \textbf{Claim 4.} A reproducible paper pipeline is also a trust signal for future technology applications.
\end{enumerate}

\section{Evidence Plan}
A prototype should rebuild the existing paper style on a small corpus and verify that PDFs, TeX files, and manifests stay synchronized. A second test creates an erratum and demonstrates traceable supersession without deleting the original paper.

\section{JMP0X1B Implementation Surface}
JMP0X1B can define the manifest schema, digest verification, build steps, and web-index generation. The package should integrate with provenance and document-control libraries.

\subsection*{Illustrative JMP0X1B-style contract}
\begin{verbatim}
record PaperBundle { id: Text, tex: Digest, pdf: Digest, artifacts: List<Digest>, errata: List<Erratum> }
fn publish(bundle: PaperBundle) -> PublishReceipt effects{Build, Provenance, DocControl, Audit}
\end{verbatim}


\section{Release And Review Plan}
Release a manifest specification, example bundle, build script, web index generator, and validation report for this paper pack.

\section{Open Questions}
\begin{itemize}
\item Should the site require deterministic PDF hashes?
\item How should large raw data be linked without bloating paper bundles?
\item What errata severity levels are needed?
\item Can reviewer comments be preserved privately while public errata stay concise?
\end{itemize}

\section{Conclusion}
ResearchPack makes the publication site itself part of the research infrastructure. It turns papers into auditable supply chains.

\section*{References}
\begin{thebibliography}{99}
\bibitem{jmp001} JMP0X1B Research Group. \emph{Twelve Five-Dimensional Projection Models for Maxwell-Compatible Electromagnetism}. Working paper, 2026. \url{https://research.jmp0x1b.com/papers/twelve-5d-projection-electromagnetism.html}
\bibitem{jmp002} JMP0X1B Research Group. \emph{Electrostatic Projection Couplings in Five-Dimensional Maxwell-Compatible Theory}. Working paper, 2026. \url{https://research.jmp0x1b.com/papers/electrostatic-projection-couplings-5d-electrogravity.html}
\bibitem{jmp_main} JMP0X1B. \emph{Technology for Earth, designed with space as the operating condition}. \url{https://jmp0x1b.com/}
\bibitem{jmp_libs} JMP0X1B. \emph{jmp0x1b Package Registry}. \url{https://libs.jmp0x1b.com/}
\bibitem{wilkinson} M. D. Wilkinson et al. The FAIR Guiding Principles for scientific data management and stewardship. \emph{Scientific Data}, 3:160018, 2016.
\bibitem{prov} World Wide Web Consortium. \emph{PROV-DM: The PROV Data Model}. W3C Recommendation, 2013. \url{https://www.w3.org/TR/prov-dm/}
\bibitem{jmp_provenance} JMP0X1B. \emph{jmp0x1b\_provenance package}. \url{https://libs.jmp0x1b.com/packages/jmp0x1b_provenance}
\bibitem{jmp_lang_spec} JMP0X1B. \emph{jmp0x1b\_lang\_spec package}. \url{https://libs.jmp0x1b.com/packages/jmp0x1b_lang_spec}
\end{thebibliography}

\end{document}
