Gate 7 reading pipeline coverage criteria#12
Merged
geraldarthurdavis merged 7 commits intoMay 19, 2026
Conversation
Add the focused Read-Need and Need-Fit test contract to the V28 gate criteria, including typed phase/agent/tool/step/substep mock requirements and the rule that specification, tests, and core algorithmic design must move together.
|
Deployment failed with the following error: |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Specify the ReadNeedComprehensionSynthesis and ReadFindingFitsSynthesis contracts with PTRR agents, ThricifiedGeneration ids, prompt registry metadata, and V28 parity/QA coverage. Implement bounded ThricifiedGeneration telemetry for Reading inference, source-safe Finding Fits admission, richer pipeline harness stream metadata, and default Terminal visibility for the five enterprise Reading steps. Expand asset-pack, harness, protocol, and UAPI tests for Read-Need synthesis, Finding Fits discovery, source-safe preview, stream telemetry, and local Terminal browser/build readiness.
Normalize common real-model response variance in Reading inference outputs while keeping PTRR ThricifiedGeneration telemetry typed and auditable. Coerce scalar list fields into arrays and fail closed on nonnumeric confidence or quality labels returned by live OpenAI runs so local staging Read-Need synthesis can complete without weakening the contract.
Update the V28 parity matrix and QA ledger with current local OpenAI, Terminal browser, REST readback, and DB readback validation for the Reading pipelines. Mark the bounded ReadNeedComprehensionSynthesis and ReadFindingFitsSynthesis gate surfaces closed where the source-bound staging-testnet verifier now proves telemetry, Finding Fits, AssetPack delivery, settlement, and ledger/database synchronization.
Carry the verified source-bound Reading run back into the high-level V28 staging parity rows so Fit-finding, pipeline runtime, telemetry, BTC fee, ledger, and database readback no longer contradict the detailed Gate 7 closure evidence. Leave unrelated V28 promotion blockers, including MCP/ChatGPT parity and broad ledgerized model-selection cleanup, explicitly outside this gate closure.
Resolve Gate 6 to Gate 7 conflicts after registry access policy landed on version/v28. The resolution preserves Gate 7's BTD exports and Jest module mappers while adopting Gate 6's BTD typecheck script and newer Jest dependency ranges. The lockfile remains frozen-consistent.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@bitcode/btd/terminal-operational-health, built from existing BTD primitives for deployment lanes, telemetry, upgrades, receipts, ranges, ledger anchors, journals, and reconciliationValidation
pnpm -C packages/btd testpnpm -C uapi exec jest --runTestsByPath tests/terminalOperationalHealthPanel.test.tsx tests/terminalPageShell.test.tsx --runInBandpnpm -C packages/pipelines/asset-pack exec jest --runTestsByPath src/__tests__/read-need.test.ts src/__tests__/depository-search.test.ts src/__tests__/depository-search-tool.test.ts --runInBandpnpm -C packages/pipeline-hosts exec jest --runTestsByPath src/__tests__/asset-pack-harness.test.ts src/__tests__/manifest.test.ts src/__tests__/vercel-sandbox-host.test.ts --runInBandpnpm -C uapi exec jest --runTestsByPath tests/api/readReviewRoute.test.ts tests/api/pipelineHarnessRoute.test.ts tests/api/pipelineHarnessPreflight.test.ts tests/terminalPipelineHarnessClient.test.ts tests/searchRelevantAssetPackEvidence.test.ts tests/terminalOperationalHealthPanel.test.tsx --runInBandpnpm -C protocol-demonstration test:fit-findingnode --test scripts/verify-v28-pipeline-readback.test.mjspnpm -C uapi exec tsc --noEmit --pretty falsepnpm -C uapi buildpnpm run check:canon-posture-driftnode scripts/check-bitcode-spec-family.mjs --version V28 --mode draft --current-target V27 --skip-pointer-checkgit diff --checkKnown Existing Caveat
pnpm run check:spec-familyandnode scripts/run-bitcode-spec-quality.mjs --mode strict-version --version V28still fail before V28 validation because the current promoted V27 spec family is missing required appendix/proof-family entries. The V28 draft-family check above passes.