Versioning
|
CYCLE Calibration position — Active Development This page is a conceptual instrument under Permanent Beta. It declares a real calibration position, not a finished product waiting to ship. Checking continues; an edit is only required when evidence demands it. Stage: Seed to Fruit. Feedback welcome — especially clarity, failure modes, and calibration gaps. Use discussion or Contribute. |
Meta
Versioning
| Type | Meta & Framework |
|---|---|
| Functional Layer | Governance Standard |
| Application Layer | Framework |
| Category | Meta & Framework |
| Version | 0.2 |
| Maturity | Developing |
| Last Calibration | 2026-07-29 |
| Status | Permanent Beta |
| Description | This page defines the versioning and instrument grading standards used across The Sovereign Games to maintain traceability, clarity, and honest communication about the maturity and reliability of every module and page. |
Menu
Core Principles
- Reality gets final vote
- See the Game. Refuse the Game. Build Better.
- Permanent Beta
Navigation
Related
Versioning
This page establishes how The Sovereign Games tracks changes and communicates the reliability of its conceptual instruments.
Two-Axis Model
- Document Version — Tracks revisions ("Which revision am I looking at?")
- instrument_grade — Communicates current calibration trustworthiness ("How reliable is this instrument right now?")
Both are recorded in the
template on every page.
Versioning Scheme
- 0.x → Early development (frequent changes expected)
- 1.x → Stable working version
- 2.0+ → Major revision
instrument_grade Levels
- Experimental — Very early, high uncertainty, frequent changes
- Development — Actively being refined, moderate stability
- Confirmed — Self-assessed + reviewed by at least one other calibrator
- Field Validated — Tested in real-world use with supporting evidence
- Reference Standard Candidate — High confidence, suitable for broad reliance
These levels are implemented via the `instrument_grade` field in the Template:Admin Page Status.
Changelog Practice
Every page should maintain a short Calibration History section (usually in its Calibration Log) that records meaningful changes as calibration events.
Example:
- 0.4 (2026-06-12) — Initial draft
- 0.7 (2026-06-28) — Added boundary conditions
- 1.0 (2026-07-09) — First Confirmed Rating after external review
See the Game. Refuse the Game. Build Better.