Операции

Previous Next

Статус: Draft Дата: 2026-04-29

1. Operation lifecycle

flowchart TB Start([start]) --> queued queued --> running running --> waiting_approval waiting_approval --> running running --> paused paused --> running running --> failed failed --> diagnosing diagnosing --> patch_review patch_review --> running failed --> verifying verifying --> running running --> completed running --> cancelled completed --> End([end]) cancelled --> End

2. Temporal integration

Temporal запускает generic workflow:

1
2
3
4
5
6
7
RunOperationWorkflow(operation_id)
  load plan snapshot
  find ready nodes
  execute jobs through execution-plane
  wait for gates/signals
  apply approved PlanPatch
  persist timeline facts

Rules:

  • Temporal workflow id = operation id;
  • workflow uses operation-manager as source of truth;
  • workflow signals: approve gate, reject gate, pause, resume, cancel, apply patch;
  • workflow does not expose product API.

3. PlanPatch flow

sequenceDiagram participant User as User/AI participant CP as control-plane-service participant WF as Temporal workflow User->>CP: propose PlanPatch CP->>CP: validate against current plan CP->>CP: store patch as pending User->>CP: approve patch CP->>WF: signal apply_patch(patch_id) WF->>CP: reload effective plan

4. Gate flow

Gates block operation until a valid decision is recorded.

Allowed decisions:

  • approve;
  • reject;
  • choose provider;
  • provide missing input;
  • cancel operation.

5. Operational metrics

Required metrics:

  • active operations;
  • operations by status;
  • node run duration;
  • failed node count by job type;
  • gate waiting duration;
  • PlanPatch approval latency;
  • workflow signal failures;
  • catalog projection lag;
  • execution result processing latency.
Модули Обзор