|
| 1 | +# Bitcode Spec V41 Delta |
| 2 | + |
| 3 | +## Status |
| 4 | + |
| 5 | +- Version: `V41` |
| 6 | +- V41 state: draft opened; this delta records the V40-to-V41 prompt-program opening plan |
| 7 | +- Current canonical/latest target: `V40` |
| 8 | +- Prior canonical anchor: `BITCODE_SPEC_V40.md` |
| 9 | +- Prior generated proof appendix: `BITCODE_SPEC_V40_PROVEN.md` |
| 10 | +- Generated structured artifact inventory: draft `.bitcode/v41-spec-family-report.json`, draft `.bitcode/v41-canonical-input-report.json`, planned prompt-program catalogue artifacts, planned benchmark artifacts, planned promotion-readiness artifact, and eventual `BITCODE_SPEC_V41_PROVEN.md` after V41 promotion |
| 11 | +- Source parity state: V41 source parity begins at specification and workflow posture; prompt rewrites are explicitly deferred until catalogue and benchmark gates close |
| 12 | +- Scope: V41 draft delta for Prompt and PromptPart excellence over promoted V40 |
| 13 | + |
| 14 | +## Why V41 exists |
| 15 | + |
| 16 | +V38 hardened inference architecture and V40 hardened testing and benchmark lanes. |
| 17 | +V41 uses that base to treat prompts as programs: enumerable, benchmarkable, typed, source-safe, and registry-bound. |
| 18 | + |
| 19 | +## Accepted V41 decisions |
| 20 | + |
| 21 | +- V41 is singularly focused on Prompt and PromptPart implementation quality. |
| 22 | +- Reading prompts are the priority, especially `ReadNeedComprehensionSynthesis` and `ReadFitsFindingSynthesis`. |
| 23 | +- Prompt rewrites require prior inventory, registry composition proof, interpolation proof, benchmark baselines, parsed return-type checks, and source-safe telemetry proof. |
| 24 | +- Prompt artifacts may carry ids, hashes, metrics, verdicts, and redacted summaries, but not raw protected prompt text, raw provider responses, secrets, wallet material, protected source, private settlement payloads, or unpaid AssetPack source. |
| 25 | +- V41 preserves V27 BTC/BTD law, V38 inference call-stack law, V39 Reading product law, and V40 testing law. |
| 26 | + |
| 27 | +## V41 gate plan |
| 28 | + |
| 29 | +### Gate 1: Prompt Program Roadmap And Spec Opening |
| 30 | + |
| 31 | +Open the V41 full specification family, roadmap, package script, workflow posture, documentation posture, branch convention, and checker. |
| 32 | + |
| 33 | +### Gate 2: PromptPart And Prompt Inventory Catalog |
| 34 | + |
| 35 | +Inventory every raw PromptPart and composed Prompt across Reading, Conversation, tool-definition, and interface inference surfaces. |
| 36 | + |
| 37 | +### Gate 3: Registry Composition And Interpolation Contracts |
| 38 | + |
| 39 | +Prove registry composition, prompt context interpolation, execution ancestry, tool prompt injection, and parsed return type bindings. |
| 40 | + |
| 41 | +### Gate 4: Reading Pipeline Prompt Benchmark Baselines |
| 42 | + |
| 43 | +Create source-safe baseline benchmarks for Reading prompt surfaces before rewriting them. |
| 44 | + |
| 45 | +### Gate 5: ReadNeedComprehensionSynthesis Prompt Rewrite And Return-Type Hardening |
| 46 | + |
| 47 | +Rewrite and repartition ReadNeed prompts only after evidence proves the rewrite improves exact Need comprehension and typed output reliability. |
| 48 | + |
| 49 | +### Gate 6: ReadFitsFindingSynthesis Prompt Rewrite Search And AssetPack Context Hardening |
| 50 | + |
| 51 | +Rewrite and repartition Finding Fits prompts only after evidence proves the rewrite improves Depository search, ranking, selected-fit provenance, and AssetPack context source-safely. |
| 52 | + |
| 53 | +### Gate 7: Conversation Tool And Interface Prompt Rewrite |
| 54 | + |
| 55 | +Apply the same prompt-program discipline to Conversation, tool-definition, MCP API, ChatGPT App, public API, Terminal, and other interface prompts. |
| 56 | + |
| 57 | +### Gate 8: Prompt Benchmark Report And Telemetry Integration |
| 58 | + |
| 59 | +Close post-rewrite benchmark deltas, prompt lineage, telemetry integration, and source-safe rich stream projections. |
| 60 | + |
| 61 | +### Gate 9: Promotion Readiness |
| 62 | + |
| 63 | +Bind all V41 prompt artifacts, tests, workflow checks, generated proof support, promotion commands, and active V41 / draft V42 posture. |
| 64 | + |
| 65 | +## Explicitly deferred |
| 66 | + |
| 67 | +- No prompt content is rewritten during Gate 1. |
| 68 | +- New commercial product behavior is deferred unless needed to make prompt-program tests truthful. |
| 69 | +- Production-mainnet value-bearing prompt rehearsals remain opt-in. |
| 70 | + |
| 71 | +## Pre-Implementation Sequence |
| 72 | + |
| 73 | +1. Open `version/v41` and `v41/gate-1-prompt-program-roadmap-opening`. |
| 74 | +2. Keep `BITCODE_SPEC.txt` at `V40`. |
| 75 | +3. Add the V41 spec family and Gate 1 checker. |
| 76 | +4. Update roadmap, docs, package scripts, and workflows for active V40 / draft V41. |
| 77 | +5. Validate V41 draft family and V40 active posture. |
| 78 | + |
| 79 | +## Commit-Body Direction |
| 80 | + |
| 81 | +V41 commits should name the prompt-program surface, generated artifact or checker, benchmark posture, registry/callsite scope, source-safety boundary, and tests run. |
0 commit comments