Operations

Chinese version

Failure semantics

When data is incomplete or an external service is unavailable, the platform records a degraded state and stops downstream processing when it cannot safely produce a result. Success, degraded, and failure outcomes must all be represented by inspectable receipts.

Deployment boundary

Host timers, production credentials, real delivery targets, and runtime state are managed by quant-intel-deploy. The public repository provides reusable code, contracts, and offline checks only.

Recovery and scheduling

Use the documented dm, a-share-daily, and recovery scripts through stable production paths. Do not point scheduled jobs at temporary worktrees. After changing production paths, reload the relevant systemd units and run the matching offline or shadow smoke test.

Quality gate

The repository gate is:

uv run python project_tools/check_all.py --scope all

It covers tests, lint, type checks, CLI help synchronization, package coverage, and scripts. CI runs public-boundary checks separately. CI does not fetch real market data, call Feishu, or use broker credentials.

Weekly basket personal delivery

Pass --personal-only with a-share-daily weekly-basket --send to deliver only to the explicit --personal-chat-id. This ignores any configured group target and does not require --group-chat-id. Without this flag, sending continues to require and deliver to both personal and group targets. Personal receipts and idempotency keys remain the same when switching between these modes.