33## Status
44
55- Version: ` V30 `
6- - V30 state: future notes scaffold only
7- - Current canonical/latest target: ` V27 `
8- - Current active draft target: ` V28 `
9- - Prior canonical anchor: ` BITCODE_SPEC_V27.md `
10- - Prior generated proof appendix: ` BITCODE_SPEC_V27_PROVEN.md `
6+ - V30 state: notes-only draft opening
7+ - Current canonical/latest target: ` V29 `
8+ - Current active draft target: ` V30 `
9+ - Canonical pointer: ` BITCODE_SPEC.txt ` -> ` V29 `
10+ - Active canonical anchor: ` BITCODE_SPEC_V29.md `
11+ - Active generated proof appendix: ` BITCODE_SPEC_V29_PROVEN.md `
12+ - Prior canonical anchor: ` BITCODE_SPEC_V29.md `
13+ - Prior generated proof appendix: ` BITCODE_SPEC_V29_PROVEN.md `
1114- Generated structured artifact inventory: none for V30 yet
12- - Source parity state: not opened ; V30 source parity begins only after V30 draft opening
15+ - Source parity state: notes-only draft opening ; V30 source parity begins only after V30 first-gate work
1316- Scope: future notes for Protocol/BTD hardening after V28 commercial Protocol/Terminal MVP and V29 deeper Terminal work. Exchange is deferred beyond V35.
1417
1518This NOTES file does not promote V30 and does not open V30 implementation.
16- It preserves roadmap intent so V28 can remain focused on commercial Protocol/Terminal MVP QA, bugfixing, audit, and hardening.
19+ It preserves roadmap intent so V30 first-gate work can open from promoted V29 without rediscovering deferred Protocol/BTD hardening pressure .
1720
18- ## Notes companion rule
21+ ## Notes-only draft rule
1922
20- This file is planning memory only.
21- Requirements become binding only when V30 is explicitly opened as the draft-target SPEC family.
23+ This file is planning memory only and is not first-gate implementation .
24+ Requirements become binding only when V30 is explicitly opened as a full draft-target SPEC family.
2225
2326## Concise current-system reading
2427
25- V27 is active canon.
26- V28 is current draft target and owns commercial Protocol implementation, Terminal MVP QA, MCP API/ChatGPT App MVP, BTD/testnet/ledgerization, and demonstration-to-commercial boundary cleanup.
27- V29 is expected to deepen Terminal workflows.
28+ V29 is active canon.
2829V30 is expected to harden Protocol/BTD surfaces after V28/V29 reveal implementation pressure.
2930Exchange is not V30 work.
3031
31- ## Intended V30 focus
32+ ## Deferred from V29
33+
34+ V29 canonically closes deeper Terminal transaction depth, local/staging promotion readiness, and promotion automation.
35+ V30 inherits deferred hardening pressure around Bitcoin fee boundaries, GitHub delivery evidence, compute/runtime capability truth, storage/readback posture, and build/process proof surfaces.
36+
37+ ## Candidate V30 workstreams
3238
3339V30 owns Protocol/BTD hardening:
3440
@@ -40,13 +46,8 @@ V30 owns Protocol/BTD hardening:
4046- source-to-shares proof cleanup revealed by V28/V29;
4147- Protocol/BTD-specific tests, proofs, and telemetry hooks needed before Exchange returns beyond V35.
4248
43- ## Boundaries
49+ ## Non-goals during V30 opening
4450
4551V30 must not redefine ` $BTD ` supply, BTC fee separation, AssetPack range identity, owner-read/licensed-read law, measureminting, or ancestry.
4652V30 must not absorb V31 Auxillaries expansion, V32 provation/testing depth, V33 interface depth, V34 deployment depth, or V35 telemetry/documenting depth except for narrow Protocol/BTD-owned hooks.
4753V30 must not absorb Exchange or website Conversations; those return beyond V35.
48-
49- ## Return To V28
50-
51- Do not start V30 implementation during V28.
52- Use this scaffold only to keep V28 focused on commercial Protocol/Terminal MVP QA and hardening.
0 commit comments