|
| 1 | +# Bitcode Spec V42 Notes |
| 2 | + |
| 3 | +## Status |
| 4 | + |
| 5 | +- Version: `V42` |
| 6 | +- V42 state: draft opened; notes track reliable MVP experience planning over active V41 |
| 7 | +- Current canonical/latest target: `V41` |
| 8 | +- Prior canonical anchor: `BITCODE_SPEC_V41.md` |
| 9 | +- Prior generated proof appendix: `BITCODE_SPEC_V41_PROVEN.md` |
| 10 | +- Generated structured artifact inventory: draft `.bitcode/v42-spec-family-report.json`, `.bitcode/v42-canonical-input-report.json`, `.bitcode/v42-canon-posture-drift-report.json`, and later V42 gate artifacts |
| 11 | +- Source parity state: notes are source-facing planning until later gates implement and prove product behavior |
| 12 | +- Scope: V42 notes for reliable MVP product experience |
| 13 | + |
| 14 | +## Notes companion rule |
| 15 | + |
| 16 | +This notes companion records the working V42 product plan and simplified reading. |
| 17 | +It does not override `BITCODE_SPEC_V42.md`. |
| 18 | +Product behavior changes remain blocked until the relevant V42 gate admits and verifies them. |
| 19 | + |
| 20 | +## V42 Gate 1 opening note |
| 21 | + |
| 22 | +Gate 1 is intentionally specification, documentation, workflow, and checker posture only. |
| 23 | +It opens the reliable MVP experience version after V41 prompt-program promotion and prepares later gates to implement Depositing, Reading, settlement, delivery, and demonstration behavior without ad hoc scope drift. |
| 24 | + |
| 25 | +## Depositing shortest-path note |
| 26 | + |
| 27 | +The V42 Depositing path should minimize the journey from source material to Depository admission proof. |
| 28 | +The user needs to know that the source is admitted, searchable for future Need-Fit work, and eligible for BTC compensation if it contributes to a synthesized AssetPack. |
| 29 | +The UX can stay simple, but expandable details must show source authority, admission proof, storage projection, search-document posture, compensation route, and repair state. |
| 30 | + |
| 31 | +## Reading shortest-path note |
| 32 | + |
| 33 | +The V42 Reading path should be a five-step enterprise flow: |
| 34 | + |
| 35 | +1. request read; |
| 36 | +2. review synthesized Need; |
| 37 | +3. request Finding Fits; |
| 38 | +4. review source-safe AssetPack measurements and preview metadata; |
| 39 | +5. buy, settle, transfer rights, and receive repository delivery. |
| 40 | + |
| 41 | +The default UI should be guided and low-detail. |
| 42 | +The rich execution log, proof roots, telemetry rows, and ledger/storage details remain available on expansion. |
| 43 | + |
| 44 | +## AssetPack source-safety note |
| 45 | + |
| 46 | +V42 must make the preview valuable without leaking the source-bearing AssetPack before settlement. |
| 47 | +Readers may see measurements, fit confidence, quote posture, selected-fit provenance summaries, proof roots, and source-safe explanations. |
| 48 | +They may not see protected source, raw provider responses, protected prompts, private settlement payloads, wallet private material, or unpaid AssetPack source before BTC settlement and BTD rights transfer. |
| 49 | + |
| 50 | +## AI-reading demonstration note |
| 51 | + |
| 52 | +The standalone demonstration should prove why Bitcode matters for AI-dominant Reading. |
| 53 | +A deposited proprietary or otherwise non-public technical intelligence source should contribute to an AssetPack that measurably improves an AI system's training, prompt/context, or evaluation result beyond what a public-data-only baseline can do. |
| 54 | +The demonstration must remain minimal, local, deterministic where feasible, and self-contained inside `protocol-demonstration/`. |
| 55 | + |
| 56 | +## V43+ agentic depositing roadmap note |
| 57 | + |
| 58 | +V43 or a later explicitly opened version should evolve the deposit side into an agentic AssetPack option experience for enterprises. |
| 59 | +Repository-installed Bitcode Agents should compare a connected enterprise codebase, the current Bitcode Depository, and Reading activity to propose deposit AssetPack options. |
| 60 | +Those options should be source-safe, sub-critical, likely positive ROI, and approve/rejectable before Depository admission. |
| 61 | +That later version should split `/terminal` into `/read` and `/deposit`, and rename `/exchange` to `/packs` across routes, code naming, docs, and operator vocabulary. |
| 62 | + |
| 63 | +## Concise current-system reading |
| 64 | + |
| 65 | +Bitcode is active at V41. |
| 66 | +V42 drafts the next canon: the reliable MVP experience for enterprise Depositing and Reading. |
| 67 | +The central product promise is that a user can deposit source, request a read, review a synthesized Need, find fitting Depository sources, preview a source-safe AssetPack, pay in BTC/BTD settlement terms, receive rights, and get repository delivery. |
| 68 | + |
| 69 | +## Simplified-spec reading rule |
| 70 | + |
| 71 | +Read V42 as shortest credible paths over existing protocol law. |
| 72 | +If a product step cannot be routed, stored, replayed, telemetered, proven, and source-safely explained, it is not V42-ready. |
| 73 | + |
| 74 | +## Non-goals during V42 opening |
| 75 | + |
| 76 | +- Do not implement product behavior in Gate 1. |
| 77 | +- Do not split `/terminal` or rename `/exchange`. |
| 78 | +- Do not expose protected source or unpaid AssetPack source. |
| 79 | +- Do not bypass Need review before Finding Fits. |
| 80 | +- Do not claim settlement, BTD rights transfer, or repository delivery without synchronized ledger/database/storage proof. |
0 commit comments