Curation Policy (Continuity Science / CSS Community)

This Zenodo community curates work in Continuity Science (CSS): receipts-first methods for measuring coherence, drift, failure, and repair in complex systems under load.

In scope

• Manuscripts, preprints, protocols, preregistrations, and method notes

• Datasets, synthetic benchmarks, and analysis code needed to rerun results

• Pattern cards / catalogs with explicit observables and pass–fail bars

• Instrument specs and governance audits (e.g., gated inference, null-world baselines, integrity screens)

• Replications, negative results, and refusals with documented evidence

Minimum standards (required)

• Clear title/abstract describing scope and claims

• Versioning + changelog (or “what changed” note)

• Stated observables, procedure, and explicit failure criteria (pass/refuse bars)

• Provenance/receipts: how data were produced, and how conclusions were gated

• License + citation information; include code/data links when applicable

Out of scope / not accepted

• Unverifiable claims with no procedure or data trail

• Pure opinion, persuasion campaigns, or normative/policy directives presented as measurement

• Harassment, doxxing, or targeted attacks

• Content that relies on private revelations or cannot be independently checked

Curation process

• Submissions may be approved, requested for revision, or declined based on scope and standards above.

• When standards are not met, the community may post a refusal (reason for non-admissibility) rather than debate.

• Replications and critiques are welcome if they include receipts and a rerunnable method.

Principle
This community is audit-first: we prioritize work that others can rerun, check, and refuse or pass on evidence—not on status or persuasion.