Table 1
MIRROR compared with adjacent practices; numbers in parentheses are references.
| PRACTICE | WHAT IT ALREADY DOES WELL | WHAT MIRROR ADDS |
|---|---|---|
| Checksummed package (e.g., BagIt, RFC 8493) | Lists files with their digests, so changed bytes can be detected (3). | Connects listed files and their digests to specific claims. |
| RO-Crate | Packages research objects with structured metadata (1). | A local working packet whose files can later be packaged as an RO-Crate. |
| PROV | Describes what was produced, from what inputs, by which activity or agent (2). | A practical claim register for review, without a full provenance graph. |
| CodeMeta | Standardises descriptive software metadata in a linked-data JSON format (4). | A claim-level register; its own codemeta.json names the software, not the evidence for each claim. |
| Artifact review (e.g., CODECHECK) | Assesses availability, functionality, reuse, or reproduction in a venue process (5, 6). | Local materials prepared before formal artifact review. |
| Claim-evidence models | Models a scholarly claim, its evidence, and arguments as linked data (7). | Pairs each claim with evidence pointers and publishable wording, offline, before publication. |
| Supply chain tools | Signs and logs builds and their inputs in automated release pipelines (8, 9, 10). | Runs offline under the user’s control; signing and public logs stay with those tools. |
Table 2
Author’s assessment of the JANUS packet of 30 May 2026 and its leakage scan of 28 May 2026; counts are files, not claims. The scan covered the 21 files of the release supplement and five reviewer-only files, four of them with warnings.
| CRITERION | QUESTION FOR A REVIEWER | JANUS OBSERVATION |
|---|---|---|
| Completeness | Are the release files and descriptor files present? | Yes: Three release files and five source descriptors (Section 4). |
| File identity | Can retained bytes be checked later? | The PDF, source ZIP, and supplement ZIP were tied to SHA-256 records. |
| Claim clarity | Does each claim point to inspectable support? | The data availability statement was changed to name the release supplement, whose digest the packet records. |
| Problem visibility | Are warnings and exclusions visible? | The study’s own leakage scan flagged four files as reviewer-only, all from its MIRROR-format bundle (register, manifest, note file, and one source CSV); they stayed out of the release packet. |