mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

[COORD-004] Implement basic orchestration loop #160

New Issue
Closed
opened 2026-01-31 21:28:16 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-31 21:28:16 +00:00
Owner
Copy Link

Objective

Create the main orchestration loop that processes the queue and spawns agents.

Implementation Details

  1. Create Coordinator class
  2. Implement process_queue() method:
    • Get next ready issue
    • Spawn agent (stub for now)
    • Mark complete (stub for now)
  3. Add error handling
  4. Add logging
  5. Make it run as async loop
  6. Graceful shutdown handling

Context Estimate

  • Files to modify: 5 (coordinator.py, main.py, config.py, models.py, tests/)
  • Implementation complexity: high (30000 tokens)
  • Test requirements: high (15000 tokens)
  • Documentation: heavy (5000 tokens)
  • Total estimated: 71500 tokens
  • Recommended agent: opus

Difficulty

high

Dependencies

  • Blocked by: #159 (COORD-003 - needs queue manager)
  • Blocks: COORD-005 (integration test needs loop working)

Acceptance Criteria

  • Orchestrator runs as async loop
  • Gets next ready issue from queue
  • Spawns agent (stub implementation OK for Phase 0)
  • Handles errors gracefully
  • Logs all actions
  • Can be started/stopped cleanly
  • 85% test coverage
  • Integration test: Processes mock queue

Testing Requirements

  • Unit tests for core loop logic
  • Test error handling
  • Test graceful shutdown
  • Integration test: End-to-end with mock queue
  • Manual test: Run coordinator, assign issue, verify processing
## Objective Create the main orchestration loop that processes the queue and spawns agents. ## Implementation Details 1. Create Coordinator class 2. Implement process_queue() method: - Get next ready issue - Spawn agent (stub for now) - Mark complete (stub for now) 3. Add error handling 4. Add logging 5. Make it run as async loop 6. Graceful shutdown handling ## Context Estimate - Files to modify: 5 (coordinator.py, main.py, config.py, models.py, tests/) - Implementation complexity: high (30000 tokens) - Test requirements: high (15000 tokens) - Documentation: heavy (5000 tokens) - **Total estimated: 71500 tokens** - **Recommended agent: opus** ## Difficulty high ## Dependencies - Blocked by: #159 (COORD-003 - needs queue manager) - Blocks: COORD-005 (integration test needs loop working) ## Acceptance Criteria - [ ] Orchestrator runs as async loop - [ ] Gets next ready issue from queue - [ ] Spawns agent (stub implementation OK for Phase 0) - [ ] Handles errors gracefully - [ ] Logs all actions - [ ] Can be started/stopped cleanly - [ ] 85% test coverage - [ ] Integration test: Processes mock queue ## Testing Requirements - Unit tests for core loop logic - Test error handling - Test graceful shutdown - Integration test: End-to-end with mock queue - Manual test: Run coordinator, assign issue, verify processing
jason.woltje added the p0apiapi labels 2026-01-31 21:28:16 +00:00
jason.woltje added this to the M4.1-Coordinator (0.0.4) milestone 2026-01-31 21:28:43 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label api api p0
Milestone
No items
No Milestone M4.1-Coordinator (0.0.4)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#160
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?