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
|`global_etf_rotation`| quarterly rebalance + daily canary | weekdays near US close, e.g. `45 15 * * 1-5` in `America/New_York`| Non-rebalance days should only act on the canary emergency path. |
55
+
|`soxl_soxx_trend_income`| daily | weekdays near US close, e.g. `45 15 * * 1-5` in `America/New_York`| Trend/income value-mode profile. |
56
+
|`tqqq_growth_income`| daily | weekdays near US close, e.g. `45 15 * * 1-5` in `America/New_York`| Current SG line. |
57
+
|`russell_1000_multi_factor_defensive`| monthly | first few calendar days after month end, e.g. `45 15 1-7 * *` in `America/New_York`| Consumes monthly feature snapshots from `UsEquitySnapshotPipelines`. |
58
+
|`tech_communication_pullback_enhancement`| monthly | first few calendar days after month end, e.g. `45 15 1-7 * *` in `America/New_York`| Current HK line. LongBridge constrains this profile to the first trading day after the monthly snapshot to avoid month-internal rebalancing. |
59
+
60
+
The upstream snapshot/data workflows live in `UsEquitySnapshotPipelines` and run
61
+
monthly. Cloud Scheduler only invokes the broker runtime; it does not generate
62
+
new feature snapshots.
63
+
46
64
**Layers**
47
65
48
66
-**Trading:** SOXL / SOXX / BOXX
@@ -193,7 +211,7 @@ Important:
193
211
2. Create secret `longport_token_hk` for HK / `longport_token_sg` for SG (or your custom `LONGPORT_SECRET_NAME`) in Secret Manager and add your LongPort access token as the first version.
194
212
3. Set the required env vars above on the Cloud Run service.
195
213
4. Deploy the app to Cloud Run (e.g. `gcloud run deploy` from repo root with Dockerfile or buildpack).
196
-
5. Create a Cloud Scheduler job that POSTs to the Cloud Run URL on a schedule (e.g. `45 15 * * 1-5` for ~15 min before US market close on weekdays).
214
+
5. Create a Cloud Scheduler job that POSTs to the Cloud Run URL on a schedule. Use the [runtime cadence](#runtime-cadence) table: daily profiles usually use `45 15 * * 1-5`, while monthly snapshot profiles use a first-week monthly candidate window such as `45 15 1-7 * *`.
197
215
198
216
IAM: the Cloud Run service account needs **Secret Manager Admin** (or Secret Accessor for the configured `LONGPORT_SECRET_NAME`, `LONGPORT_APP_KEY_SECRET_NAME`, and `LONGPORT_APP_SECRET_SECRET_NAME`, such as `longport_token_hk`, `longport-app-key-hk`, `longport-app-secret-hk`) and **Logs Writer**. Build/deploy typically uses a separate account with Artifact Registry Writer, Cloud Run Admin, Service Account User.
199
217
@@ -244,6 +262,22 @@ IAM: the Cloud Run service account needs **Secret Manager Admin** (or Secret Acc
244
262
python3 scripts/print_strategy_profile_status.py
245
263
```
246
264
265
+
### 策略执行频率
266
+
267
+
策略频率由策略档位决定,但实际券商执行是 Cloud Scheduler 触发的。
268
+
每个 Cloud Run 服务的 Cloud Scheduler 需要和当前 `STRATEGY_PROFILE` 对齐:
0 commit comments