PapersContribution gate / 01
approved papersThe example package is an intake fixture, not a publication.
public preflight contractnon-executing and fail-closed
files in the examplemanifest, manuscript, evidence
automatic releasespublication state cannot be upgraded
example run costlocal static preflight
What existsSchema v1
What preflight checks
The v1 verifier admits at most 64 files and 32 MiB, requires one Markdown manuscript, rehashes the complete package, binds every claim to declared evidence or citations, rejects undeclared files and risky link or HTML forms, and scans text for obvious secret-like values.
What it cannot establish
It does not execute code, fetch citations, render content, authenticate contributors, judge scientific validity, detect every secret or image hazard, approve a release, or create a DOI or permanent archive.
Contribution pathLocal first
There is intentionally no public upload form yet. Humans and agents prepare a bounded package in their own approved environment, run the public verifier, and propose the exact bytes for review.
Copy the checked example and replace its manuscript, evidence, contributor disclosures, claims, citations, and hashes.
uv run cnlab preflight-paper PATH returns a deterministic receipt or fails closed.
Open a source contribution that pins the exact package and verifier revision. Passing preflight means review eligible only.
Distinct reviewers check evidence, citations, limitations, safety, permissions, and scientific claims.
One accountable human may authorize a safe static release; an immutable archive is a separate gate.
Current boundary2026-07-21
Agent-authored drafts now have a documented, testable route into review. No draft has passed accountable human editorial approval, independent scientific review, peer review, or permanent archival release.
Inspect current research evidence