release: freeze the specification at v0.1.0 - #4
Open
ion-alpha-dev wants to merge 1 commit into
Open
Conversation
Every surface flips from 0.1.0-draft to 0.1.0 in one change: SPEC/CONFORMANCE/GLOSSARY/predicate version headers, registry.json, CITATION.cff (version and date-released, ahead of the tag Zenodo will archive), the two vector manifests as regenerated by the reference implementation (suite_version is generator output; byte-identical to flynn, 73 files, zero drift), client README prose, and the draft-status paragraphs across README, CONTRIBUTING, SECURITY, GOVERNANCE, PATENTS and VERSIONING. SPEC Section 7 gains the freeze charter: the enumerated frozen and not-frozen lists, including that the name is frozen because it is a hashed constant (DECISIONS.md D1). The word draft survives only in historical text. check_suite: 65 vectors, versions aligned.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The version flip: every surface goes
0.1.0-draftto0.1.0in one change. Version headers inSPEC.md,CONFORMANCE.md,GLOSSARY.md,predicates/run-provenance.md;registry.json;CITATION.cff(version anddate-released, committed ahead of the tag so the Zenodo archive of the tagged tree is correct); both vector manifests exactly as regenerated by the reference implementation; client README prose; and the draft-status paragraphs across README, CONTRIBUTING, SECURITY, GOVERNANCE, PATENTS and VERSIONING.SPEC.mdSection 7 gains the freeze charter: the enumerated frozen and not-frozen lists, including that the name is frozen because it is a hashed constant (DECISIONS.mdD1).Why
The freeze criteria are met: the wire format is pinned in the spec, the published vectors embody it, the three clients and the reference implementation pass the suite in CI, and the governance and versioning policies are in place.
scripts/check_suite.pyenforces one version string across every surface, so the flip is all-or-nothing by construction. The manifests are generator output: the reference implementation bumped its suite-version constants to0.1.0and regenerated first, andcheck_vector_drift.pyconfirms 73 files byte-identical across both repositories, so the lockstep ordering (spec, then generator, then published copy) is preserved. No vector bytes change; only the twosuite_versionlines.Conformance impact
The suite version becomes
0.1.0. No vector, verdict, tier, or failure-code changes;check_suite.pyreports 65 vectors, versions aligned.SPEC.mdandCONFORMANCE.mdchange status text and version together and stay consistent. After merge: tagv0.1.0, publish the GitHub Release (mints the Zenodo version DOI), then a follow-up adds the new version DOI toCITATION.cff.