|
3 | 3 | ## Status |
4 | 4 |
|
5 | 5 | - Version: `V45` |
6 | | -- V45 state: formal draft specification consolidated from accepted V45 notes atoms; V44 remains active canon until V45 promotion |
7 | | -- Current canonical/latest target: `V44` |
| 6 | +- V45 state: canonical promotion complete; V45 is the active knowledge commoditization canon and the V45 hand-authored plus generated canon are aligned |
| 7 | +- Current canonical/latest target: `V45` |
| 8 | +- Canonical proof-source commit: `23294cc578dcb2148a6b602c3463b3ca01f1fef1` |
8 | 9 | - Prior canonical anchor: `BITCODE_SPEC_V44.md` |
9 | 10 | - Prior generated proof appendix: `BITCODE_SPEC_V44_PROVEN.md` |
10 | | -- Generated structured artifact inventory: draft `.bitcode/v45-spec-family-report.json`, draft `.bitcode/v45-canonical-input-report.json`, V45 proof-family artifacts, `.bitcode/v45-source-safe-e2e-rehearsal.json`, `.bitcode/v45-promotion-readiness-report.json`, V45 notes atom checkers, V45 formal-spec consolidation checker, `v45-canon-promotion.yml`, and draft `BITCODE_SPEC_V45_PROVEN.md`; V44 generated artifacts remain active canonical proof until V45 promotion |
11 | | -- Source parity state: V45 protocol law is formally consolidated for later parity audit; implementation parity is not yet audited, grouped implementation gates are not yet authorized, and V44 source remains the active implementation canon |
| 11 | +- Generated structured artifact inventory: active canonical `.bitcode/v45-spec-family-report.json`, `.bitcode/v45-canonical-input-report.json`, `.bitcode/v45-canon-posture-drift-report.json`, all nine V45 proof-family artifacts, `.bitcode/v45-source-safe-e2e-rehearsal.json`, `.bitcode/v45-promotion-readiness-report.json`, V45 gate-quality and promotion workflow evidence, and `BITCODE_SPEC_V45_PROVEN.md` as the generated proof appendix for V45 promotion |
| 12 | +- Source parity state: V45 source-side AssetPack commodity lifecycle, BTD scalar-volume, BTC settlement, interface disclosure, proof readback, source-safe rehearsal, workflow, and promotion surfaces are canonicalized in the promoted V45 file family |
12 | 13 | - Notes companion: `BITCODE_SPEC_V45_NOTES.md` |
13 | 14 | - Delta companion: `BITCODE_SPEC_V45_DELTA.md` |
14 | 15 | - Parity companion: `BITCODE_SPEC_V45_PARITY_MATRIX.md` |
15 | | -- Scope: V45 draft specification for Bitcode as the world's knowledge commoditization system, consolidating AssetPack lifecycle, BTD scalar-volume, BTC settlement, interface disclosure, proof readback, and gate taxonomy law |
16 | | -- Last fully realized canonical target preserved in source: `V44` |
| 16 | +- Scope: V45 canonical system specification for knowledge commoditization across AssetPack commodity lifecycle, BTD scalar-volume and rights, BTC settlement, interface disclosure, proof readback, source-safe end-to-end rehearsal, and promotion readiness surfaces |
| 17 | +- Last fully realized canonical target preserved in source: `V45` |
17 | 18 |
|
18 | 19 | ## Version executive summary |
19 | 20 |
|
@@ -42,13 +43,12 @@ rights, and proof-backed readback is the only state advancement mechanism. |
42 | 43 |
|
43 | 44 | ## V45 source-of-truth hierarchy |
44 | 45 |
|
45 | | -`BITCODE_SPEC.txt` points to `V44`; V44 remains active promoted canon. |
| 46 | +`BITCODE_SPEC.txt` points to `V45`; V45 is the active promoted Bitcode canon. |
46 | 47 | `BITCODE_SPEC_V45.md`, `BITCODE_SPEC_V45_DELTA.md`, |
47 | | -`BITCODE_SPEC_V45_NOTES.md`, and `BITCODE_SPEC_V45_PARITY_MATRIX.md` are V45 |
48 | | -draft specification-family material. The V45 formal specification family is the |
49 | | -only authority for the next implementation parity audit, but it is not active |
50 | | -canon and cannot authorize source disclosure, settlement, rights transfer, or |
51 | | -implementation behavior until V45 promotion. |
| 48 | +`BITCODE_SPEC_V45_NOTES.md`, and `BITCODE_SPEC_V45_PARITY_MATRIX.md` are the |
| 49 | +promoted V45 specification-family material. The V45 formal specification family |
| 50 | +is active canon and authorizes implementation behavior only through the |
| 51 | +source-safe, entitlement-bound, proof-backed boundaries it states. |
52 | 52 |
|
53 | 53 | Implementation remains unversioned in source paths. Package, route, component, |
54 | 54 | test, prompt, script, telemetry, schema, API, and workflow names move in place |
|
0 commit comments