v9 Status
Historical v9 semantic-state baseline: 9.0.0-draft.1. The current Framework proposed standard in the supplied snapshot is v10 10.0.0-draft.3; see Status-v10.
The v9 architecture is implemented and testable: normative draft prose, schemas, TCK vectors, reference JavaScript behavior and an independent Python KristalDiag qualification surface exist.
Why draft?
Final status means the machine contracts and commitment profiles are frozen enough that independent implementations can rely on them permanently.
The main freeze-sensitive areas are:
- Logical Commitment projection/ordering/exclusions;
- semantic identity continuity/migration;
- protected/private commitment profiles;
- exact Standard-versus-operational boundary for activation/concurrency.
Independent qualification
KristalDiag v9 recomputes the commitment profiles independently in Python and runs negative/invariance and polymorphism workloads.
The transition toward RC/final is therefore a qualification/freeze process rather than a plan to replace the v9 architecture.
See KristalDiag-v9, Conformance-v9 and Contract-Evolution-v9.