V46 promotion: open V47 notes posture

Add the V47 notes-only draft opening after promoted V46, refresh the roadmap posture, align canonical-input artifact expectations, and make the V46 local-interface rehearsal predicate tolerant of the promoted V46/V47-opening state.

Author: geraldarthurdavis

.bitcode/v46-local-interface-comprehension-rehearsal.json

@@ -5,7 +5,7 @@
   "currentTarget": "V45",
   "sourceSafetyVerdict": "source-safe-local-interface-comprehension-rehearsal",
   "generatedAt": "deterministic",
-  "artifactRoot": "v46-local-interface-comprehension-rehearsal:942eb498085ab1a322c4e877",
+  "artifactRoot": "v46-local-interface-comprehension-rehearsal:9e374e9ee12476c0176e0e0e",
   "rehearsalStatus": "completed_source_safe_local",
   "passed": true,
   "surfaceIds": [
@@ -705,7 +705,7 @@
       "artifactId": "v46-public-operator-claim-boundaries",
       "sourcePath": ".bitcode/v46-public-operator-claim-boundaries.json",
       "passed": true,
-      "sourceRoot": ".bitcode/v46-public-operator-claim-boundaries.json:24ea766927437c135a0e5d90"
+      "sourceRoot": ".bitcode/v46-public-operator-claim-boundaries.json:352e9021ffbe43d650923b98"
     },
     {
       "artifactId": "v46-product-route-comprehension-readback",
@@ -799,20 +799,20 @@
     "delta": "BITCODE_SPEC_V46_DELTA.md:a16a16db40d4eeae612a0657",
     "notes": "BITCODE_SPEC_V46_NOTES.md:cca70aca3566132e7026351c",
     "parity": "BITCODE_SPEC_V46_PARITY_MATRIX.md:91b47eeaa106639d2d21856b",
-    "roadmap": "SPECIFICATIONS_ROADMAP.md:64b11cb963635e16fd70bf48",
+    "roadmap": "SPECIFICATIONS_ROADMAP.md:90a3988a2651878e43f96c65",
     "readme": "README.md:d28ec731634e03953d8adfe6",
     "protocolReadme": "packages/protocol/README.md:f5b175049f4f4e8df179e184",
     "packageJson": "package.json:b79014968c556bc1b43ab341",
     "packageIndex": "packages/protocol/src/index.js:1f16ea428bd71351a1292cb6",
     "packageTypes": "packages/protocol/src/index.d.ts:278dfc652c621533b5e86f4d",
-    "packageSource": "packages/protocol/src/canonical/v46-local-interface-comprehension-rehearsal.js:5acdbe0be5d52cd18c5e4678",
+    "packageSource": "packages/protocol/src/canonical/v46-local-interface-comprehension-rehearsal.js:553cbdb03542959151ef8fce",
     "packageTest": "packages/protocol/test/v46-local-interface-comprehension-rehearsal.test.js:5b6ad282088791ea76ec2bbf",
     "generator": "scripts/generate-v46-local-interface-comprehension-rehearsal.mjs:d6a9dadb6f8ee51de50a529f",
     "checker": "scripts/check-v46-gate7-local-interface-comprehension-rehearsal.mjs:beb49c72404e73e730640a72",
     "gateWorkflow": ".github/workflows/bitcode-gate-quality.yml:e5de1dddfaeeb0ee525b0c0f",
     "canonWorkflow": ".github/workflows/bitcode-canon-quality.yml:43cc4ded2bd9757dda9091dc",
     "v46ProtocolArtifact": ".bitcode/v46-protocol-comprehension-object-model.json:b09508f0d7841284effb0e01",
-    "v46PublicArtifact": ".bitcode/v46-public-operator-claim-boundaries.json:24ea766927437c135a0e5d90",
+    "v46PublicArtifact": ".bitcode/v46-public-operator-claim-boundaries.json:352e9021ffbe43d650923b98",
     "v46ProductArtifact": ".bitcode/v46-product-route-comprehension-readback.json:c5d1d887915cb920288b18a8",
     "v46InterfaceArtifact": ".bitcode/v46-interface-claim-contracts.json:85379590a5c5e719d0cc1ed1",
     "v46ProofArtifact": ".bitcode/v46-proof-readback-operator-explanation.json:5fb82dae1fac3711939dcd89",

BITCODE_SPEC_V47_NOTES.md

@@ -0,0 +1,59 @@
+# Bitcode Spec V47 Notes
+
+## Status
+
+- Version: `V47`
+- Canonical pointer: `BITCODE_SPEC.txt` -> `V46`
+- Active canonical anchor: `BITCODE_SPEC_V46.md`
+- Active generated proof appendix: `BITCODE_SPEC_V46_PROVEN.md`
+- Current canonical/latest target: `V46`
+- Prior canonical anchor: `BITCODE_SPEC_V45.md`
+- Prior generated proof appendix: `BITCODE_SPEC_V45_PROVEN.md`
+- V47 state: notes-only draft opening
+- Scope: V47 starts as a specification-workshopping target over promoted V46 protocol comprehension canon.
+
+## Notes-only draft rule
+
+These notes make the V47 draft target visible to strict spec-quality checks after
+V46 promotion. They are not first-gate implementation authority, not a full V47
+specification family, and not permission to bypass the V46 canon. V47 work must
+continue by refining specification atoms, creating an explicit parity matrix,
+and then opening scoped gate branches only after the new specification intent is
+clear.
+
+## Deferred from V46
+
+V46 promoted protocol comprehension and launch-facing claim readiness. It made
+Bitcode explainable as a source-safe knowledge commoditization protocol across
+`/packs`, `/read`, `/deposit`, public docs, operator readback, API/MCP,
+ChatGPT App, Bitcode Chat, proof roots, repair states, Bitcoin/BTC settlement
+language, BTD scalar-volume and rights language, GitHub delivery boundaries, compute
+constraints, storage boundaries, and build/process validation.
+
+V47 begins from the remaining question: which protocol atoms need further
+precision before the next implementation parity pass. The opening posture is
+intentionally small so V47 can be workshopped from the promoted canon rather
+than inherited from stale notes.
+
+## Candidate V47 workstreams
+
+- Protocol atom audit: inspect the promoted V46 law in small pieces and classify
+  each atom as precise, vague, contradictory, missing, or implementation-ready.
+- Parity matrix preparation: convert accepted V47 specification changes into a
+  source-to-proof matrix before implementation gates begin.
+- Product claim discipline: keep public, operator, interface, and proof
+  language aligned with source-safe AssetPack, BTD, BTC, rights, settlement,
+  delivery, repair, and compensation law.
+- Commercial readiness proofs: identify the tests, generated artifacts,
+  workflows, local rehearsals, and staging-testnet evidence needed for any V47
+  implementation gates.
+
+## Non-goals during V47 opening
+
+- Do not implement V47 product behavior from this notes-only opening.
+- Do not rewrite V46 promoted canon except through an explicit addendum.
+- Do not expose raw source, unpaid AssetPack source, secrets, wallet private
+  material, private settlement payloads, raw prompts, or raw provider responses.
+- Do not collapse estimate, quote, observed payment, final settlement,
+  contributor allocation, delivery, compensation, and repair states.
+- Do not treat notes-only V47 material as stronger than active V46 protocol law.

SPECIFICATIONS_ROADMAP.md

@@ -2,12 +2,12 @@
 
 ## Status
 
-- Current active canonical pointer: `BITCODE_SPEC.txt` -> `V45`
-- Current active canon: `BITCODE_SPEC_V45.md`
-- Current draft target: `BITCODE_SPEC_V46.md`
-- Current working gate: V46 Gate 8 Promotion Readiness And Canonical Promotion.
-- Next queued work after V46 Gate 8: V46 canonical promotion into `main`, then V47 opening after the promoted pointer is current.
-- Latest closed gate: V46 Gate 7 Local Interface Comprehension Rehearsal, which added `V46LocalInterfaceComprehensionRehearsal`, `.bitcode/v46-local-interface-comprehension-rehearsal.json`, local docs/landing, `/packs`, `/read`, `/deposit`, API/MCP, ChatGPT App, Bitcode Chat, proof telemetry, repair readback rows, prior V46 artifact pass checks, package exports, focused tests, workflow wiring, and `check:v46-gate7`.
+- Current active canonical pointer: `BITCODE_SPEC.txt` -> `V46`
+- Current active canon: `BITCODE_SPEC_V46.md`
+- Current draft target: `BITCODE_SPEC_V47_NOTES.md` notes-only opening
+- Current working gate: V47 opening preparation after V46 canonical promotion.
+- Next queued work after V46 promotion: workshop V47 protocol atoms from promoted V46, then create the V47 parity matrix and scoped gate branches.
+- Latest closed gate: V46 Gate 8 Promotion Readiness And Canonical Promotion, which added `V46PromotionReadinessReport`, `.bitcode/v46-promotion-readiness-report.json`, `BITCODE_SPEC_V46_PROVEN.md`, V46 promotion workflow support, promotion-script support, promoted V46 / draft V47 runtime posture, source-safe promotion metadata, package exports, focused tests, workflow wiring, `check:v46-gate8`, and the standalone `BITCODE_SPEC.txt` pointer promotion to V46.
 - V45 Gate 19 closure anchor: promoted V45 spec-family checks, canonical-input checks, canon-posture drift checks, promoted-stale-posture tests, generated artifact freshness checks, `check:v45-gate19`, and diff hygiene passed before merge to `main`.
 - V46 Gate 1 closure target: open the V46 draft family over active V45, name commercial protocol comprehension as the V46 focus, list provisional V46 gates, expose `check:v46-gate1`, and wire CI to validate active V45 plus draft V46 without claiming V46 promotion.
 - V46 Gate 1 closure anchor: Gate 1 is closed when V46 SPEC, DELTA, NOTES, and PARITY files validate in draft mode, this roadmap lists V46 as active draft target, V45 remains the active pointer, CI runs draft V46 checks when V46 files exist, `check:v46-gate1` passes, and the gate branch is committed, pushed, and pull-requested into `version/v46`.
@@ -156,9 +156,9 @@ They are referenced here for specification history only; active implementation w
 ## Source Families
 
 - Legacy ENGI specifications: `_legacy/ENGI_SPEC_V1.md` through `_legacy/ENGI_SPEC_V25.md`, with companion `NOTES`, `DELTA`, `PARITY_MATRIX`, `SYSTEM_PARITY_MATRIX`, `PROVEN`, and audit files where present.
-- Active Bitcode specifications: `BITCODE_SPEC_V45.md`, with companion `DELTA`, `NOTES`, `PARITY_MATRIX`, and `PROVEN` files.
-- Promoted Bitcode history: `BITCODE_SPEC_V26.md` through `BITCODE_SPEC_V44.md`, with companion `DELTA`, `NOTES`, `PARITY_MATRIX`, and `PROVEN` files.
-- Draft and future Bitcode specifications: V46 opens next over promoted V45. Planned V46+ work follows the active roadmap and any accepted notes created after V45 promotion.
+- Active Bitcode specifications: `BITCODE_SPEC_V46.md`, with companion `DELTA`, `NOTES`, `PARITY_MATRIX`, and `PROVEN` files.
+- Promoted Bitcode history: `BITCODE_SPEC_V26.md` through `BITCODE_SPEC_V45.md`, with companion `DELTA`, `NOTES`, `PARITY_MATRIX`, and `PROVEN` files.
+- Draft and future Bitcode specifications: V47 opens next over promoted V46 as `BITCODE_SPEC_V47_NOTES.md` until a full V47 specification family is intentionally drafted. Planned V47+ work follows the active roadmap and any accepted notes created after V46 promotion.
 - Specification discipline references: `BITCODE_SPECIFYING.md` and `BITCODE_SPEC_TEMPLATEGUIDE.md`.
 
 ## Roadmap
@@ -209,8 +209,9 @@ They are referenced here for specification history only; active implementation w
 | V42 | `BITCODE_SPEC_V42.md` | promoted historical Bitcode canon | Reliable MVP experience after V41 prompt hardening: shortest-path Depositing for any source material with Depository admission proof and later BTC compensation when deposits contribute to synthesized AssetPacks; shortest-path Reading for Read Request submission, synthesized Need review/resynthesis, Finding Fits, source-safe AssetPack measurement/preview review, BTD/BTC purchase and settlement, and repository delivery; and an AI-reading dominant demonstration proving an AssetPack can improve an AI system's training, prompt/context, or evaluation performance beyond public-data-only baselines using proprietary or otherwise non-public deposit and read materials. |
 | V43 | `BITCODE_SPEC_V43.md` | promoted historical Bitcode canon | Agentic enterprise deposit-side AssetPack option synthesis and broad UX cleanup after V42 reliable MVP paths: repository-installed Bitcode Agents compare a connected enterprise codebase, the Bitcode Depository, and Reading activity to propose deposit AssetPack options for review; filter out critical IP; estimate positive ROI against development cost and likely demand; let enterprises approve/reject options for Depository admission; split `/terminal` into `/read` and `/deposit`; and rename `/exchange` to `/packs` throughout product routes, code naming, docs, component prefixes, tests, and operator vocabulary. `/packs` becomes the searchable master-detail activity surface for all pack activity, with column sorting/filtering/search over measurements, synthesized AssetPack titles and descriptions, values, activity/transaction type, settlement posture, compensation, proof roots, and repair state. `/deposit` and `/read` become the short core paths into and out of the Depository. Outside public docs, product UX should be self-explanatory through route structure, concise labels, progressive detail, and rich reusable themed components rather than self-referential instructional copy. |
 | V44 | `BITCODE_SPEC_V44.md` | promoted historical Bitcode canon | Scaled engineering economy and tokenized AssetPack network operation after V43 route cleanup: enterprise AssetPack portfolios, Pack market signals, Reading demand signals, deposit supply opportunities, Reading budget policy, AssetPack quote policy, BTD/BTC/source-to-shares accounting, contributor compensation statements, organization policy, wallet/spend authority, scaled local/staging-testnet rehearsal, and polished economic operation across `/packs`, `/read`, and `/deposit` while keeping value-bearing mainnet blocked until later launch authority. |
-| V45 | `BITCODE_SPEC_V45.md` | active canon | Knowledge commoditization protocol precision after V44 scaled economics: AssetPack commodity lifecycle, BTD Need-relative scalar knowledge-volume and rights, BTC settlement finality, source-safe interface disclosure, proof-backed readback, operational repair, generated proof-family artifacts, source-safe end-to-end rehearsal, and canonical promotion. |
-| V46 | `BITCODE_SPEC_V46.md` | active draft target | Commercial protocol comprehension and launch-facing interface claim readiness after V45 knowledge commoditization law: source-safe public/operator explanation, product route comprehension for `/packs`, `/read`, and `/deposit`, API/MCP/ChatGPT App/Bitcode Chat claim contracts, proof-readable market activity, and local interface rehearsal without value-bearing mainnet authority. |
+| V45 | `BITCODE_SPEC_V45.md` | promoted historical Bitcode canon | Knowledge commoditization protocol precision after V44 scaled economics: AssetPack commodity lifecycle, BTD Need-relative scalar knowledge-volume and rights, BTC settlement finality, source-safe interface disclosure, proof-backed readback, operational repair, generated proof-family artifacts, source-safe end-to-end rehearsal, and canonical promotion. |
+| V46 | `BITCODE_SPEC_V46.md` | active canon | Commercial protocol comprehension and launch-facing interface claim readiness after V45 knowledge commoditization law: source-safe public/operator explanation, product route comprehension for `/packs`, `/read`, and `/deposit`, API/MCP/ChatGPT App/Bitcode Chat claim contracts, proof-readable market activity, local interface rehearsal without value-bearing mainnet authority, and canonical promotion. |
+| V47 | `BITCODE_SPEC_V47_NOTES.md` | notes-only draft target | Specification-workshopping target after promoted V46: audit protocol atoms in small pieces, refine exact Bitcode law before implementation parity, prepare the V47 parity matrix, and then open scoped gates only after the accepted specification changes are precise. |
 
 ## Current Planning Spine
 

packages/protocol/src/canonical/v46-local-interface-comprehension-rehearsal.js

@@ -446,7 +446,10 @@ function buildPredicateResults(repoRoot) {
       (sources.roadmap.includes('Current working gate: V46 Gate 7 Local Interface Comprehension Rehearsal') &&
         sources.roadmap.includes('V46 Gate 6 closure anchor')) ||
         (sources.roadmap.includes('V46 Gate 7 closure anchor') &&
-          sources.roadmap.includes('Current working gate: V46 Gate 8 Promotion Readiness And Canonical Promotion')),
+          sources.roadmap.includes('Current working gate: V46 Gate 8 Promotion Readiness And Canonical Promotion')) ||
+        (sources.roadmap.includes('V46 Gate 7 closure anchor') &&
+          sources.roadmap.includes('Latest closed gate: V46 Gate 8 Promotion Readiness And Canonical Promotion') &&
+          sources.roadmap.includes('Current working gate: V47 opening preparation')),
     ),
     predicateResult(
       'readmes-document-gate7',

protocol-demonstration/test/v21-specifying.test.js

@@ -32,6 +32,8 @@ function expectedActiveCanonicalInputArtifactCount(version) {
     V42: 10,
     V43: 11,
     V44: 11,
+    V45: 13,
+    V46: 9,
   };
   if (Object.hasOwn(expectedCountsByVersion, version)) {
     return expectedCountsByVersion[version];