|
| 1 | +# Bitcode Spec V45 Notes |
| 2 | + |
| 3 | +## Status |
| 4 | + |
| 5 | +- Version: `V45` |
| 6 | +- Canonical pointer: `BITCODE_SPEC.txt` -> `V44` |
| 7 | +- Active canonical anchor: `BITCODE_SPEC_V44.md` |
| 8 | +- Active generated proof appendix: `BITCODE_SPEC_V44_PROVEN.md` |
| 9 | +- V45 state: notes-only draft opening |
| 10 | +- Scope: discussion-prep notes for the next Bitcode canon candidate after V44 scaled engineering economy promotion |
| 11 | + |
| 12 | +## Notes-only draft rule |
| 13 | + |
| 14 | +These notes are not first-gate implementation authority. They keep the V45 draft |
| 15 | +target visible to strict spec-quality validation while V44 remains the active |
| 16 | +canon and while V45 intent is discussed before any gate work begins. |
| 17 | + |
| 18 | +## Deferred from V44 |
| 19 | + |
| 20 | +V44 promotes the scaled engineering economy: `/packs` as portfolio and market |
| 21 | +intelligence, `/read` as budgeted BTC procurement of source-bearing |
| 22 | +AssetPacks, `/deposit` as supply and earning visibility, and organization |
| 23 | +policy over wallet authority, spend limits, source criticality, and approval |
| 24 | +thresholds. |
| 25 | + |
| 26 | +V45 should begin by discussing Bitcode as the world's knowledge |
| 27 | +commoditization system. The discussion should audit whether the canonical |
| 28 | +protocol fully specifies the commercial experience of depositing and reading |
| 29 | +packs, BTC source-of-truth settlement, BTD measuring/mining/minting, rights |
| 30 | +transfer, proof/ledger observability, API/MCP access, GitHub delivery, |
| 31 | +ChatGPT App surfaces, Bitcode Chat conversation overlays, public docs, |
| 32 | +landing-page claims, compute constraints, storage boundaries, and |
| 33 | +build/process validation. |
| 34 | + |
| 35 | +## Candidate V45 workstreams |
| 36 | + |
| 37 | +- Protocol completeness: audit the V44 canon for AssetPack synthesis, BTD |
| 38 | + measuring/mining/minting, BTC settlement, proof roots, ledgerized |
| 39 | + journaling, and source-safe disclosure boundaries. |
| 40 | +- Product comprehension: refine how `/packs`, `/read`, and `/deposit` explain |
| 41 | + the exchange without in-app essays while preserving expandable proof, |
| 42 | + telemetry, and economic detail. |
| 43 | +- Interface system: align website routes, ChatGPT App, Bitcode Chat |
| 44 | + conversation overlay, API/MCP entrypoints, public docs, and landing page as |
| 45 | + coherent windows into the same protocol. |
| 46 | +- Operational proof: preserve V44 workflow reliability while identifying the |
| 47 | + next proof, test, and replay obligations needed for the commercial system. |
| 48 | + |
| 49 | +## Non-goals during V45 opening |
| 50 | + |
| 51 | +- Do not implement V45 gate behavior before the V45 intent discussion is |
| 52 | + completed. |
| 53 | +- Do not rename V44 canon surfaces while the active canonical pointer remains |
| 54 | + V44. |
| 55 | +- Do not weaken Bitcoin, BTD, GitHub, compute, storage, build/process, |
| 56 | + proof, or source-safety boundaries to simplify the opening notes. |
0 commit comments