Repository-native publishing works when the repository contains the report's operating state and reproducible package, while private and licensed sources remain behind explicit boundaries.
Choose what belongs under version control
Store templates, outlines, report source, bibliography data, source and claim metadata, visual specifications, scripts, checks, approval records, and release manifests when the buyer's policy permits it. Keep credentials, restricted source files, personal data, embargoed findings, and licensed material outside public repositories. The ledger can point to a controlled location without copying the material.
Give each report a predictable directory and one status file that names the current stage, approved outline, active draft, open holds, reviewers, outputs, and next transition. Repository history should support the current state, not force a new contributor to reconstruct it from every commit and discussion. Archive superseded packages without making them look current.
Render the same source deliberately
Pin the publishing tool and required extensions, document the clean build command, and produce the agreed HTML, PDF, document, or repository package from the reviewed source. Quarto documents multi-format rendering, citations, cross-references, manuscripts, websites, and continuous-integration publishing, making it one possible implementation rather than a required platform.
Automated builds should validate references, required metadata, missing assets, and output generation. Preserve the tool version, source revision, command, output checksums, and timestamp in a release receipt. A passing render shows that the package was generated; it does not decide that a figure is legible, a claim is supported, or the document meets every destination rule.
Reset the system after release
Mark the exact released revision, publication destination, URL or identifier, date, and approver. Close resolved holds, carry forward open corrections, and create the next-cycle state without overwriting the release receipt. If the public report changes, record whether the update is a correction, source refresh, formatting change, or new edition.
Reality Contact, LLC installs and documents this operating path for Research Release Desk. The buyer controls repository visibility, source permissions, publication accounts, corrections, retention, and ongoing maintenance. The installed workflow does not make private research safe to publish or guarantee reproducibility beyond the data, tools, environments, and checks actually included.
Where the service stops
Reality Contact, LLC installs research-publishing operations but does not conduct peer review, validate data or methods, determine authorship, approve conclusions, give legal or ethics advice, warrant citation accuracy, represent a journal, or guarantee acceptance, indexing, readership, or search visibility. The buyer supplies authorized sources, names responsible authors and reviewers, approves the outline and claims, resolves methodological and ethical questions, accepts every visual and format, and authorizes publication through its normal governance. This workflow service does not replace methodological, statistical, subject-matter, peer, legal, ethics, privacy, authorship, accessibility, or publication review. The buyer authorizes all sources, assigns every reviewer, approves all claims and visuals, and controls publication; private research waits for secure intake and written deletion terms.
Sources: Quarto authoring features for citations and multiple outputs; Quarto publishing destinations and continuous integration.