|
| 1 | +# Bitcode Spec V40 Delta |
| 2 | + |
| 3 | +## Status |
| 4 | + |
| 5 | +- Version: `V40` |
| 6 | +- V40 state: draft opened; this delta records the planned exhaustive commercial application testing closure set |
| 7 | +- Current canonical/latest target: `V39` |
| 8 | +- Prior canonical anchor: `BITCODE_SPEC_V39.md` |
| 9 | +- Prior generated proof appendix: `BITCODE_SPEC_V39_PROVEN.md` |
| 10 | +- Generated structured artifact inventory: draft `.bitcode/v40-spec-family-report.json`, `.bitcode/v40-canonical-input-report.json`, and later V40 testing artifacts |
| 11 | +- Source parity state: V40 testing surfaces are scoped but not yet closed |
| 12 | + |
| 13 | +## Why V40 exists |
| 14 | + |
| 15 | +V39 made commercial Reading product behavior canonical. |
| 16 | +V40 exists because that behavior now needs exhaustive proof through tests: browser E2E, visual/screenshot comparisons, API contracts, pipeline integrations, conversation integrations, ledger/database/storage synchronization, unit coverage, prompt benchmark smoke, and local/staging rehearsal. |
| 17 | + |
| 18 | +## Accepted V40 decisions |
| 19 | + |
| 20 | +- V40 is a testing-focused version, not a prompt-rewriting version. |
| 21 | +- V40 must test both primitives and real commercial implementations. |
| 22 | +- V40 must make the five-step Reading flow fully browser-proven and contract-proven. |
| 23 | +- V40 must add generated artifacts for every major testing surface. |
| 24 | +- V40 must keep value-bearing production-mainnet checks opt-in until explicitly promoted. |
| 25 | +- V41 is reserved for Prompt and PromptPart excellence after V40 makes benchmark and test lanes reliable. |
| 26 | + |
| 27 | +## V40 gate plan |
| 28 | + |
| 29 | +### Gate 1: Exhaustive Testing Roadmap And Spec Opening |
| 30 | + |
| 31 | +Open the V40 spec family, roadmap, branch posture, workflow posture, checker, and V41 planning boundary. |
| 32 | + |
| 33 | +### Gate 2: Test Inventory And Coverage Matrix |
| 34 | + |
| 35 | +Inventory existing tests, missing critical surfaces, owners, commands, fixtures, and generated artifacts. |
| 36 | + |
| 37 | +### Gate 3: Unit Coverage For Packages And Primitives |
| 38 | + |
| 39 | +Close unit coverage over protocol, BTD, prompts, agents, tools, executions, pipelines, utilities, and isolated app helpers. |
| 40 | + |
| 41 | +### Gate 4: API And Route Integration Contracts |
| 42 | + |
| 43 | +Close API, UAPI, public route, MCP API, ChatGPT App, persistence, and authorization contract suites. |
| 44 | + |
| 45 | +### Gate 5: Reading Pipeline Integration Coverage |
| 46 | + |
| 47 | +Close primitive and real implementation coverage for `ReadNeedComprehensionSynthesis` and `ReadFitsFindingSynthesis`. |
| 48 | + |
| 49 | +### Gate 6: Conversation And Terminal Integration Coverage |
| 50 | + |
| 51 | +Close cross-surface tests for Conversation, Terminal handoff, Reading state, telemetry, and source-safe disclosure. |
| 52 | + |
| 53 | +### Gate 7: Browser E2E, Accessibility, Responsive, And Visual Proof |
| 54 | + |
| 55 | +Close Playwright/browser paths, visual baselines, accessibility, responsive viewports, and interaction-state matrices. |
| 56 | + |
| 57 | +### Gate 8: Ledger, Database, Storage, Wallet, And Delivery Synchronization |
| 58 | + |
| 59 | +Close synchronization and reconciliation tests for settlement, rights transfer, delivery, repair, and storage projections. |
| 60 | + |
| 61 | +### Gate 9: Local And Staging-Testnet Rehearsal Automation |
| 62 | + |
| 63 | +Close local/staging rehearsal scripts with lane-bound secrets, no tracked credentials, and reproducible operator receipts. |
| 64 | + |
| 65 | +### Gate 10: Prompt Benchmark Smoke And V41 Readiness |
| 66 | + |
| 67 | +Make prompt and PromptPart benchmark commands runnable and reportable without rewriting prompt content, then hand focused prompt evolution to V41. |
| 68 | + |
| 69 | +### Gate 11: V40 Promotion Readiness |
| 70 | + |
| 71 | +Bind all V40 artifacts, proof generation, workflows, and promotion commands into the V40 canonical promotion path. |
| 72 | + |
| 73 | +## Explicitly deferred |
| 74 | + |
| 75 | +- Prompt and PromptPart semantic rewriting, repartitioning, retitling, and excellence auditing are deferred to V41. |
| 76 | +- New commercial product features are deferred unless needed to make tests truthful. |
| 77 | +- Production-mainnet value-bearing tests remain opt-in until a later promotion mandates them. |
| 78 | + |
| 79 | +## Pre-Implementation Sequence |
| 80 | + |
| 81 | +1. Open `version/v40` and `v40/gate-1-testing-roadmap-opening`. |
| 82 | +2. Keep `BITCODE_SPEC.txt` at `V39`. |
| 83 | +3. Add the V40 spec family and Gate 1 checker. |
| 84 | +4. Update roadmap, docs, package scripts, and workflows for active V39 / draft V40. |
| 85 | +5. Validate V40 draft family and V39 active posture. |
| 86 | + |
| 87 | +## Commit-Body Direction |
| 88 | + |
| 89 | +V40 commits should name the testing surface, generated artifact, proof command, and whether the gate closes unit, integration, browser, visual, local/staging, or promotion readiness coverage. |
0 commit comments