Repository navigation
fix: align validation console with Evidence State v2 - #32
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
chin0312
force-pushed
the
codex/console-v2-semantics
branch
from
October 6, 2026 18:03
aef5fab to
c29695c
Compare
chin0312
force-pushed
the
codex/console-v2-semantics
branch
from
October 6, 2026 18:52
c29695c to
b5236cc
Compare
chin0312
force-pushed
the
codex/console-v2-semantics
branch
from
October 6, 2026 19:07
b5236cc to
88f8328
Compare
chin0312
force-pushed
the
codex/console-v2-semantics
branch
from
October 6, 2026 19:29
88f8328 to
edd83f6
Compare
This branch was successfully deployed
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
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
PR #23 has been merged. Production assets are NVDAx, SPYx, and AAPLx; QQQx and TSLAx remain research-only.
This PR keeps the approved Evidence State v2 backend contract and completes its human-facing Console integration:
Evidence State v2 mapping
James's frozen SUPPORT/WATCH/REVIEW bands, model fits, calibration, q80/q95 thresholds, and research outputs are unchanged.
Research evidence
The following are James's original frozen exposed-test results, not fresh-panel metrics:
The exact fresh canonical CSV bytes were unavailable locally, so the full fresh SUPPORT-band truth metrics were not independently recomputed. This is a follow-up validation limitation, not a merge blocker: the frozen research bands and thresholds are unchanged, and the removed X-Perp directional preference within SUPPORT was not part of James's validated detector rule.
The expected v2 panel totals below are arithmetic derivations from committed frozen aggregates, not a new row-level replay:
Publisher safety
Publisher compatibility expects v2 and checks the result's evidence_semantics explicitly. Existing deployment bindings do not declare v2 publication compatibility, so writes remain fail-closed. This PR does not change deployment manifests, contracts, or publication configuration; no transaction was sent.
Validation
npm test: 53 passed.npm run build: TypeScript and Vite production build passed; existing large-chunk advisory remains.Scope
Only
apps/web/**changed. CSS, frontend layout system, backend, quant artifacts, docs, contracts, deployments, Landing, Docs, and Methodology were not changed. No production deployment or mutation was performed.