Drop the four CBOE implied-vol indices from the registry - #19
Merged
Conversation
VIX, VXN, OVX and GVZ were fetchable but nothing kept them. The workspace notes had recorded them as "deliberately let go" since July while they sat here in the registry, so every unscoped `--bars --domain equities` fetched them straight back. That is what happened on 2026-08-20: a new scheduled equities task ran unscoped, the four reappeared, and the whole equities half moved forward a month on every replica. The prose and the registry disagreed, and the registry is what runs. Removing them here is the only thing that actually stops it. Scoping the producer task would fix that one caller; any other unscoped fetch, from any checkout, would undo it. CONSEQUENCE, recorded in the file rather than left to be discovered: npf/trading_riot maps all four to a realized counterpart (VIX->ES, VXN->NQ, OVX->CL, GVZ->GC) for a variance risk premium study, and its data.py documents fetching them with `--bars --symbols VIX`. That command now prints "no registry symbols resolve to this provider" and exits 0 having written nothing, which is a silent no-op rather than an error. Re-adding the block is the fix if that work resumes; the note in registry.yaml says so at the point someone would look. Store side is already done on the producer: the four parquets and their manifest entries are gone, leaving 11 equities symbols, which is what this registry now lists. Suite 200 passed, 12 skipped, ruff clean. The month-end pin is untouched: the frozen copy never carried these. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Aug 21, 2026
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.
VIX,VXN,OVXandGVZwere fetchable but nothing kept them. The workspace notes had recorded them as "deliberately let go" since July while they sat here in the registry, so every unscoped--bars --domain equitiesfetched them straight back.That is what happened on 2026-08-20: a new scheduled equities task ran unscoped, the four reappeared, and the whole equities half moved forward a month on every replica. The prose and the registry disagreed, and the registry is what runs.
Removing them here is the only thing that actually stops it. Scoping the producer task fixes that one caller; any other unscoped fetch, from any checkout, would undo it.
Consequence, recorded in the file rather than left to be discovered
npf/trading_riotmaps all four to a realized counterpart for a variance risk premium study:and its
data.pydocuments fetching them with--bars --symbols VIX. After this change that command is a silent no-op:Exit 0, nothing written. So the note left in
registry.yamlsays exactly this, at the point someone would look, and says re-adding the block is the fix if that work resumes.trading_riotis not scheduled and not imported bysrc/, so this is a bench dependency rather than a running book, but it is a real one.Verification
Matches the producer store, which already has the four parquets and their manifest entries removed. Suite 200 passed, 12 skipped, ruff clean. The month-end pin is untouched: the frozen copy never carried these.
Coordination note
The same edit already exists locally on the Windows producer and was never pushed. Once this merges, that checkout should be reset onto
origin/mainrather than pushing its own version, or the two will diverge on the same file.🤖 Generated with Claude Code