Add strict index ETF research and pinned promotion integration - #255
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
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.
The index ETF pilot currently uses a close-only proxy, so it cannot supply the execution and accounting evidence required for promotion. Add a strict runner for the existing two-ETF profile, using verified raw-price inputs, next-session opens, prior-volume capacity, trading limits, costs, cash and corporate-action accounting. Preserve the proxy as a synthetic learning path.
The research job validates the approved input root and frozen development/validation plan before any model call. It performs the existing bounded parameter search, retains all trials, isolates experiments by their real drift observation and resumes through QPK's persistent promotion path. The benchmark uses the same monthly decision and execution constraints. Historical declarations alone grant no trusted provenance or live authority.
Adopt the published QPK and research SDK commits in actual dependencies, lockfile and workflows. CI and evidence validation use the exact consumer pin instead of a floating source override; the five promotion-validator files remain byte-identical to the old pinned revision.
Validation: a fresh installation without PYTHONPATH overrides passed all 182 CN tests and 12 subtests with networking denied and no skips. QPK/SDK installed commit identities, dependency compatibility, pin checks, Ruff, three workflow checks, wheel/sdist builds and diff checks passed. Independent review covered strict computation, source identity, experiment isolation and the real QPK caller. Tests use synthetic inputs; no real market backtest, model request, forward shadow or live trading was performed.