|
| 1 | +# Bitcode Spec V46 Delta |
| 2 | + |
| 3 | +## Status |
| 4 | + |
| 5 | +- Version: `V46` |
| 6 | +- V46 state: draft opening; V46 is the active draft target over promoted V45 canon |
| 7 | +- Current canonical/latest target: `V45` |
| 8 | +- Prior canonical anchor: `BITCODE_SPEC_V45.md` |
| 9 | +- Prior generated proof appendix: `BITCODE_SPEC_V45_PROVEN.md` |
| 10 | +- Generated structured artifact inventory: draft `.bitcode/v46-spec-family-report.json` and `.bitcode/v46-canonical-input-report.json`; later V46 gates must authorize proof-family, rehearsal, promotion-readiness, and generated proof appendix artifacts before they become required V46 evidence |
| 11 | +- Source parity state: V46 source parity has not been audited; Gate 1 opens the draft-target roadmap and validation boundary only |
| 12 | +- Notes companion: `BITCODE_SPEC_V46_NOTES.md` |
| 13 | +- Spec companion: `BITCODE_SPEC_V46.md` |
| 14 | +- Parity companion: `BITCODE_SPEC_V46_PARITY_MATRIX.md` |
| 15 | +- Scope: V46 draft delta for commercial protocol comprehension, public/operator explanation, source-safe interface claims, and proof-readable launch posture over promoted V45 knowledge commoditization law |
| 16 | +- Last fully realized canonical target preserved in source: `V45` |
| 17 | + |
| 18 | +## Why V46 exists |
| 19 | + |
| 20 | +V45 made Bitcode's knowledge commoditization law explicit: AssetPack is the |
| 21 | +commodity, BTD is Need-relative weighted scalar knowledge-volume whose settled |
| 22 | +form carries rights, BTC is settlement money, source-to-shares routes |
| 23 | +contributor compensation, and proof-backed readback advances state. V46 exists |
| 24 | +to make that law commercially legible across public, operator, product, |
| 25 | +machine, and conversational surfaces without weakening source-safety or |
| 26 | +overstating live value-bearing posture. |
| 27 | + |
| 28 | +## Accepted V46 decisions |
| 29 | + |
| 30 | +- V45 remains active canon while V46 is drafted. |
| 31 | +- V46 opens as a specification-first version; Gate 1 is roadmap/spec-family |
| 32 | + opening only. |
| 33 | +- V46 focuses on external protocol comprehension and launch-facing claim |
| 34 | + readiness before it authorizes implementation changes. |
| 35 | +- Public docs, landing copy, `/packs`, `/read`, `/deposit`, API/MCP, ChatGPT |
| 36 | + App, and Bitcode Chat must explain the same protocol law with source-safe |
| 37 | + boundaries. |
| 38 | +- Investor or pitch material may inform wording, but it is not protocol law |
| 39 | + unless reconciled into the formal V46 specification family. |
| 40 | +- All V46 work must preserve V45's source-safe preview, BTC finality before |
| 41 | + source unlock, BTD rights, proof readback, repair, and value-bearing mainnet |
| 42 | + blocks. |
| 43 | + |
| 44 | +## Explicitly deferred |
| 45 | + |
| 46 | +- V46 does not replace V45 until a later promotion workflow validates and |
| 47 | + advances `BITCODE_SPEC.txt`. |
| 48 | +- Gate 1 does not authorize runtime behavior, schema changes, route changes, |
| 49 | + settlement behavior, proof-family artifacts, source-safe rehearsal artifacts, |
| 50 | + or promotion-readiness artifacts. |
| 51 | +- Value-bearing mainnet operation remains deferred. |
| 52 | +- Generated V46 proof appendix material remains future work until a proof or |
| 53 | + promotion gate makes it current. |
| 54 | + |
| 55 | +## Accepted Pre-Implementation Sequence |
| 56 | + |
| 57 | +1. Open the V46 draft family over active V45 and validate draft posture. |
| 58 | +2. Specify commercial protocol comprehension atoms in small gates. |
| 59 | +3. Consolidate accepted atoms into the formal V46 specification family. |
| 60 | +4. Audit implementation parity from the formal V46 family. |
| 61 | +5. Group implementation, proof, interface, rehearsal, and documentation work |
| 62 | + by accepted parity gaps. |
| 63 | +6. Close promotion readiness only after all scoped gates are green. |
| 64 | +7. Promote V46 only through the maintained promotion workflow. |
| 65 | + |
| 66 | +## Gate 1: V46 Commercial Protocol Comprehension Roadmap Opening |
| 67 | + |
| 68 | +Gate 1 closes when the V46 spec family exists as draft material over active |
| 69 | +V45, the roadmap names the V46 focus and tentative gates, the branch/check |
| 70 | +contract is present, CI knows how to validate active V45 plus draft V46, and no |
| 71 | +V46 file claims promoted authority. |
| 72 | + |
| 73 | +## Commit-Body Direction |
| 74 | + |
| 75 | +V46 commit bodies should name the gate class, protocol law or interface claim |
| 76 | +being clarified, validation command, source-safety posture, and whether the |
| 77 | +change is specification-only, parity-only, proof-only, interface-only, |
| 78 | +implementation, rehearsal, or promotion work. |
0 commit comments