|
2 | 2 |
|
3 | 3 | [Chinese README](README.zh-CN.md) |
4 | 4 |
|
5 | | -> ⚠️ Investing involves risk. This project does not provide investment advice and is for educational and research purposes only. |
| 5 | +> Investing involves risk. This project does not provide investment advice and is for education, research, and engineering review only. |
6 | 6 |
|
7 | | -## What this project does |
| 7 | +## What this repository is |
8 | 8 |
|
9 | | -QuantRuntimeSettings is a **Runtime configuration package** in the QuantStrategyLab ecosystem. It defines schemas and tooling for shared QuantStrategyLab runtime settings. |
| 9 | +QuantRuntimeSettings is a QuantStrategyLab runtime settings package. It defines schemas and tooling for versioned runtime settings shared across QuantStrategyLab platforms. |
10 | 10 |
|
11 | | -## Who this is for |
| 11 | +It supports the system but does not decide which strategy should be live. Strategy eligibility remains in the strategy and snapshot repositories; broker execution remains in the platform repositories. |
12 | 12 |
|
13 | | -- Engineers and researchers who want to inspect, reproduce, or extend this part of the QuantStrategyLab stack. |
14 | | -- Operators who need a clear entry point before reading the deeper runbooks or workflow files. |
15 | | -- Reviewers who need to understand the repository purpose, safety boundary, and evidence requirements before enabling automation. |
| 13 | +## Design boundary |
16 | 14 |
|
17 | | -## Current status |
18 | | - |
19 | | -Shared configuration contract; changes can affect multiple platforms. |
| 15 | +- Keep contracts stable and versioned where downstream repositories depend on them. |
| 16 | +- Prefer backward-compatible changes unless a coordinated migration is planned. |
| 17 | +- Keep secrets and environment-specific settings outside the shared library code. |
| 18 | +- Document changes that affect multiple platforms or strategy packages. |
20 | 19 |
|
21 | 20 | ## Repository layout |
22 | 21 |
|
23 | | -- `tests/`: unit and contract tests. |
24 | | -- `.github/workflows/`: CI, scheduled jobs, and deployment workflows. |
| 22 | +- `tests/`: unit, contract, and regression tests. |
| 23 | +- `.github/workflows/`: CI, scheduled jobs, release, or deployment workflows. |
25 | 24 | - `scripts/`: operator scripts and local helpers. |
26 | 25 |
|
27 | 26 | ## Quick start |
28 | 27 |
|
29 | | -From a fresh clone: |
30 | | - |
31 | 28 | ```bash |
32 | 29 | python -m pip install -e . |
33 | 30 | python -m pytest -q |
34 | 31 | ``` |
35 | 32 |
|
36 | | -If a command requires credentials, run it only after reading the relevant workflow or runbook and configuring secrets outside Git. |
37 | | - |
38 | | -## Deployment and operation |
39 | | - |
40 | | -Use the schemas in platform repositories and CI validation. Roll out setting changes through review, dry-run validation, and controlled platform deployment. |
41 | | - |
42 | | -Prefer manual or dry-run execution first. Enable schedules or live execution only after logs, artifacts, permissions, and rollback steps are reviewed. |
43 | | - |
44 | | -## Strategy performance and evidence |
45 | | - |
46 | | -Not a strategy repository. Quality is measured by compatibility, validation coverage, and reducing configuration mistakes. |
47 | | - |
48 | | -README files are intentionally not a source of dated performance promises. Re-run the relevant tests, backtests, or pipeline jobs before relying on any result. |
49 | | - |
50 | | -## Safety notes |
51 | | - |
52 | | -- Never commit API keys, broker credentials, OAuth tokens, cookies, or account identifiers. |
53 | | -- Run new strategies and platform changes in dry-run or paper mode before any live execution. |
54 | | -- Review generated orders, artifacts, and logs manually before enabling schedules. |
55 | | - |
56 | | -## Contributing |
| 33 | +## Useful docs |
57 | 34 |
|
58 | | -Keep changes small, reproducible, and covered by the narrowest useful tests. For strategy-facing changes, include the evidence artifact or command used to validate behavior. |
| 35 | +- No separate `docs/` directory yet; start with this README and the workflow files. |
59 | 36 |
|
60 | 37 | ## License |
61 | 38 |
|
62 | | -See [LICENSE](LICENSE) if present in this repository. |
| 39 | +See [LICENSE](LICENSE). |
0 commit comments