Skip to content

architecture.md

Latest commit

 

History

History
40 lines (31 loc) · 1.77 KB

architecture.md

File metadata and controls

40 lines (31 loc) · 1.77 KB
Raw

Architecture / 架构

Operra is a local, task-first control plane for Qoder Cloud Agents.

Operra 是一个本地运行、以 Task 为核心的 Qoder Cloud Agents 控制面。

flowchart TB
    UI["Web UI · Oopz"] --> API["FastAPI control plane"]
    API --> TS["Task service & state machine"]
    API --> FS["Local workspace store"]
    TS --> QA["QCA adapter"]
    QA --> QCA["Qoder Cloud Agents API"]
    QCA <--> GH["User GitHub repository"]
    QCA --> EV["Normalized events"]
    EV --> TS
    TS --> UI
Loading

Boundaries / 边界

  • app/api/ exposes the local HTTP and streaming interface and serves the UI.

  • app/services/ owns task workflows, reconciliation, review, and orchestration.

  • app/domain/ defines task and event semantics.

  • app/engine/ is the sole QCA runtime boundary.

  • app/fs/ and app/store/ persist local workspace state.

  • app/operator/ implements the Oopz-facing operating layer.

  • app/api/ 提供本地 HTTP/流式接口与 Web UI。

  • app/services/ 承担任务流程、对账、审核与协调。

  • app/domain/ 定义 Task 与事件语义。

  • app/engine/ 是唯一的 QCA 运行时边界。

  • app/fs/ 与 app/store/ 持久化本地工作区状态。

  • app/operator/ 实现面向 Oopz 的运营层。

Design rules / 设计约束

Task is the user-facing aggregate. QCA-specific events are normalized before they enter the domain. External or irreversible work must be represented by a review gate. Raw traces remain available for diagnosis, while the default UI presents human-readable progress and artifacts.

Task 是面向用户的聚合根。QCA 事件进入领域层前会被归一化；对外或不可逆动作必须通过审核卡点表达。原始 trace 可用于诊断，默认界面则以人话进度和产物为主。