Reproducing the record.

Gubernaut publishes its own safety and auditing artifacts rather than describing them. The engineering receipts folder in the public repository holds the raw run artifacts for the fail-safe battery, the concurrency isolation run, the edge soak and the ablation, published unedited apart from stripped local paths. The fail-safe battery is published together with the round that failed it: the pre-hardening run recorded 4 fail-open leaks in Gubernaut's own code and the hardened run records 0. Four reproduction levels let you re-run the record yourself, and the first three need no API key and cost nothing.

Source: HARDTEST v1.0 release gates, 2026-07-24.

The paper is on arXiv as 2607.24339, cross-listed cs.AI, cs.CL, and archived on Zenodo under DOI 10.5281/zenodo.21303518. Both carry the same text, and the Zenodo record also holds the complete validation release.

Cite 10.5281/zenodo.21303518, the concept DOI. A concept DOI resolves to the newest version of a Zenodo record, so a citation written today still lands on the current release. Version-specific DOIs exist inside the archive and are not used in published copy.

The paper is a preprint on arXiv and has not completed journal peer review. The evaluation was pre-registered before data collection, and the transcripts, judge panels and analysis scripts are public, so the result can be checked directly rather than taken on the strength of a review.

Cite the paper by its concept DOI, 10.5281/zenodo.21303518, or by its arXiv identifier 2607.24339. A ready BibTeX entry sits on the research page of this site, and the repository carries a CITATION.cff file that reference managers read directly.

The paper and the validation release are CC-BY-4.0, so reuse and redistribution are permitted with attribution. Software carries Apache-2.0 instead. Figures on this site are CC-BY-4.0 and ship machine-readable licence metadata alongside them.

Dushyant Sharma, M.Eng., at Gubernaut Research, ORCID 0009-0007-6534-0347. Gubernaut Research is an independent lab, and the same author wrote the controller, ran the evaluation and published the record.

The release holds every endurance and evaluation transcript for four frontier families in both arms verbatim, all judge panels with SHA-256 provenance, the sealed matrices, tidy per-turn telemetry tables, and the extraction, statistics and figure scripts that regenerate every published number.

The sealed release is archived on Zenodo under DOI 10.5281/zenodo.21303518 and mirrored in the public GitHub repository thegubernaut/Gubernaut_Validation. Zenodo is the citable archive of record; GitHub is the working copy that carries the scripts.

Each transcript and judge panel carries a SHA-256 hash recorded in the sealed release, so any later edit changes the hash and becomes visible. Verifying is a local hash of the file against the manifest, which requires no trust in this website.

Re-judging is the intended path. All transcripts and four-family judge panels ship with SHA-256 provenance, and the extraction scripts that turn raw panels into every published number are in the public repository, so a different panel or a different rubric can be run against the same replies.

The spend figures are outputs of a scoring script rather than hand-tallied estimates, and the receipts harness is part of the published record. Running the same battery against your own keys produces your own prices, and the governed-to-ungoverned ratio is the portable part of the result.

Source: Pre-registered receipts benchmark, 2026-07-19. Scored output of harness/report.py.

The evaluation was pre-registered: the design, the scoring protocol and the analysis were fixed and written down before data collection began, and the pre-registration documents ship inside the public release. Every fix to a documented failure mode was likewise declared before it was written.

A fresh panel scoring the published transcripts and finding the regulated arm no calmer would falsify the central claim, as would a governed run that fails to hard-stop the loop battery, or a replication in which recovery does not return to baseline. The materials to attempt each of those are published.

Report it as a public issue on the validation repository, or write to the lab directly. Corrections are made in the open with a dated note, and the published numbers on this site trace to a single register file, so one correction propagates to every page at once.