V36 Gate 1: Open Exchange roadmap

Open the V36 Exchange-depth spec family over promoted V35 canon, including SPEC, DELTA, NOTES, and PARITY files.

Wire check:v36-gate1 through package scripts and gate/canon quality workflows, refresh roadmap and contributor docs to V35 active / V36 draft posture, and preserve V37 Conversations as deferred scope.

Validation: node scripts/check-bitcode-spec-family.mjs --version V36 --mode draft --current-target V35; node scripts/check-bitcode-canonical-inputs.mjs --current-target V35; node scripts/check-bitcode-canon-posture-drift.mjs --active-canon V35 --draft-target V36; pnpm run check:v36-gate1; node scripts/check-bitcode-spec-family.mjs --version V35 --mode promoted --current-target V35; node scripts/check-v35-gate10-promotion-readiness.mjs --promotion-mode --skip-branch-check; git diff --check.

Author: geraldarthurdavis

.github/pull_request_template.md

@@ -1,7 +1,7 @@
 ## Title
 
-Use the version and gate prefix for gate PRs: `V35 Gate N: Concise Topical Title`.
-Use the version and promotion prefix for version promotion PRs: `V35 Canonical Promotion: Concise Topical Title`.
+Use the version and gate prefix for gate PRs: `V36 Gate N: Concise Topical Title`.
+Use the version and promotion prefix for version promotion PRs: `V36 Canonical Promotion: Concise Topical Title`.
 
 ## Closure
 

.github/workflows/bitcode-canon-quality.yml

@@ -164,7 +164,15 @@ jobs:
                 node scripts/check-bitcode-spec-family.mjs --version V35 --mode draft --current-target V34
               fi
               ;;
+            spec:\ V36*|spec:\ v36*)
+              POINTER="$(cat BITCODE_SPEC.txt)"
+              if [ "$POINTER" = "V36" ]; then
+                node scripts/check-bitcode-spec-family.mjs --version V36 --mode promoted --current-target V36
+              else
+                node scripts/check-bitcode-spec-family.mjs --version V36 --mode draft --current-target V35
+              fi
+              ;;
             *)
-              echo "Skipping strict spec-title conformance; title is not a V29/V30/V31/V32/V33/V34/V35 spec change."
+              echo "Skipping strict spec-title conformance; title is not a V29/V30/V31/V32/V33/V34/V35/V36 spec change."
               ;;
           esac

.github/workflows/bitcode-gate-quality.yml

@@ -200,6 +200,7 @@ jobs:
             node scripts/check-v35-gate10-promotion-readiness.mjs --promotion-mode --skip-branch-check
             if [ -f BITCODE_SPEC_V36.md ]; then
               node scripts/check-bitcode-spec-family.mjs --version V36 --mode draft --current-target V35
+              node scripts/check-v36-gate1-exchange-roadmap-opening.mjs --skip-branch-check
             fi
           else
             echo "Unexpected BITCODE_SPEC.txt pointer: $POINTER" >&2

BITCODE_SPEC_V36.md

@@ -0,0 +1,165 @@
+# Bitcode Spec V36 Delta
+
+## Status
+
+- Version: `V36`
+- V36 state: active draft target opened; this delta records the planned V35-to-V36 Exchange-depth closure set
+- Current canonical/latest target: `V35`
+- Prior canonical anchor: `BITCODE_SPEC_V35.md`
+- Prior generated proof appendix: `BITCODE_SPEC_V35_PROVEN.md`
+- Generated structured artifact inventory: draft `.bitcode/v36-spec-family-report.json` and `.bitcode/v36-canonical-input-report.json`; later gates add Exchange generated artifacts
+- Source parity state: V36 source parity begins with Gate 1 roadmap/spec opening and is closed gate-by-gate through Exchange contracts, UI, telemetry, settlement, repair, rehearsal, and promotion readiness
+- Spec companion: `BITCODE_SPEC_V36.md`
+- Notes companion: `BITCODE_SPEC_V36_NOTES.md`
+- Parity companion: `BITCODE_SPEC_V36_PARITY_MATRIX.md`
+- Generated proof appendix: `BITCODE_SPEC_V36_PROVEN.md` only after V36 promotion
+- Scope: V36 draft delta for deeper Exchange over promoted V35 telemetry/documentation canon
+
+## Why V36 exists
+
+V35 promoted telemetry and documentation depth.
+That made Bitcode understandable, supportable, observable, and testnet-rollout ready.
+
+V36 exists because Bitcode now needs the Exchange surface to become real product law instead of deferred posture.
+Exchange must let enterprise users inspect market-wide activity, list or request rights transfers, buy, sell, bid, ask, cancel, accept, settle, and inspect history while preserving BTC fee separation, non-fungible BTD range identity, source-safe AssetPack previews, settlement finality, repair paths, and ledger/database synchronization.
+
+## Accepted V36 decisions
+
+- V35 remains active canon during V36 drafting.
+- V36 gate branches are opened from `version/v36` and merged back only when their gate acceptance criteria are closed.
+- V36 owns deeper Exchange: `ExchangeActivityBook`, `ExchangeIntent`, `ExchangeOrder`, `ExchangeRightsTransferPreview`, `ExchangePricingQuote`, `ExchangeSettlementReceipt`, `ExchangeDisputeRepairCase`, and `ExchangeRevenueRoute`.
+- Exchange contracts must be package-owned before they are exposed by route handlers, UI state, dashboards, runbooks, MCP tools, ChatGPT App actions, public docs, or generated artifacts.
+- Exchange previews disclose measurements, roots, rights posture, fee quote roots, owner posture, settlement state, and denial reasons; they must not disclose protected source, raw protected prompts, wallet private material, secrets, or unpaid AssetPack contents.
+- Ledger records and journals remain source-of-truth for ownership, settlement, and finality; database projections are repairable projections.
+- Exchange pricing may include measurement weights, measurement volume, liquidity bands, wrapper analysis, and BTC fee quotes only through deterministic auditable quote roots.
+
+## Explicitly deferred
+
+- V37 owns website Conversations product behavior.
+- Production-mainnet value-bearing launch remains explicitly blocked until a future promoted canon admits it.
+- Bridge chain-of-record implementation remains out of V36.
+- V36 does not reopen BTD supply law, Reading pipeline product law, V34 deployment law, V35 telemetry/docs law, or AssetPack source disclosure law.
+
+## Pre-Implementation Sequence
+
+1. Open `version/v36` from promoted `main`.
+2. Open `v36/gate-1-exchange-roadmap-opening` from `version/v36`.
+3. Create the V36 SPEC, DELTA, NOTES, and PARITY family while preserving `BITCODE_SPEC.txt -> V35`.
+4. Refresh `SPECIFICATIONS_ROADMAP.md` so V35 is active canon, V36 is draft target, and V37 scope remains coherent.
+5. Retarget gate-quality and canon-quality workflow posture checks to V35 active / V36 draft.
+6. Add `check:v36-gate1` and a V36 Gate 1 checker.
+7. Define V36 gates, acceptance criteria, carryforward parity rows, and post-V36 roadmap responsibilities.
+8. Validate spec family, canonical inputs, canon posture, workflows, roadmap truth, README/docs, and diff hygiene.
+9. Push the gate branch and open a pull request to `version/v36`.
+
+## Commit-Body Direction
+
+V36 gate commit bodies should describe the closed gate, specification changes, implementation surfaces, tests, proof commands, and accepted boundaries.
+The eventual V36 promotion commit body must name all closed V36 gates, generated Exchange proof artifacts, settlement/reconciliation evidence, UI proof, public/internal documentation evidence, telemetry/runbook evidence, local/staging rehearsal proof, and the `BITCODE_SPEC.txt` pointer change from `V35` to `V36`.
+It must explicitly defer V37 Conversations depth, bridge chain-of-record implementation, and value-bearing mainnet launch.
+
+## Gate Delta
+
+### Gate 1: V36 Exchange Roadmap And Spec Opening
+
+Gate 1 opens V36 correctly:
+
+- V36 SPEC, DELTA, NOTES, and PARITY files exist.
+- `BITCODE_SPEC.txt` remains `V35`.
+- README, roadmap, PR template, package docs, demonstration docs, and workflows describe V35 active / V36 draft posture.
+- `check:v36-gate1` validates branch naming, spec family, notes, parity, roadmap truth, workflow posture, Exchange vocabulary, and promotion boundaries.
+- The V36 gate list is explicit before Exchange implementation begins.
+
+### Gate 2: Exchange Activity Book And Market Master Detail
+
+Gate 2 inventories source-safe market activity.
+
+Closure acceptance:
+
+- `ExchangeActivityBook` owns market-wide activity rows, filters, detail payloads, proof roots, event ids, and redaction posture;
+- activity rows cover listings, bids, asks, cancellations, acceptances, settlements, repairs, revenue routes, and history entries;
+- activity detail never exposes protected source or unpaid AssetPack content.
+
+### Gate 3: Buy Sell Bid Ask Cancel Accept Intent Contracts
+
+Gate 3 defines market action envelopes.
+
+Closure acceptance:
+
+- `ExchangeIntent` and `ExchangeOrder` own buy, sell, bid, ask, cancel, accept, settle, and history transition contracts;
+- each transition names actor, organization role, wallet posture, authority proof, idempotency key, policy decision, and fail-closed result;
+- order history is replayable without private wallet material or secrets.
+
+### Gate 4: AssetPack Range Trading And Rights Transfer Review
+
+Gate 4 defines rights-transfer preview.
+
+Closure acceptance:
+
+- `ExchangeRightsTransferPreview` names BTD range identity, current owner, requested buyer, rights scope, settlement unlock condition, and disclosure limit;
+- AssetPack source is hidden until paid settlement and rights transfer are complete;
+- previews distinguish owner-read, licensed-read, and blocked transfer states.
+
+### Gate 5: Pricing Liquidity Fee Quote And Wrapper Analysis
+
+Gate 5 defines deterministic price and fee roots.
+
+Closure acceptance:
+
+- `ExchangePricingQuote` includes BTC amount, measurement weight, measurement volume, liquidity band, wrapper analysis, treasury route, depositor route, reader route, and quote root;
+- wrapper analysis cannot make BTD range cells fungible chain-of-record assets;
+- underpayment, overpayment, stale quote, or unsupported network posture fails closed.
+
+### Gate 6: Exchange Settlement Ledger Database Reconciliation
+
+Gate 6 synchronizes settlement.
+
+Closure acceptance:
+
+- `ExchangeSettlementReceipt` binds payment observation, finality state, rights transfer receipt, ledger root, database projection root, object storage root, delivery state, and repair id;
+- observers and repair jobs reconcile database projections to ledger truth;
+- settlement finality and delivery are auditable.
+
+### Gate 7: Dispute Repair Revenue Route Operations
+
+Gate 7 turns failure into operator action.
+
+Closure acceptance:
+
+- `ExchangeDisputeRepairCase` covers stale owner, cancelled order replay, underpayment, overpayment, projection drift, source leakage, and delivery mismatch;
+- `ExchangeRevenueRoute` covers depositor, reader, treasury, fee, BTC route, BTD right route, and conservation proof;
+- runbooks and repair commands are source-safe and proof-rooted.
+
+### Gate 8: Exchange UX And Terminal Navigation Integration
+
+Gate 8 makes Exchange usable.
+
+Closure acceptance:
+
+- `/exchange` exposes market-wide master-detail, filters, order history, rights-transfer review, pricing quote, settlement state, and repair state;
+- Terminal can hand off to Exchange without losing transaction context;
+- collapsed UI gives readable status and expanded UI exposes source-safe detail.
+
+### Gate 9: Local Staging Exchange Rehearsal And Proof Coverage
+
+Gate 9 proves Exchange locally and in staging-testnet.
+
+Closure acceptance:
+
+- local and staging-testnet rehearsals exercise list, bid, ask, cancel, accept, settle, repair, and history flows;
+- rehearsal logs/screenshots are source-safe;
+- ledger/database synchronization and value-bearing mainnet blocking are visible.
+
+### Gate 10: V36 Promotion Readiness
+
+Gate 10 owns final generated proof, promotion workflow support, source-safe `.bitcode/v36-promotion-readiness-report.json`, and V36 closure.
+
+Closure acceptance:
+
+- V36 promotion checks validate all Exchange artifacts, contracts, UI proof, telemetry/docs/runbook bindings, settlement/reconciliation evidence, repair evidence, rehearsal proof, and generated proof appendix support;
+- promotion scripts support V36 command planning, dry-run, generated proof output, and derived promotion commit body generation;
+- promotion rewrites runtime posture to active V36 / draft V37 only after validations pass.
+
+## Delta completion condition
+
+This delta is complete for Gate 1 when `version/v36` contains the V36 spec family, roadmap posture, workflow posture, README/package docs posture, PR template title guidance, `check:v36-gate1`, and validations proving V35 active / V36 draft readiness.

BITCODE_SPEC_V36_DELTA.md

@@ -3,45 +3,79 @@
 ## Status
 
 - Version: `V36`
-- V36 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`
-- Generated structured artifact inventory: none for V36 yet
-- Source parity state: not opened; V36 source parity begins only after V36 draft opening
-- Scope: future notes for deeper Exchange work after V35 telemetry/documenting depth.
-
-This NOTES file does not promote V36 and does not open V36 implementation.
+- V36 state: active draft target opened; Gate 1 turns prior future notes into the Exchange-depth working specification family
+- Current canonical/latest target: `V35`
+- Prior canonical anchor: `BITCODE_SPEC_V35.md`
+- Prior generated proof appendix: `BITCODE_SPEC_V35_PROVEN.md`
+- Generated structured artifact inventory: draft `.bitcode/v36-spec-family-report.json` and `.bitcode/v36-canonical-input-report.json`; Exchange artifacts begin after Gate 1
+- Source parity state: V36 source parity begins with Gate 1 and remains draft until each Exchange gate closes
+- Spec companion: `BITCODE_SPEC_V36.md`
+- Delta companion: `BITCODE_SPEC_V36_DELTA.md`
+- Parity companion: `BITCODE_SPEC_V36_PARITY_MATRIX.md`
+- Generated proof appendix: `BITCODE_SPEC_V36_PROVEN.md` only after V36 promotion
+- Scope: V36 notes for deeper Exchange work after promoted V35 telemetry/documenting depth
 
 ## Notes companion rule
 
-This file is planning memory only.
-Requirements become binding only when V36 is explicitly opened as the draft-target SPEC family.
+This file records working notes for the V36 draft target.
+Requirements become binding when copied into `BITCODE_SPEC_V36.md`, `BITCODE_SPEC_V36_DELTA.md`, `BITCODE_SPEC_V36_PARITY_MATRIX.md`, checker scripts, package contracts, tests, or generated artifacts.
 
 ## Concise current-system reading
 
-V28 no longer includes Exchange closure.
-Exchange returns after the Protocol/Terminal, Auxillaries, provation, interface, deployment, telemetry, and documentation spine is mature enough to support a market surface.
+V35 is active canon.
+V36 opens Exchange depth without changing Reading, BTD tokenomics, BTC fee separation, deployment law, telemetry/documentation law, or source disclosure law.
+
+Exchange must operate as a market surface over rights and source-safe previews.
+It must not become a hidden tokenomics rewrite, a source leakage path, or a database-first settlement system.
+
+## Simplified-spec reading rule
+
+Read V36 as:
+
+1. The active system is V35.
+2. V36 adds auditable Exchange product behavior.
+3. Exchange actions manipulate market intents, orders, rights-transfer previews, settlement receipts, dispute/repair cases, and revenue routes.
+4. BTD range identity remains non-fungible source-share law.
+5. Protected source remains hidden before paid settlement.
+6. Ledger truth remains stronger than database projection.
+
+## Exchange depth notes
+
+- Market activity needs master-detail clarity: a collapsed row should be enough for status, while expanded detail must include proof roots, safe metadata, and repair posture.
+- Buy/sell/bid/ask/cancel/accept/settle/history actions must be typed intents, not route-local ad hoc payloads.
+- Pricing must be deterministic and auditable. Initial design uses measurement weight times measurement volume as a source factor, then folds liquidity, fee, and policy factors into a BTC quote root.
+- Wrapper analysis is allowed only as analysis. A wrapper cannot become the chain-of-record for BTD ownership.
+- Rights-transfer preview must clearly separate current owner, prospective buyer, BTD range identity, source-safe measurements, quote roots, settlement posture, and post-settlement delivery.
+- Dispute and repair posture must exist before optimistic market UX is considered complete.
 
-## Intended V36 focus
+## V36 gate plan
 
-V36 owns deeper Exchange:
+1. Gate 1: V36 Exchange Roadmap And Spec Opening.
+2. Gate 2: Exchange Activity Book And Market Master Detail.
+3. Gate 3: Buy Sell Bid Ask Cancel Accept Intent Contracts.
+4. Gate 4: AssetPack Range Trading And Rights Transfer Review.
+5. Gate 5: Pricing Liquidity Fee Quote And Wrapper Analysis.
+6. Gate 6: Exchange Settlement Ledger Database Reconciliation.
+7. Gate 7: Dispute Repair Revenue Route Operations.
+8. Gate 8: Exchange UX And Terminal Navigation Integration.
+9. Gate 9: Local Staging Exchange Rehearsal And Proof Coverage.
+10. Gate 10: V36 Promotion Readiness.
 
-- Exchange MVP/deepening after V35, not during V28;
-- market-wide activity master-detail;
-- buy, sell, bid, ask, cancel, accept, settle, and history flows;
-- AssetPack range trading UX and rights-transfer review;
-- pricing, liquidity, wrapper, and settlement analytics only where they preserve `$BTD` non-fungible source-share law;
-- dispute, repair, revenue-route, and ledger/database reconciliation operations specific to market activity;
-- Exchange-specific tests, proofs, telemetry, and public documentation.
+## Gate 1 working notes
 
-## Boundaries
+Gate 1 closes when:
 
-V36 must not redefine `$BTD` supply, BTC fee separation, AssetPack range identity, owner-read/licensed-read law, measureminting, or ancestry.
-V36 must not retroactively make Exchange a V28 promotion blocker.
+- V36 SPEC, DELTA, NOTES, and PARITY files exist;
+- `BITCODE_SPEC.txt` remains `V35`;
+- roadmap status marks V35 active and V36 draft;
+- README, protocol package README, demonstration README, and PR template name V36 workflow;
+- gate-quality and canon-quality workflows understand V36 draft posture;
+- `check:v36-gate1` passes locally and in CI.
 
-## Return To V28
+## Accepted boundaries
 
-Do not start V36 implementation during V28.
-Record Exchange findings during V28 only when they contaminate active V28 Terminal, Protocol, BTD, MCP API, or ChatGPT App behavior.
+- V36 owns deeper Exchange.
+- V37 owns website Conversations.
+- V36 does not authorize value-bearing production-mainnet launch.
+- V36 does not redefine BTD supply, BTC fee separation, AssetPack range identity, owner-read/licensed-read law, measureminting, ancestry, or Reading pipeline product law.
+- Exchange must not expose protected AssetPack source before settlement.