Major.minor is enough.
The Core version changes only when the accepted Human Capital .+ model changes. Perspectives stay live and do not carry their own version numbers.
There is no finish line at 1.9.
1.8 → 1.9 → 1.10 → 1.11 → …
A minor version is an index, not a decimal fraction. We never promote to 2.0 because we ran out of digits. A major release happens only when the model deserves one.
Major should mean major.
A move from 1.x to 2.0 means a defining assumption or architecture changed: ownership, the economic relationship, a fundamental right, or another element that changes the identity of the model rather than improving it.
There is no quota. Core 1 may have two minor releases or twenty-seven. We do not optimize the count.
Perspectives are live thinking captured at Core releases.
We can revise, expand, challenge or add Perspectives without creating a version number. When a new Core is published, it includes a frozen copy of the Perspective set as it exists at that moment.
Discovery now. Core release later.
A working session may update a live Perspective immediately or surface a possible Core change. It does not publish a new Core version in the same session in which that Core change is first discovered.
Cooling-off rule: no Core release in the same working session in which the change first appears. The point is reflection, not bureaucracy.
Useful signal, not a score.
A long 1.x history may later show that the fundamental model survived many rounds of refinement. A short path to 2.0 may show that an important discovery changed the foundations quickly. 1.17 is not automatically more mature than 1.6.
Who decides?
At this stage, “we” means the human project author and ChatGPT developing Human Capital .+ collaboratively. There is no hidden committee, standards body, approval ladder or fictional governance process behind the version number.