|
| 1 | +# Bitcode Spec V48 Notes |
| 2 | + |
| 3 | +## Status |
| 4 | + |
| 5 | +- Version: `V48` |
| 6 | +- Canonical pointer: `BITCODE_SPEC.txt` -> `V47` |
| 7 | +- Active canonical anchor: `BITCODE_SPEC_V47.md` |
| 8 | +- Active generated proof appendix: `BITCODE_SPEC_V47_PROVEN.md` |
| 9 | +- Current canonical/latest target: `V47` |
| 10 | +- Prior canonical anchor: `BITCODE_SPEC_V46.md` |
| 11 | +- Prior generated proof appendix: `BITCODE_SPEC_V46_PROVEN.md` |
| 12 | +- V48 state: notes-only draft opening |
| 13 | +- Scope: V48 starts as the interactive local experiential QA target over promoted V47 commercial website testnet launch canon. |
| 14 | + |
| 15 | +## Notes-only draft rule |
| 16 | + |
| 17 | +These notes make the V48 draft target visible to strict spec-quality checks |
| 18 | +after V47 promotion. They are not first-gate implementation authority, not a |
| 19 | +full V48 specification family, and not permission to bypass the V47 canon. V48 |
| 20 | +work must continue by exercising the live commercial testnet experience |
| 21 | +interactively, recording accepted findings, creating an explicit parity |
| 22 | +matrix, and then opening scoped gate branches only after the QA-driven |
| 23 | +specification intent is clear. |
| 24 | + |
| 25 | +## Deferred from V47 |
| 26 | + |
| 27 | +V47 promoted commercial website testnet launch readiness. It launch-froze |
| 28 | +`/deposit`, `/read`, `/packs`, and Auxillaries, made measurement law and the |
| 29 | +IP seller/buyer state machines exact, completed the depositor and reader |
| 30 | +websites, the packs/Auxillaries commercial dashboard, browser-proven E2E IP |
| 31 | +selling and buying, landing/public launch messaging, the staging-testnet |
| 32 | +deployment rehearsal, and promotion readiness — all over the preserved |
| 33 | +Bitcoin/BTC settlement language, BTD scalar-volume and rights language, |
| 34 | +GitHub delivery boundaries, compute constraints, storage boundaries, and |
| 35 | +build/process validation carried from the promoted V46 comprehension canon. |
| 36 | + |
| 37 | +V48 begins from the remaining question: what does the first live commercial |
| 38 | +(testnet) experience still need before real users can walk every core step |
| 39 | +without friction. The opening posture is intentionally experiential: run the |
| 40 | +deployed staging-testnet system end to end, step by step, and fix what breaks. |
| 41 | + |
| 42 | +## Candidate V48 workstreams |
| 43 | + |
| 44 | +- Environment preparation: staging Supabase database readiness, wallet-fauceted |
| 45 | + testnet BTC, local telemetry expectations, and a step-by-step debugging |
| 46 | + experience that validates each core user step. |
| 47 | +- Identity and authentication: sign up/in, and Auxillaries readiness for |
| 48 | + connecting GitHub, wallet(s), and other external surfaces. |
| 49 | +- Depositing: connecting knowledge, requesting AssetPack syntheses to review, |
| 50 | + reviewing, and depositing. |
| 51 | +- Reading: connecting knowledge, requesting a Read, reviewing the synthesized |
| 52 | + Need, reviewing potential Fits, and buying Fit(s). |
| 53 | +- Ledgerized journaling: replayability, auditability, `/packs` page UX/UI, and |
| 54 | + the personal (Auxillaries) history of work. |
| 55 | + |
| 56 | +## Non-goals during V48 opening |
| 57 | + |
| 58 | +- Do not implement V48 product behavior from this notes-only opening. |
| 59 | +- Do not rewrite V47 promoted canon except through an explicit addendum. |
| 60 | +- Do not expose raw source, unpaid AssetPack source, secrets, wallet private |
| 61 | + material, private settlement payloads, raw prompts, or raw provider responses. |
| 62 | +- Do not collapse estimate, quote, observed payment, final settlement, |
| 63 | + contributor allocation, delivery, compensation, and repair states. |
| 64 | +- Do not launch value-bearing mainnet settlement in V48 opening work. |
| 65 | +- Do not treat notes-only V48 material as stronger than active V47 protocol law. |
0 commit comments