Publication checklist
This file records release blockers; it is not evidence that publication has occurred. Do not publish a draft, pilot-only artifact, or placeholder metadata.
Scientific and artifact gates
- The 24 pilot slots are complete and clean under
pilot.lock. - The protocol, task suite, schedule, analysis, and report sources are
frozen and
freeze.lockverifies. - All 144 confirmatory slots resolve to valid terminal records, including any explicitly represented infrastructure outcomes; every non-final non-retryable infrastructure slot has a valid terminal-missing acknowledgement and was not retried.
- Every aborted confirmatory generation passes content-addressed archive verification and is excluded from the replacement primary analysis.
-
paper.compose --mode releaseandpaper.compose --mode verifypass over the exact raw records and artifacts. - Privacy, license, fairness, statistics, paper/code consistency, and adversarial audits pass.
- The post-freeze release adjudication reports the frozen base gate as
FAIL_KNOWN_FALSE_POSITIVES, binds only the exact entries recorded indata/publication_scan_adjudications.json, and separately reportsPASS_WITH_RECORDED_EXCEPTIONS; no unmodified frozen-policy PASS is claimed. - Every retained
data/artifacts/*.patchhas exactly one materialized entry indata/artifact_license_map.json; each entry resolves through the bound task manifest to one exact repository/commit rule.
Citation and Zenodo metadata
- Public author name verified as Song Luo; citation ordering is
family name
Luo, given nameSong. - Confirm whether an ORCID and affiliation should be included; omit both if they are not explicitly confirmed.
- Choose the immutable release version and release date.
- Finalize title, abstract, description, and keywords from the audited report, without claims stronger than the measured results.
- Reserve the Zenodo DOI before the final release commit.
- Replace the pre-publication
CITATION.cffmessage and add the exact version, release date, DOI, and Zenodo URL. - Prepare and independently compare the manual Zenodo deposit metadata
against
CITATION.cff(author, title, version, date, description, keywords, publication type, and reserved DOI). Do not add.zenodo.json: this mixed-license report artifact is deposited manually rather than through Zenodo's single-license GitHub integration. - Keep the report text under CC-BY-4.0 and describe the repository's mixed licenses rather than declaring the whole archive CC-BY-4.0.
Exact-archive release
- Create
rrrrrredy/beforedone-paperonly after the audited artifact is complete. - Commit the reserved DOI metadata and verify a clean tree.
- Tag the exact final commit and build the archive from that commit.
- Create a GitHub Release for that exact tag.
- Upload that exact archive to Zenodo, verify its checksum, then publish the record.
- Confirm the GitHub tag/release and Zenodo record resolve to the same commit and archive.
- Update
rrrrrredy/rrrrrredyonly after both destinations resolve: introduce the paper beside BeforeDone and link the product repository, paper repository, exact GitHub release, and Zenodo DOI. - Do not modify the BeforeDone product repository without separate authorization.