Skip to content

Clarify health signal boundaries #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Pigbibi merged 1 commit into from
Jul 5, 2026
Merged

Clarify health signal boundaries #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/hk_snapshot_publish_workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

[中文版本](./hk_snapshot_publish_workflow.zh-CN.md)

This runbook explains how to build, validate, and optionally publish the active HK snapshot artifact pack when an operator has prepared a real factor snapshot CSV, or when the workflow generates one from public yfinance data or LongBridge OpenAPI.
This runbook explains how to build, validate, and optionally publish the active HK snapshot artifact pack when an operator has prepared a real factor snapshot CSV, or when the workflow generates one from public yfinance data or LongBridge OpenAPI. The resulting reports are background evidence for artifact or content health, not AiGateway online service health, and they are not sufficient by themselves to approve live trading or automatic publish decisions.

The workflow does **not** approve live trading, deploy Cloud Run, or place broker orders. It only turns a real CSV or generated runtime input into a validated artifact pack and, when explicitly requested, uploads the pack to GCS.

Expand Down
Loading