Skip to content

Latest commit

 

History

History
26 lines (17 loc) · 2.74 KB

README.md

File metadata and controls

26 lines (17 loc) · 2.74 KB

Documentation index

English README · 中文 README

Architecture and applicability

Document Scope and reading order
Package architecture Primary entry for the configuration package, generated targets, tooling, web application and runtime-authority boundary. Read against the revision you consume; this is not deployed-state evidence.
Organization architecture Complementary repository governance: compatibility bundles, tiers/rings, dependency checks and release boundaries. It does not replace the package architecture or certify runtime health.
Configuration-driven design, 2026-06-29 Dated Chinese design rationale and migration phases. Its file lists, deployment examples and proposed phases describe that design baseline; use the package architecture and current tooling for present interfaces. English overview below.

English overview of the dated configuration design

The June 2026 design proposed one platform-config.json source for platform metadata, capabilities and domains, with build-time Python generation feeding the frontend/Worker. Strategy catalog features govern which controls are shown. The purpose was to remove repeated platform/strategy constants and derive generated assets from configuration. Its extraction, frontend refactor and generation phases are a plan, not proof that each phase or example is current or deployed.

The current package retains configuration and compatibility ownership. Broker credentials, order execution and strategy logic stay in their owning repositories. RUNTIME_TARGET_JSON is desired deployment state; settings, CI, lifecycle labels or workflow dispatch do not grant runtime, fund or stage-change authority. The complete P0–P6 boundary remains applicable.

Console by task

The existing complete documents retain their interfaces and risk controls. Index links and English summaries do not authorize deployment or change data/provider rights. See LICENSE.