События

Previous Next

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

1. Event role

Events используются для projections, audit, UI notifications и интеграции с catalog/execution. Source of truth остается в PostgreSQL.

2. Published events

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
intent.created
plan.created
operation.started
operation.node.started
operation.node.succeeded
operation.node.failed
operation.completed
operation.cancelled
gate.waiting
gate.approved
gate.rejected
plan.patch.proposed
plan.patch.approved
plan.patch.rejected
artifact.created
evidence.recorded

3. Key payloads

operation.node.failed

1
2
3
4
5
6
7
8
9
event_type: operation.node.failed
payload:
  operation_id: uuid
  plan_node_id: string
  attempt_id: uuid
  failure_category: infrastructure_error
  message: string
  artifact_refs: []
  evidence_refs: []

gate.waiting

1
2
3
4
5
6
7
event_type: gate.waiting
payload:
  operation_id: uuid
  gate_id: string
  reason: string
  required_roles: []
  options: []

plan.patch.proposed

1
2
3
4
5
6
7
event_type: plan.patch.proposed
payload:
  operation_id: uuid
  patch_id: uuid
  author_type: user | system | ai_agent
  reason: string
  requires_approval: true

4. Consumed events

From resource-catalog-service:

  • resource.created;
  • resource.updated;
  • resource.deleted;
  • resource.health_changed;
  • capability.definition.published;
  • capability.provided.

From execution-plane-service:

  • execution.attempt.started;
  • execution.attempt.succeeded;
  • execution.attempt.failed;
  • artifact.created.

5. Idempotency

Every consumed event must be processed idempotently by event_id. Projection updates must store source resource version.

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