CryptoLivePoolPipelines selects and publishes the monthly crypto live-pool used by QuantStrategyLab's crypto strategies. It ranks candidate symbols, decides which ones stay in the published pool and in what order, and produces the validation artifacts that downstream strategy code reads before trading on them. It does not place trades itself; it is the upstream evidence and release pipeline that other repositories depend on.
Investing involves risk. This project does not provide investment advice and is for education, research, and engineering review only.
CryptoLivePoolPipelines is the QuantStrategyLab crypto live-pool and release pipeline. It is the authority for monthly crypto live-pool membership, ordering, rankings, shadow candidate tracks, and release artifacts used by CryptoStrategies.
It is an evidence-producing repository. It does not place trades and should not be treated as an execution platform.
The trading logic lives in CryptoStrategies. This repository produces the live-pool and validation artifacts that the strategy package reads, and it owns the monthly selection and order of the published pool.
- core_major live pool artifacts
- monthly live-pool shadow validation
- external-data and candidate-track research outputs
CryptoStrategies and BinancePlatform should consume only release artifacts that pass the documented contract checks. Downstream systems should preserve live_pool.json["symbols"] order and should not rebuild the monthly pool from local indicators.
Live-pool artifacts are used to make strategy decisions reproducible: ranking inputs, live-pool snapshots, manifests, validation summaries, and promotion evidence. live_pool.json and artifact_manifest.json are the stable downstream execution contract; ranking files and research outputs stay upstream evidence unless the contract explicitly promotes them. They are not marketing claims. Before a downstream repository promotes a profile, review the latest artifacts across short, medium, and long windows where applicable.
- Layer:
pipeline. - Responsibility: crypto live-pool and release pipeline.
- Owns: monthly live-pool membership, ordering, validation artifacts.
- Consumes: market data inputs, QuantPlatformKit helpers.
- Must not: place trades or bypass downstream artifact contract checks.
After a successful monthly publication on main, an isolated review job reads that
run's published ai_review_input.md and strategy_metrics.json. It makes exactly
one single-turn OpenAI request and one single-turn Anthropic request, then posts
their reviews to the existing monthly-review issue. Defaults: 16,000 input tokens,
2,500 output tokens, 60 seconds per request, zero retries, and a $1 UTC-month budget.
Missing OPENAI_API_KEY or ANTHROPIC_API_KEY skips the API job with a clear log and
a review unavailable issue comment. See the operator runbook
for configuration, conservative input counting, and the issue-comment budget ledger.
Review results are human research input; the job cannot edit code, open remediation
PRs, change live settings, or place trades.
All approvals archive the verdict and close the issue with auto-verified. Flags
receive one deeper Dot task under existing workload grants; only confirmed problems
or severe consensus notify the owner. An independent dead-man check alerts after
three failed/skipped cycles. See the runbook for authorization and pause gaps.
src/: library and runtime code.tests/: unit, contract, and regression tests.docs/: runbooks, design notes, evidence, and integration contracts..github/workflows/: CI, scheduled jobs, release, or deployment workflows.scripts/: operator scripts and local helpers.config/: runtime or pipeline configuration.
python -m pip install -r requirements.txt
python -m pytest -qdocs/external_data_roadmap.mddocs/external_data_validation.mddocs/integration_contract.mddocs/operator_runbook.mddocs/validation_status.md
- Keep generated data, credentials, and private account details out of Git unless the artifact is intentionally public and documented.
- Prefer reproducible commands and explicit output directories.
- Do not promote a research artifact to live use without the documented validation evidence.
- See CONTRIBUTING.md for pull request scope, local verification, and documentation expectations.
- Follow CODE_OF_CONDUCT.md for maintainer and contributor conduct.
- Report credential, automation, broker, exchange, or cloud-resource vulnerabilities through SECURITY.md; do not open public issues for secrets or live-execution risk.
See LICENSE.