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_V40.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -113,6 +113,13 @@ The package-owned `V40UnitCoverageInventory` emits `.bitcode/v40-unit-coverage-i
113
113
Rows bind package names, source roots, test paths, command ids, verdicts, and closure requirements.
114
114
Gate 3 permits no missing, blocked, or exempt critical unit surface in the artifact; any later discovered critical package unit without a direct test must reopen Gate 3 or be explicitly closed by a later V40 artifact.
115
115
116
+
## V40 Gate 4 API And Route Integration Contracts
117
+
118
+
Gate 4 closes API and route integration contract coverage beneath later browser, pipeline, synchronization, and rehearsal gates.
119
+
The package-owned `V40ApiIntegrationContracts` emits `.bitcode/v40-api-integration-contracts.json` with source-safe rows for UAPI Reading and pipeline routes, execution stream routes, Conversation routes, Auxillaries and Orbitals routes, VCS/wallet/webhook routes, public activity/template routes, package API route orchestration, package API Conversation and pipeline routes, MCP execution interface contracts, and ChatGPT App action contracts.
120
+
Rows bind route families, source roots, test paths, command ids, verdicts, and closure requirements.
121
+
Gate 4 permits no missing, blocked, or exempt critical contract row; the artifact must prove route contract coverage while withholding secrets, protected source, raw protected prompts, raw provider responses, wallet private material, and unpaid AssetPack source.
122
+
116
123
## V40 canonical subsystem surfaces
117
124
118
125
### Depositing and asset supply
@@ -372,6 +379,8 @@ V40 inherits operator-quality artifact expectations for readable proof and repai
372
379
|`.bitcode/v40-spec-family-report.json`| protocol canonical package | draft spec family validation |
Close API, UAPI, public route, MCP API, ChatGPT App, persistence, and authorization contract suites.
46
+
Gate 4 closes with package-backed `V40ApiIntegrationContracts`, deterministic `.bitcode/v40-api-integration-contracts.json`, protocol exports, source-safe rows for every critical API/interface contract surface, and `check:v40-gate4`.
Copy file name to clipboardExpand all lines: BITCODE_SPEC_V40_NOTES.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,3 +74,10 @@ Gate 3 is closed by `V40UnitCoverageInventory`.
74
74
Its generated `.bitcode/v40-unit-coverage-inventory.json` artifact binds critical unit surfaces to package names, source roots, test paths, commands, and covered verdicts.
75
75
The covered surfaces include protocol report builders, BTD ledger/settlement/right primitives, prompt composition, PTRR agents, registry-backed tools, execution lineage, generic pipelines, Reading AssetPack units, pipeline hosts, isolated interface helpers, utility packages, and the demonstration/commercial boundary.
76
76
No missing, blocked, or exempt critical unit surface is allowed in the Gate 3 artifact.
77
+
78
+
## Gate 4 implementation notes
79
+
80
+
Gate 4 is closed by `V40ApiIntegrationContracts`.
81
+
Its generated `.bitcode/v40-api-integration-contracts.json` artifact binds critical API route integration contracts to route families, source roots, test paths, command ids, and covered verdicts.
82
+
The covered surfaces include UAPI Reading/pipeline routes, execution stream routes, Conversation routes, Auxillaries/Orbitals routes, VCS/wallet/webhook routes, public activity/template routes, package API route orchestration, package API Conversation/pipeline routes, MCP execution interface contracts, and ChatGPT App action contracts.
83
+
No missing, blocked, or exempt critical API route integration contract surface is allowed in the Gate 4 artifact.
Copy file name to clipboardExpand all lines: BITCODE_SPEC_V40_PARITY_MATRIX.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ This matrix records the V40 testing surfaces that must become promotion-grade be
32
32
| Canon workflow | Canon quality knows active V39 and draft V40 |`.github/workflows/bitcode-canon-quality.yml`| drafted |
33
33
| Browser E2E | Critical website flows have browser proof | future V40 artifacts | not yet implemented |
34
34
| Visual proof | Screenshot comparisons are deterministic and reviewable | future V40 artifacts | not yet implemented |
35
-
| API integration | Route and API contracts are parseable and source-safe |future V40 artifacts | not yet implemented |
35
+
| API integration | Route and API contracts are parseable and source-safe |`.bitcode/v40-api-integration-contracts.json`| implemented |
36
36
| Pipeline integration | Primitive and real Reading pipeline implementations are tested | future V40 artifacts | not yet implemented |
37
37
| Unit coverage | Packages, primitives, isolated implementations, and real implementations have unit coverage | future V40 artifacts | not yet implemented |
38
38
| Prompt benchmark smoke | Prompt and PromptPart benchmarks run before V41 | future V40 artifacts | not yet implemented |
@@ -44,7 +44,7 @@ This matrix records the V40 testing surfaces that must become promotion-grade be
44
44
| Gate 1 | Open V40 family and check script | drafted |
45
45
| Gate 2 | Test inventory artifact and coverage matrix | implemented |
@@ -55,6 +55,7 @@ This matrix records the V40 testing surfaces that must become promotion-grade be
55
55
56
56
Gate 2 implementation evidence: package-backed `V40TestInventoryCoverageMatrix` emits `.bitcode/v40-test-inventory-coverage-matrix.json` and is wired through `check:v40-gate2`.
57
57
Gate 3 implementation evidence: package-backed `V40UnitCoverageInventory` emits `.bitcode/v40-unit-coverage-inventory.json` and is wired through `check:v40-gate3`.
58
+
Gate 4 implementation evidence: package-backed `V40ApiIntegrationContracts` emits `.bitcode/v40-api-integration-contracts.json` and is wired through `check:v40-gate4`.
- Forward planning note: V41 should focus singularly on Prompt and PromptPart implementation quality: prompts as programs. V38's inference correctness hardening and V40's testing/benchmark depth should empower V41 to examine every raw PromptPart, every Prompt composition, every benchmark, semantic partition, title, template, interpolation contract, registry binding, and inference callsite; then repartition, retitle, rewrite, catalogue, and validate them across Reading pipelines and conversational interactions. V41 should primarily harden `ReadNeedComprehensionSynthesis` and `ReadFitsFindingSynthesis` prompt surfaces while also covering conversational and other inference prompts with the same catalogue-and-benchmark discipline.
18
+
- V40 Gate 4 closure anchor: exhaustive testing now owns package-backed `V40ApiIntegrationContracts` source, deterministic `.bitcode/v40-api-integration-contracts.json`, ten source-safe covered API integration surfaces for UAPI Reading/pipeline routes, execution stream routes, Conversation routes, Auxillaries/Orbitals routes, VCS/wallet/webhook routes, public activity/template routes, package API route orchestration, package API Conversation/pipeline routes, MCP execution interface contracts, and ChatGPT App action contracts, protocol exports, package tests, workflow wiring, and `check:v40-gate4`.
19
+
- Forward planning note: V41 should focus singularly on Prompt and PromptPart implementation quality: prompts as programs. V38's inference correctness hardening and V40's testing/benchmark depth should empower V41 to examine every raw PromptPart, every Prompt composition, every benchmark, meaningfully benchmarkable semantic part, title, template, interpolation contract, registry binding, and inference callsite; then repartition, retitle, rewrite, catalogue, and validate them across Reading pipelines and conversational interactions. V41 should primarily harden `ReadNeedComprehensionSynthesis` and `ReadFitsFindingSynthesis` prompt surfaces while also covering conversational and other inference prompts with the same catalogue-and-benchmark discipline.
19
20
- V34 Gate 2 closure anchor: deployment-depth now owns package-backed `DeploymentHostCapabilityCatalog` and `EnvironmentLaneContract` source, deterministic `.bitcode/v34-deployment-host-capability-catalog.json` and `.bitcode/v34-environment-lane-contracts.json`, and visible `value-bearing-mainnet` blocking through `blocked_future_canon_required`.
20
21
- V34 Gate 3 closure anchor: deployment-depth now owns package-backed `DistributedExecutionRuntimeReceipt` source, deterministic `.bitcode/v34-distributed-execution-runtime-receipts.json`, `request_response_not_required` long-running work posture, and source-safe roots for pipeline, PTRR agent, ThricifiedGeneration, tool, ledger, wallet, proof, object-storage, and repair work.
21
22
- V34 Gate 4 closure anchor: deployment-depth now owns package-backed `DeploymentStoragePosture` source, deterministic `.bitcode/v34-deployment-storage-posture.json`, ledger/database/object-storage drift repair fixtures, retention/encryption/backup/rollback/audit posture, and source-bearing AssetPack storage remains locked before settlement.
@@ -135,7 +136,7 @@ They are referenced here for specification history only; active implementation w
135
136
| V38 |`BITCODE_SPEC_V38.md`| promoted historical Bitcode canon | Inference correctness after V37: pipeline execution call stack, PTRR agents, FailsafeGenerationSequence over ThricifiedGeneration, prompt registry composition, PromptPart and Prompt benchmarking, Reading pipeline inference, ReadFitsFindingSynthesis depository search and embeddings, source-safe inference telemetry, local/staging rehearsal, and promotion readiness. |
136
137
| V39 |`BITCODE_SPEC_V39.md`| active canon | Commercial Reading readiness after V38: Depository supply indexing, enterprise five-step Reading UX, ReadNeed review/resynthesis, ReadFitsFinding many-candidate runtime and replay, source-safe AssetPack preview and deterministic BTC quote, settlement, BTD rights transfer, post-settlement delivery, ledger/database/storage synchronization, operational telemetry/repair, interface parity, local/staging rehearsal, and promotion readiness. |
137
138
| V40 |`BITCODE_SPEC_V40.md`| active draft target | Exhaustive commercial application testing depth after V39: rich browser E2E for all website interactions and state possibilities, visual/screenshot comparison coverage, API and integration suites for pipelines, conversations, routes, ledger/database/storage synchronization, and unit coverage for packages, primitives, isolated implementations, and real commercial implementations. |
138
-
| V41 | future draft target after V40 | planned | Prompt and PromptPart excellence, treating prompts as programs: audit every raw PromptPart and composed Prompt, run and harden benchmarks, repartition prompts into benchmarkable semantic parts, retitle and rewrite PromptParts/Prompts where optimal, catalogue registry bindings and interpolation contracts, and elevate all Reading and Conversation inference points after V38 inference scaffolding and V40 testing depth make that work measurable. The primary surface is Reading, especially `ReadNeedComprehensionSynthesis` and `ReadFitsFindingSynthesis`; conversations and other inference prompts follow with the same benchmarkable catalogue discipline. |
139
+
| V41 | future draft target after V40 | planned | Prompt and PromptPart excellence, treating prompts as programs: audit every raw PromptPart and composed Prompt, run and harden benchmarks, repartition prompts into meaningfully benchmarkable semantic parts, retitle and rewrite PromptParts/Prompts where optimal, catalogue registry bindings and interpolation contracts, and elevate all Reading and Conversation inference points after V38 inference scaffolding and V40 testing depth make that work measurable. The primary surface is Reading, especially `ReadNeedComprehensionSynthesis` and `ReadFitsFindingSynthesis`; conversations and other inference prompts follow with the same benchmarkable catalogue discipline. |
139
140
140
141
## Current Planning Spine
141
142
@@ -154,7 +155,7 @@ They are referenced here for specification history only; active implementation w
154
155
13. V38 promoted inference correctness, Reading pipeline search, prompt benchmarking, source-safe inference telemetry, and the practical PTRR/Failsafe/Thricified call stack.
15. V40 is the current draft target and hardens exhaustive testing for the rich commercial application: E2E, visual, screenshot comparison, interaction/state matrices, integration, and unit coverage across the website, APIs, pipelines, conversations, packages, primitives, and real implementations.
157
-
16. V41 is the planned prompts-as-programs target after V40: every PromptPart, Prompt composition, benchmark, semantic division, title, template, interpolation contract, registry binding, and inference callsite should be examined and improved across Reading and Conversation inference, using V38's inference correctness scaffolding and V40's testing/benchmarking depth as the measurement base.
158
+
16. V41 is the planned prompts-as-programs target after V40: every PromptPart, Prompt composition, benchmark, meaningfully benchmarkable semantic division, title, template, interpolation contract, registry binding, and inference callsite should be examined and improved across Reading and Conversation inference, using V38's inference correctness scaffolding and V40's testing/benchmarking depth as the measurement base.
0 commit comments