feat(config): expand live allowlist to 8 compliance-cleared assets - #135
Merged
Conversation
Wires the compliance-screened assets into the operative trading allowlist (guards.py rail 1). Adds SOL, XLM, LTC, ADA, LINK to the existing BTC/ETH/PAXG. All eight are screen-ADMITTED: attested (KB source-85/86; PAXG ayn + documented history exception) and backed by ~5yr of cached daily+hourly data. target_weights rebalanced across the 8 (sum = 1.00): BTC .30 / ETH .20 / PAXG .20 (real-asset diversifier) / SOL,XLM,LTC,ADA,LINK .06 each. Weights drive the DCA benchmark reference, not live sizing (the Turtle sizes by ATR/risk_pct). Dev config.yaml + byte-identical keel/templates/config.yaml + the live template all updated in lockstep (mode stays paper / confirm respectively; top-level keys unchanged). No logic change. SAFETY: the 5 new assets have NO live rules yet -- `keel rules seed` will create `candidate` Turtle rules that must pass backtest -> paper -> promotion before any live trade. Expanding the allowlist makes them eligible, not live. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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.
What
Wires the compliance-screened assets into the operative trading allowlist (
guards.pyrail 1 enforcesconfig.allowlist). Adds SOL, XLM, LTC, ADA, LINK to the existing BTC/ETH/PAXG → 8 assets.All eight are screen-ADMITTED: attested (KB §85/§86; PAXG
ayn+ a documented history-floor exception) with ~5yr of cached daily+hourly data.keel assets screen→ 8/8 admit.Weights
target_weightsrebalanced across the 8, summing to exactly 1.00:~70% in the established BTC/ETH/PAXG core (PAXG the real-asset diversifier, §83.10), 30% spread evenly across the five alts. Weights drive the DCA benchmark reference, not live sizing (the Turtle sizes by ATR/
risk_pct).Scope
config.yaml(dev) + byte-identicalkeel/templates/config.yaml+keel/templates/config.live.yaml— updated in lockstep. Dev staysmode: paper, live staysconfirm; top-level keys unchanged. No logic change.Safety
The 5 new assets have no live rules yet.
keel rules seed(run locally, post-merge) createscandidateTurtle rules that must pass backtest → paper → promotion before any live trade. Expanding the allowlist makes them eligible, not live.uv run pytest -q→ 1410 passed;uv run ruff check→ clean.🤖 Generated with Claude Code