Orchestration

Language: English · 简体中文

The strategy_pipeline package provides reusable run control, artifact publication, quality gates, receipts, and owner-handoff contracts. Callers supply the owner logic and publication adapters; the public control plane coordinates them without defining the contents of research artifacts.

The package exports RunRequest, RunReceipt, ArtifactRef, PublicationRequest, HandoffRequest, and the run, publish_artifact, and publish_handoff functions.

See the control-plane API for the request and receipt contracts, owner/publisher ports, failure handling, and handoff behavior.

Responsibilities and boundaries

• Owners implement domain work and return artifact references rather than in-memory domain objects or provider clients.
• The control plane invokes the owner and publisher, validates returned ArtifactRef values, and emits a sanitized receipt.
• Quality gates evaluate caller-provided checks and release-protocol reports. They do not calculate strategy metrics or access data providers.
• Provider SDKs, credentials, network clients, storage backends, model implementations, and strategy registries remain outside the reusable control-plane contracts.

The installable strategy-pipeline CLI is registered by the root project. Its command surface includes target export, research-protocol and AFML-evidence commands, and a cashflow shadow-publication adapter.

English documentation

• Evaluation orchestration and control-plane API
• E2 promotion receipt
• Cashflow shadow publication
• Run artifacts, output orchestration, and run summaries
• Owner integration, target export, and evidence and protocol CLI
• Operations overview and quality gates
• Development and publication checks, including the Publication audit historical snapshot
• Reference pages, including CLI helpers, configuration, and runtime helpers

The localization status tracks the remaining translation work. Paired pages link to their Chinese counterparts at the top.