Repository navigation
Document the champion's context length, and seeding a live miner's store - #26
Merged
Merged
Conversation
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.
Tip: disable this comment in your organization's Code Review settings.
Thykof
force-pushed
the
docs/context-days
branch
from
November 9, 2026 10:55
903b6e8 to
9fc749d
Compare
…ive miner's store From campaign-7 a champion's modeling.py may set CONTEXT_DAYS, an int from 3 to 30, 7 when absent. deploy-a-champion.md describes it and how to read it, and its price-store section now says what a deployed miner needs: CONTEXT_DAYS + 1 days, Binance-routed assets from the venue, and Hyperliquid-routed ones beyond about 3.5 days seeded from the archive with scripts/ingest_reservoir.py before the miner first starts, on an empty store. scoring.md, the verdict section of operate-a-campaign.md, reproduce.md and install-and-first-run.md replace the fixed 7 days with CONTEXT_DAYS. The CHANGELOG lists the context length as landing with the next synth-lib pin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016kmUsyYSEMPGiwbSuvR9hh
…pion's own store operate-a-campaign.md: the loader requires a partition for every day after an asset's first one, and days before it are NaN. Generation starts one horizon before the window, so the store needs every day from CONTEXT_DAYS + 1 days before --window-start, and audit_store.py takes --require-from <window start - CONTEXT_DAYS - 1 day>. predict.py prints `summary (CONTEXT_DAYS N):`, and the interface check's note starts with `ok (24h + 1h), CONTEXT_DAYS N`. deploy-a-champion.md runs the seed and the miner from the champion's own folder, so its market_data/ is apart from the campaign store. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016kmUsyYSEMPGiwbSuvR9hh
Thykof
force-pushed
the
docs/context-days
branch
from
November 9, 2026 10:56
9fc749d to
5ecec2c
Compare
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.
Stacked on #25. Engine side: synthdataco/synth-lib#91.
Why
From campaign-7 a champion chooses its context length. Its
modeling.pymay setCONTEXT_DAYS, aplain integer from 3 to 30; without it the champion gets 7 days, as every archived champion does.
The agent's backtests, the interface check, the verdict and the live miner read the same value. The
engine side lands in a companion synth-lib PR and reaches this repo with the next pin. This PR
documents it for operators and for anyone deploying a champion.
The deploy guide matters most. A deployed miner needs
CONTEXT_DAYS + 1days in its store, andHyperliquid serves only its last 5,000 minutes, about 3.5 days. Unseeded, a 30-day champion would
serve its 9 Hyperliquid-routed assets from about 3.5 real days, gaining one a day, for four weeks.
Stacked on
build/antigravity-cli.Merge order. This PR merges after the synth-lib stack, once a pin-bump commit to the merged
synth-lib lands on
build/kimi-code-2. The pin it sits on today has noCONTEXT_DAYScode, sothese docs describe the engine that bump brings.
What
docs/deploy-a-champion.mdCONTEXT_DAYS; the price-store section rewritten (below)docs/scoring.mdCONTEXT_DAYS, 7 when unsetdocs/operate-a-campaign.mdCONTEXT_DAYS(below); the loader's NaN head; the interface-check notedocs/reproduce.mddocs/install-and-first-run.mdsummaryline and interface-check noteCHANGELOG.mdWhat
operate-a-campaign.mdnow says about the verdict's prices:CONTEXT_DAYSdays per prompt, 7 when unset. The loaderrequires a partition for every day after the asset's first one; days before it are NaN.
window start -
CONTEXT_DAYS- 1 day. The store needs every day from there, for the largestCONTEXT_DAYSamong the legs scored, and the audit runs with--require-from <window start - CONTEXT_DAYS - 1 day>.CONTEXT_DAYSdays up tot.ok (24h + 1h), CONTEXT_DAYS N.What
deploy-a-champion.mdnow says about the store:CONTEXT_DAYS + 1daily partitions: a D-day window touches D + 1, the oldestand today's both partial.
old pre-warm loop with
market_data --days 30is gone.CONTEXT_DAYSabove 3,seed the store with
scripts/ingest_reservoir.pyfor theCONTEXT_DAYS + 1days up toyesterday. 31 days covers any champion.
cd champions/<name>, theseed as
uv run python ../../scripts/ingest_reservoir.py ..., then./entrypoint.sh. Itsmarket_data/is then apart from the campaign store in the repo root, anduvstill finds therepo's project.
settled, and the miner never fetches a settled day again.
campaign, another champion or an older engine keeps its old days.
miner starts.
Tests
uv run black --check .uv run pytest -qDocs only. The
summary (CONTEXT_DAYS N):line and the interface-check note were checked againstthe synth-lib PR's
predict.pyandnomination.py, and the window lead-in against itsrun_verdict.generation_start. Re-read the engine claims against that PR before merging this one.🤖 Generated with Claude Code
https://claude.ai/code/session_016kmUsyYSEMPGiwbSuvR9hh