You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: BITCODE_SPEC_V30.md
+22Lines changed: 22 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -349,6 +349,28 @@ The focused Playwright spec proves the cockpit in a real browser in deterministi
349
349
Gate 9 acceptance does not change Reading law, source disclosure law, settlement law, or organization authority law.
350
350
It makes the current V30 Terminal cockpit commercially operable enough that later local/staging promotion readiness can debug failures from the UI rather than from browser network logs alone.
351
351
352
+
### Gate 9 interface integration regression proof
353
+
354
+
Gate 9 adds a package-owned proof that current interface surfaces consume the
Copy file name to clipboardExpand all lines: BITCODE_SPEC_V30_NOTES.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -251,6 +251,22 @@ boundary exposes `/btd/protocol-telemetry` as a JSON-safe proof-admission route;
251
251
it does not commit source-bearing artifacts, and it does not replace existing
252
252
crypto telemetry rows used for deployment readiness health.
253
253
254
+
## Gate 9 interface integration notes
255
+
256
+
Gate 9 makes interface reuse explicit. The accepted package shape is
257
+
`BtdInterfaceIntegrationRegressionProof` plus the browser-safe
258
+
`@bitcode/btd/interface-integration-contract` subpath. Terminal uses the
259
+
contract without importing storage-backed BTD entry points into the client.
260
+
API uses `buildBtdInterfaceIntegrationRegressionSettlement` and exposes
261
+
`/btd/interface-integration-regression` as a JSON-safe proof-admission route.
262
+
MCP and ChatGPT App expose small adapter records that name their package-owned
263
+
BTD object consumption.
264
+
265
+
The proof is not a new user journey. It is regression evidence that the V30
266
+
rails can be consumed by current interfaces without losing low-detail source
267
+
safety, reintroducing route-local BTD policy copies, or changing the selected
268
+
Terminal transaction behavior promoted in V29.
269
+
254
270
## Gate 1 working notes
255
271
256
272
Gate 1 is complete only when the V30 family exists, validates in draft mode over active V29, and makes the roadmap truthful enough to drive V31 through V37 without stale V27/V28/V29 posture.
| Promotion readiness | Gate 10 | V30 promotion workflow, generated `.bitcode/v30-*`, `BITCODE_SPEC_V30_PROVEN.md`| pending |`version/v30` can promote to `main` only after all V30 checks pass and promotion automation can commit generated canon. |
67
67
68
68
## V30 implementation checklist
@@ -229,6 +229,25 @@ No `_legacy/` source is active source truth.
229
229
- Gate 8 may expose telemetry/proof hooks to Terminal/API callers for operator review.
230
230
- Gate 8 does not promote V30 or change the active canon pointer.
231
231
232
+
## Gate 9 Parity
233
+
234
+
| Requirement | Source evidence | Current V30 judgment |
- Gate 9 does not redesign Reading, settlement, source disclosure, organization authority, MCP, ChatGPT App, Auxillaries, or Exchange.
246
+
- Gate 9 does not expose protected AssetPack source, prompts, raw source, private keys, service keys, model keys, JWT-looking secrets, or database passwords.
247
+
- Gate 9 admits only source-safe interface integration records and a proof-admission route; it does not commit ledger state or deliver AssetPacks.
248
+
- Gate 9 proves current interfaces consume package-owned BTD object families without route-local policy copies.
249
+
- Gate 9 does not promote V30 or change the active canon pointer.
250
+
232
251
## completion condition
233
252
234
253
Gate 1 is complete when the V30 draft family validates, `check:v30-gate1` passes, workflow posture is V30-aware, README and roadmap reflect V30 initiation, V31-V37 scopes are current enough to guide future gates, diff hygiene passes, and the gate branch is committed and pushed for review into `version/v30`.
0 commit comments