openclaw/openclaw-intelligence-core-public
1
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions

refactor: split the orchestrator into policy-router, effect-executor, and observation-reducer modules #2

New issue
Open
opened 2026-03-21 09:11:38 +01:00 by openclaw · 0 comments
openclaw commented 2026-03-21 09:11:38 +01:00
Owner
Copy link

Context
The live orchestrator is still a 3608-line monolith with 167 analysis.update calls, 167 return analysis sites, and 110 Fix comments.

Why this matters
This is the main structural blocker to safe self-improvement. It makes trajectory slices harder to reason about, complicates replay determinism, and slows every architectural change.

Current evidence

  • /home/openclaw/.openclaw/workspace/bin/agent-orchestrate

Deliverables

  • Extract a typed policy-router layer.
  • Extract a pure effect-executor layer.
  • Extract an idempotent observation-reducer / state-commit layer.
  • Define clean boundaries and data contracts between them.
  • Preserve current sacred-gate behavior while shrinking the monolith.

Definition of done
The orchestrator becomes a thin coordinator; major mutations and routing logic live in dedicated modules with tests.

Context The live orchestrator is still a 3608-line monolith with 167 `analysis.update` calls, 167 `return analysis` sites, and 110 `Fix` comments. Why this matters This is the main structural blocker to safe self-improvement. It makes trajectory slices harder to reason about, complicates replay determinism, and slows every architectural change. Current evidence - `/home/openclaw/.openclaw/workspace/bin/agent-orchestrate` Deliverables - Extract a typed policy-router layer. - Extract a pure effect-executor layer. - Extract an idempotent observation-reducer / state-commit layer. - Define clean boundaries and data contracts between them. - Preserve current sacred-gate behavior while shrinking the monolith. Definition of done The orchestrator becomes a thin coordinator; major mutations and routing logic live in dedicated modules with tests.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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: openclaw/openclaw-intelligence-core-public#2
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?