V32 Promotion: Open V33 notes posture

Update promoted V32 quality expectations for the expanded canonical input artifact catalog and rewrite the V33 notes file into the required notes-only draft opening over V32. Local proof: V33 draft notes check, V32 canonical input check, strict V33 spec quality, V32 promotion readiness, and protocol-demonstration unit tests all pass.

Author: geraldarthurdavis

BITCODE_SPEC_V33_NOTES.md

@@ -3,30 +3,43 @@
 ## Status
 
 - Version: `V33`
-- V33 state: future notes scaffold only
-- Current canonical/latest target: `V27`
-- Current active draft target: `V28`
-- Prior canonical anchor: `BITCODE_SPEC_V27.md`
-- Prior generated proof appendix: `BITCODE_SPEC_V27_PROVEN.md`
+- Canonical pointer: `BITCODE_SPEC.txt` -> `V32`
+- Active canonical anchor: `BITCODE_SPEC_V32.md`
+- Active generated proof appendix: `BITCODE_SPEC_V32_PROVEN.md`
+- V33 state: notes-only draft opening
+- Current canonical/latest target: `V32`
+- Current active draft target: `V33`
 - Generated structured artifact inventory: none for V33 yet
-- Source parity state: not opened; V33 source parity begins only after V33 draft opening
-- Scope: future notes for deeper Interfaces after V28 MCP API/ChatGPT App MVP, V29 Terminal depth, V30 Protocol/BTD hardening, V31 Auxillaries depth, and V32 provation/testing depth.
+- Source parity state: notes-only opening; V33 source parity begins only after the first gate opens implementation.
+- Scope: next-version notes for interface, integration, and enterprise shippability depth after V32 provation/testing closure.
 
-This NOTES file does not promote V33 and does not open V33 implementation.
+This NOTES file does not promote V33 and does not authorize implementation before a scoped V33 gate branch opens.
 
-## Notes companion rule
+## Notes-only draft rule
 
-This file is planning memory only.
-Requirements become binding only when V33 is explicitly opened as the draft-target SPEC family.
+This file is planning memory only while V32 is canon.
+Requirements become binding only when V33 is explicitly opened as the draft-target SPEC family on `version/v33` and then through numbered V33 gate branches.
+Any V33 implementation must be gate-scoped, never not first-gate work hidden in a promotion repair branch.
 
 ## Concise current-system reading
 
-V28 owns commercial Protocol/Terminal MVP QA and retains MCP API plus ChatGPT App MVP acceptance.
-V33 owns later interface depth that makes Bitcode commercially integratable beyond the V28 MVP, the website, and the Auxillaries product surface.
+V32 closes provation, testing, promotion proof generation, deterministic replay, and testnet/mainnet readiness rehearsal posture for the commercial Bitcode system.
+V33 begins from that V32 canon and should make the interface and operational integration layers more directly enterprise-shippable without weakening the Bitcoin, GitHub, compute, storage, or build/process boundaries proven by V32.
 
-## Intended V33 focus
+## Deferred from V32
 
-V33 owns deeper Interfaces beyond the V28 MVP:
+The following work was intentionally deferred from V32 because V32 focused on provation/testing closure and canonical promotion mechanics:
+
+- Bitcoin production-mainnet settlement enablement beyond V32's blocked rehearsal posture;
+- GitHub delivery and review ergonomics beyond the V32 source-safe proof surfaces;
+- compute execution provider hardening where long-running pipeline hosts, retries, and pushed completion events need production contracts;
+- storage retention, replay, and customer-facing evidence lifecycle policies beyond generated proof artifacts;
+- build/process automation that keeps version gates, promotion proofs, and deployment proofs green without ad hoc repair;
+- enterprise interface depth for non-terminal consumers after V32 validated source-safe canon and proof generation.
+
+## Candidate V33 workstreams
+
+V33 candidate workstreams should be ordered into explicit gates before implementation:
 
 - MCP API maturation beyond the V28 MVP for registry-derived AssetPack range, read-right, wallet, fee, journal, reconciliation, proof, and operational actions;
 - ChatGPT App maturation beyond the V28 MVP as the first integratable chatbot application interface;
@@ -36,12 +49,12 @@ V33 owns deeper Interfaces beyond the V28 MVP:
 - interface-specific MCP and ChatGPT App QA, including route/action discovery, denied-state readability, and proof-root surfacing;
 - handoff of hosting, distributed execution, CI/CD, broad deployment operations, telemetry depth, and public documentation to V34 and V35.
 
-## Boundaries
+## Non-goals during V33 opening
 
 V33 deepens commercial interface surfaces beyond the V28 MVP.
 It should not reopen V27 tokenomics law, replace V32 provation/testing depth, or absorb V34 deployment and V35 telemetry/documentation work except for narrow interface-owned hooks.
 
-## Return To V28
+## Return To V32
 
-Do not start V33 implementation during V28 except for the V28-scoped MCP API and ChatGPT App MVP.
-Record API, MCP, ChatGPT App, and non-website interface gaps beyond V28 MVP as future V33 inputs.
+Do not start V33 implementation during V32 promotion repair.
+Record API, MCP, ChatGPT App, customer integration, deployment, telemetry, and documentation gaps beyond V32 as future V33 inputs until `version/v33` and its first gate branch are opened.

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

@@ -20,6 +20,7 @@ function projectLabel(version) {
 function expectedActiveCanonicalInputArtifactCount(version) {
   const numeric = Number.parseInt(String(version || '').replace(/^V/u, ''), 10);
   if (!Number.isInteger(numeric)) return 3;
+  if (numeric >= 32) return 13;
   if (numeric >= 30) return 4;
   if (numeric >= 27) return 0;
   if (numeric === 26) return 22;