Skip to content

Commit 5710b3b

Browse files
Merge pull request #136 from engineeredsoftware/v39/gate-1-commercial-reading-roadmap-opening
V39 Gate 1: Commercial Reading Roadmap Opening
2 parents 7711266 + 2350e8f commit 5710b3b

18 files changed

Lines changed: 1480 additions & 33 deletions

.github/pull_request_template.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
## Title
22

3-
Use the version and gate prefix for gate PRs: `V38 Gate N: Concise Topical Title`.
4-
Use the version and promotion prefix for version promotion PRs: `V38 Canonical Promotion: Concise Topical Title`.
3+
Use the version and gate prefix for gate PRs: `V39 Gate N: Concise Topical Title`.
4+
Use the version and promotion prefix for version promotion PRs: `V39 Canonical Promotion: Concise Topical Title`.
55

66
## Closure
77

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

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -181,6 +181,10 @@ jobs:
181181
node scripts/check-bitcode-canon-posture-drift.mjs --active-canon V38 --draft-target V39
182182
node scripts/check-bitcode-spec-family.mjs --version V38 --mode promoted --current-target V38
183183
node scripts/check-v38-gate11-promotion-readiness.mjs --promotion-mode --skip-branch-check --skip-package-tests
184+
if [ -f BITCODE_SPEC_V39.md ]; then
185+
node scripts/check-bitcode-spec-family.mjs --version V39 --mode draft --current-target V38
186+
node scripts/check-v39-gate1-commercial-reading-roadmap-opening.mjs --skip-branch-check
187+
fi
184188
else
185189
echo "Unexpected BITCODE_SPEC.txt pointer: $POINTER" >&2
186190
exit 1
@@ -296,7 +300,15 @@ jobs:
296300
node scripts/check-bitcode-spec-family.mjs --version V38 --mode draft --current-target V37
297301
fi
298302
;;
303+
spec:\ V39*|spec:\ v39*)
304+
POINTER="$(cat BITCODE_SPEC.txt)"
305+
if [ "$POINTER" = "V39" ]; then
306+
node scripts/check-bitcode-spec-family.mjs --version V39 --mode promoted --current-target V39
307+
else
308+
node scripts/check-bitcode-spec-family.mjs --version V39 --mode draft --current-target V38
309+
fi
310+
;;
299311
*)
300-
echo "Skipping strict spec-title conformance; title is not a V29/V30/V31/V32/V33/V34/V35/V36/V37/V38 spec change."
312+
echo "Skipping strict spec-title conformance; title is not a V29/V30/V31/V32/V33/V34/V35/V36/V37/V38/V39 spec change."
301313
;;
302314
esac

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -310,6 +310,10 @@ jobs:
310310
node scripts/check-bitcode-canonical-inputs.mjs --current-target V38
311311
node scripts/check-bitcode-canon-posture-drift.mjs --active-canon V38 --draft-target V39
312312
node scripts/check-v38-gate11-promotion-readiness.mjs --promotion-mode --skip-branch-check --skip-package-tests
313+
if [ -f BITCODE_SPEC_V39.md ]; then
314+
node scripts/check-bitcode-spec-family.mjs --version V39 --mode draft --current-target V38
315+
node scripts/check-v39-gate1-commercial-reading-roadmap-opening.mjs --skip-branch-check
316+
fi
313317
else
314318
echo "Unexpected BITCODE_SPEC.txt pointer: $POINTER" >&2
315319
exit 1

BITCODE_SPEC_V39.md

Lines changed: 549 additions & 0 deletions
Large diffs are not rendered by default.

BITCODE_SPEC_V39_DELTA.md

Lines changed: 194 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,194 @@
1+
# Bitcode Spec V39 Delta
2+
3+
## Status
4+
5+
- Version: `V39`
6+
- V39 state: draft opened; this delta records the planned V38-to-V39 commercial Reading readiness closure set
7+
- Current canonical/latest target: `V38`
8+
- Draft proof-source commit: unbound until V39 promotion
9+
- Prior canonical anchor: `BITCODE_SPEC_V38.md`
10+
- Prior generated proof appendix: `BITCODE_SPEC_V38_PROVEN.md`
11+
- Generated structured artifact inventory: draft opening requires `.bitcode/v39-spec-family-report.json` and `.bitcode/v39-canonical-input-report.json`; later V39 gates must add package-backed source-safe artifacts for Depository indexing, Reading UX state, ReadNeed review/resynthesis, ReadFitsFinding runtime, AssetPack preview/quote, settlement/delivery rights, telemetry/repair, interface parity, rehearsal, and promotion readiness
12+
- Source parity state: V39 delta opens parity requirements; implementation parity remains pending until each V39 gate closes with source, artifacts, tests, workflow checks, and source-safe documentation
13+
- Spec companion: `BITCODE_SPEC_V39.md`
14+
- Notes companion: `BITCODE_SPEC_V39_NOTES.md`
15+
- Parity companion: `BITCODE_SPEC_V39_PARITY_MATRIX.md`
16+
- Generated proof appendix: `BITCODE_SPEC_V39_PROVEN.md` only after V39 promotion
17+
- Scope: V39 draft delta for commercial Reading readiness over promoted V38 inference correctness canon
18+
19+
## Why V39 exists
20+
21+
V38 promoted inference correctness.
22+
It made pipeline execution, PTRR agents, FailsafeGenerationSequence, ThricifiedGeneration, prompt benchmarking, source-safe inference telemetry, and Reading fit-search primitives exact enough to use as production-grade infrastructure.
23+
24+
V39 exists because Bitcode now needs the full enterprise Reading path to become commercially reliable.
25+
V39 closes product runtime gaps across Depository supply indexing, Read Request capture, reviewable ReadNeed synthesis and resynthesis, Finding Fits across many candidate deposits, source-safe AssetPack preview, deterministic BTC quote, BTD rights transfer, post-settlement delivery, ledger/database/storage synchronization, repair, and interface parity.
26+
27+
## Accepted V39 decisions
28+
29+
- V38 remains active canon during V39 drafting.
30+
- V39 gate branches are opened from `version/v39` and merged back only when their gate acceptance criteria are closed.
31+
- V39 owns commercial Reading readiness across Terminal, Conversation, MCP/API, ChatGPT App, package contracts, Depository, ledger, database, storage, wallet, and delivery surfaces.
32+
- V38 inference law remains binding: PTRR agent steps use `FailsafeGenerationSequence` above `ThricifiedGeneration`, tools are step-owned, prompt registry composition is preserved, and telemetry disclosure tiers govern all inference evidence.
33+
- `ReadNeedComprehensionSynthesis` must become a persisted review/resynthesis loop whose accepted Need gates Finding Fits.
34+
- `ReadFitsFindingSynthesis` must discover many candidate deposits above threshold before AssetPack synthesis and settlement handoff.
35+
- Fit-finding must preserve the active OpenAI embedding policy (`text-embedding-3-small`, 1536 dimensions, cosine `match_deliverable_vectors`) unless a replacement is explicitly specified, tested, and migrated.
36+
- Source-bearing AssetPack delivery is forbidden before settlement unlock and BTD rights transfer.
37+
38+
## Explicitly deferred
39+
40+
- Production-mainnet value-bearing launch remains blocked.
41+
- Bridge chain-of-record implementation remains deferred.
42+
- V39 does not reopen BTD supply law, Exchange law, or Bitcoin settlement law except for inference and fit-finding traceability needed by AssetPack preview and post-settlement delivery.
43+
- New LlamaIndex, Pinecone, or provider-specific search channels may be specified only after boundaries, credentials, storage, telemetry, and tests are explicit.
44+
45+
## Pre-Implementation Sequence
46+
47+
1. Open `version/v39` from promoted `main`.
48+
2. Open `v39/gate-1-commercial-reading-roadmap-opening` from `version/v39`.
49+
3. Create the V39 SPEC, DELTA, NOTES, and PARITY family while preserving `BITCODE_SPEC.txt -> V38`.
50+
4. Refresh `SPECIFICATIONS_ROADMAP.md` so V38 is active canon, V39 is draft target, and post-V39 work remains coherent.
51+
5. Retarget gate-quality and canon-quality workflow posture checks to V38 active / V39 draft.
52+
6. Add `check:v39-gate1` and a V39 Gate 1 checker.
53+
7. Define V39 gates, acceptance criteria, carryforward parity rows, and promotion boundaries.
54+
8. Validate spec family, canonical inputs, canon posture, workflows, roadmap truth, README/docs, and diff hygiene.
55+
9. Push the gate branch and open a pull request to `version/v39`.
56+
57+
## Commit-Body Direction
58+
59+
V39 gate commit bodies should describe the closed gate, product surface, pipeline/runtime changes, generated proof artifacts, tests, telemetry/disclosure boundaries, and accepted deferrals.
60+
The eventual V39 promotion commit body must name all closed V39 gates, generated commercial Reading proof artifacts, Depository indexing evidence, ReadNeed and ReadFitsFinding runtime evidence, AssetPack preview/quote evidence, settlement/delivery evidence, telemetry/repair evidence, local/staging rehearsal proof, promotion workflow evidence, and the `BITCODE_SPEC.txt` pointer change from `V38` to `V39`.
61+
62+
## Gate Delta
63+
64+
### Gate 1: V39 Commercial Reading Roadmap And Spec Opening
65+
66+
Gate 1 opens V39 correctly:
67+
68+
- V39 SPEC, DELTA, NOTES, and PARITY files exist.
69+
- `BITCODE_SPEC.txt` remains `V38`.
70+
- README, roadmap, PR template, package docs, demonstration docs, and workflows describe V38 active / V39 draft posture.
71+
- `check:v39-gate1` validates branch naming, spec family, notes, parity, roadmap truth, workflow posture, inference vocabulary, depository-search vocabulary, and promotion boundaries.
72+
- The V39 gate list is explicit before inference implementation begins.
73+
74+
### Gate 2: Depository Supply Indexing And Searchable Deposit Lifecycle
75+
76+
Closure acceptance:
77+
78+
- deposited source materials are measurable, indexable, vector-searchable, metadata-searchable, rights-aware, and repairable;
79+
- deposit lifecycle receipts bind repository/deposit anchors, measurement roots, embedding roots, ownership boundaries, and source-safe telemetry;
80+
- `pnpm run check:v39-gate2` validates package-backed source, generated artifact freshness, tests, and workflow wiring without exposing protected source or credentials.
81+
82+
Closure implementation:
83+
84+
- Pending Gate 2 work must define its package-owned canonical source and deterministic artifact path before implementation begins.
85+
- The artifact must use a source-safe disclosure posture and include repair/replay acceptance criteria.
86+
87+
### Gate 3: Enterprise Reading UX State Machine
88+
89+
Closure acceptance:
90+
91+
- Terminal implements the five-step enterprise Reading flow: request read, review synthesized Need, request Finding Fits, review source-safe AssetPack preview, buy and settle;
92+
- each step has clear low-detail default UI and expandable source-safe detail;
93+
- `pnpm run check:v39-gate3` validates state contracts, component tests, browser proof, and disclosure boundaries.
94+
95+
Closure implementation:
96+
97+
- Pending Gate 3 work must define route contracts, UI tests, and generated UX-state proof artifact.
98+
99+
### Gate 4: ReadNeed Review, Resynthesis, And Admission Runtime
100+
101+
Closure acceptance:
102+
103+
- `ReadNeedComprehensionSynthesis` persists Read Requests, synthesized Needs, feedback, resynthesis attempts, Need measurements, accepted-Need admission, rejected-Need posture, and source-safe telemetry receipts;
104+
- Finding Fits remains blocked until a reviewed Need is accepted;
105+
- `pnpm run check:v39-gate4` validates pipeline contracts, storage, telemetry, UI, tests, artifact freshness, and workflow wiring.
106+
107+
Closure implementation:
108+
109+
- Pending Gate 4 work must define package-backed source, deterministic artifact, pipeline tests, route tests, and accepted-Need admission tests.
110+
111+
### Gate 5: ReadFitsFinding Runtime, Ranking, And Replay
112+
113+
Closure acceptance:
114+
115+
- Finding Fits uses inference-derived queries and depository search tools across lexical, symbolic, path, metadata, measurement, embedding/vector, and provider-specific channels;
116+
- candidate deposits above threshold are ranked, verified, replayable, and traceable into selected-fit provenance;
117+
- `pnpm run check:v39-gate5` validates search tools, embeddings, ranking, thresholding, replay receipts, tests, and generated evidence.
118+
119+
Closure implementation:
120+
121+
- Pending Gate 5 work must define runtime search artifacts, active embedding policy checks, and many-candidate replay evidence.
122+
123+
### Gate 6: AssetPack Preview, Quote, And Disclosure Boundary
124+
125+
Closure acceptance:
126+
127+
- source-safe AssetPack preview exposes measurements, fit reasons, selected-fit provenance, proof roots, quality posture, deterministic BTC quote, and delivery posture;
128+
- source-bearing AssetPack content remains blocked until settlement unlock;
129+
- `pnpm run check:v39-gate6` validates quote determinism, preview disclosure, leak scanning, tests, and generated evidence.
130+
131+
Closure implementation:
132+
133+
- Pending Gate 6 work must define preview/quote artifacts, disclosure tests, and deterministic quote source.
134+
135+
### Gate 7: Settlement, BTD Rights Transfer, And Delivery
136+
137+
Closure acceptance:
138+
139+
- BTC settlement observation, finality, BTD rights transfer, source-to-shares compensation, post-settlement delivery, and repair paths are auditable;
140+
- ledger, database, and object-storage projections remain synchronized or repairable;
141+
- `pnpm run check:v39-gate7` validates settlement, rights, delivery, repair, and synchronization evidence.
142+
143+
Closure implementation:
144+
145+
- Pending Gate 7 work must define settlement/delivery artifacts, receipt tests, and PR delivery repair evidence.
146+
147+
### Gate 8: Operational Telemetry, Repair, And Operator Readback
148+
149+
Closure acceptance:
150+
151+
- Reading telemetry streams source-safe phase, agent, step, Failsafe, ThricifiedGeneration, tool, storage, ledger, wallet, delivery, and UI events;
152+
- operator readback binds proof roots, runbook hooks, repair commands, and failure posture;
153+
- `pnpm run check:v39-gate8` validates telemetry contracts, UI readback, repair proof, and source-safe disclosure.
154+
155+
Closure implementation:
156+
157+
- Pending Gate 8 work must define telemetry/repair artifacts and route or component tests.
158+
159+
### Gate 9: Interface And Conversation Product Parity
160+
161+
Closure acceptance:
162+
163+
- Conversation, MCP/API, ChatGPT App, and package-facing interfaces obey the same Reading authority as Terminal;
164+
- no interface bypasses accepted-Need gating, source-safe preview, settlement unlock, BTD rights, or delivery boundaries;
165+
- `pnpm run check:v39-gate9` validates interface contract tests, Conversation handoff tests, and no-bypass posture.
166+
167+
Closure implementation:
168+
169+
- Pending Gate 9 work must define interface parity artifacts and consumer contract tests.
170+
171+
### Gate 10: Local And Staging Commercial Reading Rehearsal
172+
173+
Closure acceptance:
174+
175+
- local and staging-testnet rehearsals run the five-step Reading flow with real non-mocked inference where credentials are available;
176+
- rehearsals cover Depository search, source-safe preview, telemetry streaming/readback, ledger/database/storage synchronization, PR delivery posture, and blocked production-mainnet value-bearing admission;
177+
- `pnpm run check:v39-gate10` validates rehearsal evidence and workflow wiring.
178+
179+
Closure implementation:
180+
181+
- Pending Gate 10 work must define local/staging artifacts, credential gates, and source-safe rehearsal evidence.
182+
183+
### Gate 11: V39 Promotion Readiness
184+
185+
Closure acceptance:
186+
187+
- all V39 gates are closed;
188+
- V39 generated proof appendix support exists;
189+
- promotion workflow validates V39 and commits only the canonical pointer and generated promotion artifacts;
190+
- `pnpm run check:v39-gate11` validates promotion readiness, source-safety, generated artifacts, and V39 draft posture preparation.
191+
192+
Closure implementation:
193+
194+
- Pending Gate 11 work must define the package-backed commercial Reading promotion readiness report, V39 promotion workflow, promotion command support, generated proof appendix support, active V39 / draft V40 post-promotion posture, and blocked value-bearing mainnet evidence.

0 commit comments

Comments
 (0)