Investing involves risk. This project does not provide investment advice and is for education, research, and engineering review only.
UsEquitySnapshotPipelines is the QuantStrategyLab US equity snapshot and evidence pipeline. It builds feature snapshots, backtest summaries, rankings, and promotion evidence for US equity strategies.
It is an evidence-producing repository. It does not place trades and should not be treated as an execution platform.
Direct runtime strategies such as ETF rotation, TQQQ/SOXL profiles, and Smart DCA live in UsEquityStrategies; this repository only prepares data and evidence for profiles that need snapshot artifacts or candidate review.
- Russell 1000 Multi-Factor Defensive
- Mega Cap Leader Rotation Top50 Balanced
- Tech/Communication Pullback Enhancement research artifacts
- candidate ranking and replacement-review research outputs
UsEquityStrategies and US execution platforms consume only promoted artifacts and runtime-enabled profiles.
Snapshot artifacts are used to make strategy decisions reproducible: ranking inputs, feature snapshots, manifests, validation summaries, and promotion evidence. They are not marketing claims. Before a downstream repository promotes a profile, review the latest artifacts across short, medium, and long windows where applicable.
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.
python -m pip install -e .
python -m pytest -qdocs/artifact_contract.mddocs/crisis-context-research-v2.mddocs/crisis-response-live-promotion-spec.mddocs/crisis-response-research-roadmap.mddocs/crisis-response-v1.mddocs/leveraged-strategy-candidate-research.mddocs/live-strategy-optimization-feedback-20260603.mddocs/mega-cap-leader-rotation-dynamic-validation.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.