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_V39.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,6 +120,14 @@ artifact is `.bitcode/v39-enterprise-reading-ux-state.json`, checked by
120
120
Gate 4 makes `ReadNeedComprehensionSynthesis` a real review loop.
121
121
It must persist Read Requests, synthesized Needs, feedback, resynthesis attempts, Need measurements, accepted-Need admission, rejected-Need posture, and telemetry receipts.
122
122
Finding Fits remains blocked until a reviewed Need is accepted.
123
+
The implementation basis is `ReadNeedReviewResynthesisRuntime`, exported from
124
+
`packages/pipelines/asset-pack/src/read-need-review-resynthesis.ts`. It projects
125
+
source-safe storage records for `read_request`, `synthesized_need`, `feedback`,
Copy file name to clipboardExpand all lines: BITCODE_SPEC_V39_NOTES.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -201,6 +201,12 @@ state tests, component tests, and the maintained opt-in browser proof workflow.
201
201
## Gate 4 implementation notes
202
202
203
203
Gate 4 closes `ReadNeedComprehensionSynthesis` as a review, feedback, and resynthesis loop. Finding Fits remains blocked until a reviewed Need is accepted.
204
+
The implementation centers on `ReadNeedReviewResynthesisRuntime`: it persists
205
+
Read Requests, synthesized Needs, feedback history, resynthesis attempts, Need
206
+
measurements, accepted-Need admission, rejected-Need posture, and source-safe
207
+
telemetry receipts as PipelineExecution-compatible storage projections. The
208
+
rejected-Need posture is explicit so operator feedback can drive resynthesis
| ReadNeed review and resynthesis | Gate 4 |`ReadNeedComprehensionSynthesis`, Need storage, feedback, resynthesis, accepted-Need admission|pending| Finding Fits remains blocked until a reviewed Need is accepted. |
75
+
| ReadNeed review and resynthesis | Gate 4 |`packages/pipelines/asset-pack/src/read-need-review-resynthesis.ts`, `.bitcode/v39-read-need-review-resynthesis.json`, package tests, route tests, protocol tests|implemented| Finding Fits remains blocked until a reviewed Need is accepted; rejected Needs preserve feedback and stay blocked. |
76
76
| ReadFitsFinding runtime and replay | Gate 5 |`ReadFitsFindingSynthesis`, search tools, embeddings, ranking, selected-fit provenance, replay receipts | pending | Finding Fits searches the whole available Depository for many above-threshold candidates. |
| Read Requests and synthesized Needs persist as source-safe storage projections |`ReadNeedReviewStorageRecord`, `read_request`, `synthesized_need`, `need_measurement` records | implemented |
158
+
| Feedback and resynthesis lineage are preserved |`resynthesis_attempt` record, `previousNeedId`, `feedbackHistory`, route resynthesis tests | implemented |
159
+
| Accepted Need is the only Finding Fits admission path |`acceptReadNeed`, `admitReadFitsFinding`, `accepted_need_admission`, route acceptance tests | implemented |
Later V39 gates must add gate-specific parity sections when their implementation begins. Gates 1 through 3 intentionally do not claim closure for Need review, Finding Fits runtime, preview/quote, settlement/delivery, telemetry/repair, interface parity, rehearsal, or promotion readiness.
168
+
Later V39 gates must add gate-specific parity sections when their implementation begins. Gates 1 through 4 intentionally do not claim closure for Finding Fits runtime, preview/quote, settlement/delivery, telemetry/repair, interface parity, rehearsal, or promotion readiness.
155
169
156
170
## accepted boundaries and reopen conditions
157
171
158
172
V39 Gate 1 accepts only draft-family, roadmap, workflow, branch, and documentation posture closure.
159
173
V39 Gate 2 accepts only Depository supply indexing, source-safe search document, vector projection, storage readback posture, rights boundary, repair posture, and Finding Fits handoff closure.
Later gate scope is intentionally pending and must be reopened into gate-specific parity sections before implementation starts.
162
177
163
178
## completion condition
164
179
165
-
V39 Gate 3 is complete when `check:v39-gate3`, focused Terminal/Conversation/UAPI tests, V39 draft spec-family validation, V38/V39 canon-posture drift validation, and promoted V38 spec-family validation all pass on a `v39/gate-3-*` branch.
180
+
V39 Gate 4 is complete when `check:v39-gate4`, focused ReadNeed package and route tests, V39 draft spec-family validation, V38/V39 canon-posture drift validation, and promoted V38 spec-family validation all pass on a `v39/gate-4-*` branch.
- 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`.
@@ -63,6 +63,7 @@
63
63
- V39 Gate 1 opening anchor: Commercial Reading readiness opens over promoted V38 with V39 SPEC, DELTA, NOTES, and PARITY files, `check:v39-gate1`, V38 active / V39 draft posture, and an eleven-gate plan for Depository supply indexing, enterprise Reading UX state, ReadNeed review/resynthesis, ReadFitsFinding runtime and replay, AssetPack preview/quote disclosure, settlement/BTD rights/delivery, operational telemetry/repair, interface parity, local/staging rehearsal, and promotion readiness.
0 commit comments