CryptoLivePoolPipelines

Chinese README

Investing involves risk. This project does not provide investment advice and is for education, research, and engineering review only.

What this repository is

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.

Strategy and evidence boundary

Direct runtime strategies

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.

Snapshot-backed work handled here

• core_major live pool artifacts
• monthly live-pool shadow validation
• external-data and candidate-track research outputs

Downstream use

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.

What the artifacts are for

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.

Repository layout

• 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.

Quick start

python -m pip install -r requirements.txt
python -m pytest -q

Useful docs

• docs/external_data_roadmap.md
• docs/external_data_validation.md
• docs/integration_contract.md
• docs/operator_runbook.md
• docs/validation_status.md

Safety and contribution notes

• 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.

Community and security

• 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.

License

See LICENSE.