Exact axis + version
The release must say whether it publishes the standard, toolchain or a contract package.
Menu
RELEASES & VERSIONING
OpenRGD has multiple version axes. Merge is not release.
Standard semantics, the Python toolchain and cross-component contracts mature independently. Matching numbers are not compatibility evidence, and the current main branch must not be described as a formal release merely because it is validated and public.
CITATION RECORD
MATURITYVERSION & RELEASE STATUS
LAST VERIFIED27 Sep 2026
SOURCE VERSIONVERSIONING.md + RELEASE_POLICY.md + CHANGELOG.md · snapshot afe1a831
EVIDENCE BOUNDARYCurrent repository state is not automatically a formal release; release axes are independent.
CURRENT AXES
Three public versions, three different meanings.
Standard bundle0.2.0Draft
Python toolchain0.1.1Working alpha
Agent Contracts0.1.0Candidate · non-normative
Kernel profile0.1.0Profile version, not whole-standard version
The current citation snapshot is a source snapshot, not a scoped release tag.
Snapshot afe1a831b950a4e6560f0285a0103fc4eaa343b7 is useful for reproducible citation and code inspection. A formal release requires a separate release pull request, evidence inventory and the release policy for the relevant axis.
TAG MODEL
Future releases are explicitly scoped by artifact axis.
Frozen tag prefixes
standard-vMAJOR.MINOR.PATCH
toolchain-vMAJOR.MINOR.PATCH
contracts-agent-vMAJOR.MINOR.PATCHHistorical unscoped tags v0.1.0 and v0.1.1 remain repository/toolchain lineage evidence. They do not establish the current standard-bundle version.
NEXT PROPOSED TOOLCHAIN CANDIDATE
Planned does not mean released.
Python version0.2.0rc1Proposed in policy only
Git tagtoolchain-v0.2.0-rc.1Not created by this page
RELEASE EVIDENCE
A real release carries more than a version number.
Final source commit
The exact reviewed commit is part of the release evidence.
Compatibility + migration
Semantic and consumer impact must be stated explicitly.
Integrity + artifacts
Relevant source root, artifact inventory and SHA-256 values are recorded.
Maturity labels
Bundled candidate/accepted status remains explicit.
Signing boundary
A digest proves content identity; stable trust-sensitive claims require the signing/attestation lifecycle defined by policy.
PERMANENT REFERENCE