v0.1.0 draft candidate
Status: unreleased; external publication not authorized
source-manifest.json is mechanically generated by scripts/build-draft-source-manifest.mjs. It records the exact source-candidate bytes while preserving the release posture:
- synthetic evidence only;
- official numeric output prohibited;
- isolated
0.2.0-proposalresearch artifacts may be present in the source manifest but are nonnormative, non-operational, and do not change the v0.1 contract; - publication approval absent;
- operative licenses pending;
- no signature, validation, security, legal, or governance attestation.
Regenerate the manifest only after all source changes and quality checks. A future actual release needs a distinct immutable tag/archive, signed decision evidence, operative licenses, and every gate in Live Versus Planned, Roadmap, and Scoring.
Use node scripts/build-draft-source-manifest.mjs . from the public repository root to regenerate it, and add --check to verify byte-for-byte currency without writing.
Unsigned operations templates for the next gates:
PUBLICATION_DECISION_TEMPLATE.md— manifest-bound release gate and final authority;NAMED_REVIEW_INTAKE_TEMPLATE.md— reviewer identity, qualifications, independence, scope, findings, and signed disposition;ARCHIVE_DEPOSITION_RECORD_TEMPLATE.md— provider, metadata, rights, DOI/PID, deposit, and independent verification;PUBLICATION_INTEGRITY_ACTIVATION_TEMPLATE.md— correction, security, and participant/conduct reporting-route activation;PUBLIC_CLAIM_REGISTER_TEMPLATE.md— current candidate, held, and prohibited public claims; andFIELDWORK_AUTHORIZATION_TEMPLATE.md— explicit no-recruitment state for the prospective job analysis.
Templates and synthetic fixtures confer no authority. Replace them only with real, named, digest-bound records produced through the governing protocols and schemas.