You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/deployment_model.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
5
5
-`QuantPlatformKit` remains the shared platform package and is **not deployed as a runtime service**.
6
6
- The current runtime repositories (`InteractiveBrokersPlatform`, `CharlesSchwabPlatform`, `LongBridgePlatform`, `BinancePlatform`) are the **transitional deployment units**.
7
-
- The **target state** is one deployment repository per broker platform, with strategy behavior selected through `RuntimeTarget` / `RUNTIME_TARGET_JSON` and compatibility selectors such as `STRATEGY_PROFILE`.
7
+
- The **target state** is one deployment repository per broker platform, with structured runtime identity carried through `RuntimeTarget` / `RUNTIME_TARGET_JSON` and `STRATEGY_PROFILE` retained only as a compatibility routing selector.
8
8
- Strategy or platform repositories should always depend on a fixed `QuantPlatformKit` Git tag instead of `main`.
9
9
10
10
For the live runtime inventory across repositories, projects, services, schedulers, runtime identities, and current secret names, see [`platform_runtime_inventory.md`](./platform_runtime_inventory.md).
@@ -152,7 +152,7 @@ Within one broker platform repository, selecting a strategy by configuration is
152
152
Recommended selector:
153
153
154
154
-`RUNTIME_TARGET_JSON` for structured runtime identity
155
-
-`STRATEGY_PROFILE` for compatibility with existing strategy routing
155
+
-`STRATEGY_PROFILE`only for compatibility with existing strategy routing
-region token secrets selected by `LONGPORT_SECRET_NAME`
109
+
-account token secrets selected by `LONGPORT_SECRET_NAME`
108
110
- runtime Telegram token secret
109
111
-**Runtime notes**
110
-
-HK and SG keep two independent Cloud Run services, two triggers, and two GitHub Environments.
112
+
-PAPER and SG are live today; HK keeps the same deployment pattern when it is added. Each account identity gets its own Cloud Run service, trigger, and GitHub Environment.
Copy file name to clipboardExpand all lines: docs/platform_strategy_matrix.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ For strategy behavior, research status, and archived backtest evidence, see
18
18
- There are currently two strategy domains:
19
19
-`us_equity`
20
20
-`crypto`
21
-
- Runtime repositories now expose `RUNTIME_TARGET_JSON`plus `STRATEGY_PROFILE`; this is **not** a full multi-strategy marketplace yet.
21
+
- Runtime repositories now expose `RUNTIME_TARGET_JSON`as the primary structured runtime identity, with `STRATEGY_PROFILE` kept as a compatibility routing selector; this is **not** a full multi-strategy marketplace yet.
22
22
- Today, each US equity platform can switch among the `runtime_enabled``us_equity` profiles published by `UsEquityStrategies`, subject to each platform's rollout configuration.
23
23
- Platform runtime adapters are generated from strategy input/target-mode declarations plus platform capabilities, so new in-contract profiles should not need per-platform allowlist edits.
24
24
- The shared contract is in `QuantPlatformKit`; real `us_equity` strategy implementations now live in `UsEquityStrategies`, while platform repositories own runtime adapters and broker execution.
@@ -29,7 +29,7 @@ For strategy behavior, research status, and archived backtest evidence, see
29
29
|---|---|---|---|---|---|---|
30
30
| IBKR |`QuantStrategyLab/InteractiveBrokersPlatform`|`us_equity`|`RUNTIME_TARGET_JSON` + `ACCOUNT_GROUP`|`STRATEGY_PROFILE=<runtime_enabled us_equity profile>`| Cloud Run | Yes - controlled by platform rollout config |
31
31
| Charles Schwab |`QuantStrategyLab/CharlesSchwabPlatform`|`us_equity`|`RUNTIME_TARGET_JSON`|`STRATEGY_PROFILE=<runtime_enabled us_equity profile>`| Cloud Run | Yes - controlled by platform rollout config |
32
-
| LongBridge |`QuantStrategyLab/LongBridgePlatform`|`us_equity`|`RUNTIME_TARGET_JSON` + `ACCOUNT_REGION`|`STRATEGY_PROFILE=<runtime_enabled us_equity profile>` per regional service | Cloud Run | Yes - controlled by platform rollout config|
32
+
| LongBridge |`QuantStrategyLab/LongBridgePlatform`|`us_equity`|`RUNTIME_TARGET_JSON` + `ACCOUNT_REGION`|`STRATEGY_PROFILE=<runtime_enabled us_equity profile>` per account service | Cloud Run | Yes - paper and SG today; HK later|
33
33
| Binance |`QuantStrategyLab/BinancePlatform`|`crypto`|`RUNTIME_TARGET_JSON` (workflow-local) |`crypto_leader_rotation`| Oracle Cloud + self-hosted runner | No - only this profile is supported today |
34
34
35
35
## What this means right now
@@ -42,6 +42,8 @@ Platforms currently in this domain:
42
42
-`CharlesSchwabPlatform`
43
43
-`LongBridgePlatform`
44
44
45
+
LongBridge account identities are modeled as `paper`, `HK`, and `SG`; today the live services use `paper` and `SG`, and `HK` follows the same contract when it is introduced.
46
+
45
47
Important limitation:
46
48
47
49
- This does **not** mean any arbitrary future `us_equity` strategy can run by name alone.
0 commit comments