Comparison to Existing Tools

The gap analysis established that no single tool integrates all six cross-cutting concerns. Here we synthesize the fourteen-dimension comparison into three structural insights. First, the landscape bifurcates: workflow managers (Snakemake [koster2012snakemake], Nextflow [ditommaso2017nextflow], CWL [amstutz2016cwl]) provide distributed execution but no manuscript support; publication tools (Quarto [allaire2024quarto], Jupyter Book, R Markdown [xie2018dynamic], Overleaf [overleaf2025], Prism [openai2026prism]) author documents but embed no integrity guarantees; and DVC [iterative2024dvc] versions artifacts without orchestrating pipelines. template/ occupies the intersection, sacrificing distributed execution for unified enforcement of testing, provenance, and documentation. This positioning is complementary—a mature deployment might use Nextflow upstream and template/ for rendering, testing enforcement, and provenance downstream. Typst [madje2023typst], with its faster compilation cycle, is not one of the nine compared peers but could serve as an alternative rendering backend if a Pandoc writer were contributed.

Second, the eight enforcement capabilities template/ co-locates—testing enforcement, coverage thresholds, steganographic watermarking, multi-project management, AI-agent documentation, the agentic skill protocol, an interactive TUI, and Zero-Mock policy—are individually straightforward (and several, such as multi-project management and AI-agent documentation, are matched in part by individual peers). Their value here lies in a shared pipeline contract: required test and documentation gates run together, while selected provenance stages carry their own validation. The FAIR4RS principles [barker2022fair4rs; lamprecht2020towards] articulate what research software quality requires; FAIRsoft [garijo2024fairsoft] scores compliance observationally; template/ operationalizes part of this agenda by failing project tests below the declared 90% floor and validating provenance artifacts when those stages are enabled. Cohen et al.’s four pillars of research software engineering [cohen2021four]—sustainability, quality, community, and policy—are addressed primarily through the first two pillars via quality-gated automation.

Third, the AI-agent documentation dimension reveals an underserved need. Overleaf and Prism provide AI writing assistance, but neither exposes structured documentation for external agents to consume. template/’s AGENTS.md + SKILL.md layer enables an agent entering the repository to discover capabilities, understand API contracts, and invoke modules without prior training (Documentation Duality, AI Collaboration).

FAIR4RS Evolution (2024–2026)

Since the FAIR4RS principles were published [barker2022fair4rs], the community has moved toward operationalization. The RDA Virtual Plenary 24 (April 2025) featured a two-year retrospective review [honeyman2024fair4rs] recommending principle amendments—notably adding reproducibility as an explicit requirement and clarifying “domain-relevant standards”—alongside a leadership refresh and parallel guidance activities. The ReSA Actionable FAIR4RS Task Force (launched December 2024) analyzed the 17 principles into six actionable categories (identifiers, metadata for publication/discovery/reuse, standards, references, and licenses), with a first draft expected by September 2025 [resa2024actionable]. Tools for automated FAIR assessment have also matured: the F-UJI extension for research software evaluation now scores against FRSM-04 through FRSM-17 metrics, complementing Garijo et al.’s FAIRsoft evaluator [garijo2024fairsoft]. template/’s pipeline-enforced quality gates—coverage thresholds, documentation completeness checks, and provenance embedding—anticipate this operationalization trend by implementing FAIR4RS not as a post-hoc assessment but as an architectural invariant.

In Gentleman and Temple Lang’s terminology [gentleman2007research], template/ is a research compendium scaled to the repository level—bundling not just one study’s code and data but N studies, with shared infrastructure, automated testing, and embedded provenance. Nüst et al.’s executable research compendium (ERC) [nust2017containerization] extends this vision with containerized reproduction environments; template/ complements containerization by adding the testing enforcement, multi-project management, and provenance embedding layers that ERCs do not address.