Refactor reactive module to unify stream and graph execution models #5337

Open
opened 2026-04-09 05:53:49 +00:00 by HAL9000 · 2 comments
Owner

The reactive module currently has two separate execution models: a stream-based model in stream_router.py and a graph-based model in graph_executor.py. While there is no direct code duplication between them, the existence of two parallel execution engines for the same conceptual task (executing a plan) adds unnecessary complexity to the codebase.

This makes the system harder to understand, maintain, and extend. A refactoring should be undertaken to unify these two execution models into a single, more flexible execution engine that can handle both stream-based and graph-based execution.

Acceptance Criteria:

  • A single, unified execution engine is created that can handle both stream-based and graph-based plans.
  • The stream_router.py and graph_executor.py modules are refactored or replaced by the new execution engine.
  • The application.py module is updated to use the new unified execution engine.
  • All existing tests for the reactive module pass with the new implementation.

Automated by CleverAgents Bot
Supervisor: Architecture Guard | Agent: architecture-guard

The reactive module currently has two separate execution models: a stream-based model in `stream_router.py` and a graph-based model in `graph_executor.py`. While there is no direct code duplication between them, the existence of two parallel execution engines for the same conceptual task (executing a plan) adds unnecessary complexity to the codebase. This makes the system harder to understand, maintain, and extend. A refactoring should be undertaken to unify these two execution models into a single, more flexible execution engine that can handle both stream-based and graph-based execution. **Acceptance Criteria:** - A single, unified execution engine is created that can handle both stream-based and graph-based plans. - The `stream_router.py` and `graph_executor.py` modules are refactored or replaced by the new execution engine. - The `application.py` module is updated to use the new unified execution engine. - All existing tests for the reactive module pass with the new implementation. --- **Automated by CleverAgents Bot** Supervisor: Architecture Guard | Agent: architecture-guard
Author
Owner

Label compliance fix applied:

  • Added missing labels to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
Author
Owner

Label compliance check — missing milestone:

  • This issue is in State/Verified but has no milestone assigned.
  • Per CONTRIBUTING.md, non-Epic/non-Legendary issues in State/Verified or later should have a milestone.
  • This is a MoSCoW/Could have refactor — suggested milestone: v3.6.0 or later.
  • Please assign a milestone to schedule this work.

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance check — missing milestone: - This issue is in `State/Verified` but has no milestone assigned. - Per CONTRIBUTING.md, non-Epic/non-Legendary issues in `State/Verified` or later should have a milestone. - This is a `MoSCoW/Could have` refactor — suggested milestone: `v3.6.0` or later. - Please assign a milestone to schedule this work. --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#5337
No description provided.