Read documents at the library revision used by your consumer. These are source-level specifications and design references, not evidence of deployed versions or permission to trade.
- Architecture (中文): layers, data flow, design patterns, naming, dependencies and cross-cutting concerns.
- Development standard: English overview · complete Chinese v1.0 standard: platform/strategy development, configuration, monitoring, security and checklists. The v1.0 plugin examples are historical; see the compatibility section below before reading mount examples.
- Strategy-platform configuration: source of truth, strategies, platforms, validation and scheduler timezones. Legacy plugin/config-sync examples must be read with the historical boundary below.
-
One-time setup intent: immutable, non-executing owner scope and Decisions handoff; no runtime adoption or activation authority.
-
Platform notification outcomes: credential-free intents, receipts and log redaction.
-
Notification routing policy: durable daily facts and urgent incidents.
-
Alpaca public market data collection: manual, read-only workflow and its secrets.
-
Pending order evidence v1: optional journal evidence without budget release.
-
Paper execution consumer, portfolio action matrix and evidence package.
-
IBKR read-only order outcomes: identity-bound terminal observations without execution authority.
- Legacy plugin runtime contract (中文): HISTORICAL / no authority effect. Retained for replay and migration troubleshooting; not the current platform-mount specification.
- Automatic name-based
latest_signal.jsonmounts are retired. V2 observation/notification evidence does not enable Paper/Live or establish P4–P6 eligibility. A runnable composite candidate needs its own bound revisions, inputs, portfolio rules and P1–P3/target-channel evidence, as stated in the linked contract.
Provider rights, credential restrictions, risk controls and the repository license remain applicable.