Модель данных

Previous Next

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

1. Ownership

control-plane-service владеет planning и operation state. Он не владеет canonical resources и не хранит raw artifact blobs.

2. Conceptual entities

erDiagram INTENT ||--o| PLAN : produces SCENARIO ||--o{ PLAN : instantiates PLAN ||--o{ PLAN_NODE : contains PLAN ||--o{ RESOURCE_BINDING : binds PLAN ||--o{ PLAN_PATCH : changed_by PLAN ||--o{ OPERATION : runs_as OPERATION ||--o{ OPERATION_NODE_RUN : executes OPERATION ||--o{ GATE : waits_on OPERATION ||--o{ INTERVENTION : records OPERATION ||--o{ ARTIFACT_METADATA : produces OPERATION ||--o{ EVIDENCE_METADATA : records OPERATION ||--o{ OPERATION_TIMELINE : appends

3. Tables

scenario_packs / scenarios

Хранят marketplace/internal executable сценарии и версии.

Key fields:

  • id;
  • version;
  • source;
  • target_resource_type;
  • actions;
  • requires;
  • provides;
  • risk_metadata;
  • created_at.

plan_templates / job_templates

Хранят reusable template graph.

Key fields:

  • scenario_id;
  • template_version;
  • graph_definition;
  • job_contracts;
  • editable_points;

intents

User/agent desired result.

Key fields:

  • id;
  • actor_id;
  • action;
  • target_resource_type;
  • target_resource_id;
  • desired_result;
  • constraints;
  • status;

plans / plan_nodes

Concrete DAG snapshot.

Key fields:

  • plan_id;
  • intent_id;
  • scenario_ref;
  • status;
  • effective_version;
  • graph_hash;
  • customizations.

Plan node fields:

  • node_id;
  • type;
  • title;
  • requires;
  • produces;
  • job_contract;
  • depends_on;

capability_requirements / resource_bindings

Binding requirement to provider or sub-operation.

Key fields:

  • requirement_id;
  • capability_key;
  • constraints;
  • binding_status;
  • selected_resource_id;
  • sub_operation_plan_id;
  • resolution_reason.

operations / operation_node_runs

Execution state.

Key fields:

  • operation_id;
  • plan_id;
  • status;
  • current_phase;
  • started_at;
  • completed_at;
  • actor_id;

Node run fields:

  • operation_id;
  • plan_node_id;
  • status;
  • attempts;
  • started_at;
  • finished_at;
  • last_error;

gates / interventions / plan_patches

Human and AI-in-the-loop control.

Rules:

  • PlanPatch append-only;
  • gate decision stores actor and timestamp;
  • manual intervention requires verification nodes.

artifact_metadata / evidence_metadata

Metadata only. Blob/secret values live in S3/MinIO/Vault.

local projections

1
2
3
catalog_resource_projection
catalog_capability_projection
catalog_topology_projection

Projections are eventually consistent and rebuildable from catalog events.

4. Status enums

Operation:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
queued
running
waiting_input
waiting_approval
paused
failed
diagnosing
patch_review
verifying
completed
cancelled

Node run:

1
2
3
4
5
6
7
pending
ready
running
skipped
succeeded
failed
blocked

Plan:

1
2
3
4
5
6
7
draft
resolving
waiting_input
waiting_approval
ready
locked
archived
API События