1.6 KiB
id, name, status, depends_on, scope, risk, impact, level
| id | name | status | depends_on | scope | risk | impact | level | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| meta/reactive-layer | Complete reactive execution layer — WorkflowRoot, node-status, maxConcurrency, retries | completed |
|
broad | high | phase | planning |
Description
Meta task that clusters all reactive execution tasks. Once complete, the reactive layer provides signal-backed execution with automatic precondition resolution, failure propagation, and event-log-driven state management.
Acceptance Criteria
- All reactive tasks completed
- WorkflowReactiveRoot implements EventLogProjection correctly
- Preconditions drive automatic state transitions
- Failure follows dependency edges, not structural scope
- dispose() prevents signal leaks
References
- docs/architecture/reactive-execution.md
Notes
All four dependent tasks (reactive/workflow-root, reactive/node-status, reactive/max-concurrency, reactive/retry-semantics) were already completed. This meta-task verifies the integrated reactive execution layer works correctly end-to-end.
Summary
Verified the complete reactive execution layer: WorkflowReactiveRoot implements EventLogProjection correctly with signal-backed status, computed preconditions drive automatic state transitions, failure propagation follows dependency edges (not structural scope), maxConcurrency semaphore works for Parallel groups, retry semantics preserve full event history, and dispose() prevents signal leaks. All 665 tests pass (129 reactive-specific).