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

[COORD-010] Build orchestration loop #150

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

Objective

Build the main orchestration loop that coordinates issue queue processing, agent assignment, and quality verification.

Implementation Details

Implement orchestration flow from Part 3:

Orchestration loop:

  1. Read issue queue (priority sorted)
  2. Estimate context for next issue
  3. Assign cheapest capable agent (50% rule)
  4. Monitor agent context during execution
  5. On completion claim, delegate to Quality Layer
  6. Handle rejection (inject continuation) or approval (move to next issue)

This is the core coordinator that ties all components together.

Context Estimate

  • Files to modify: 2 (coordinator.py, main.py)
  • Implementation complexity: high (30,000 tokens)
  • Test requirements: high (15,000 tokens)
  • Documentation: heavy (5,000 tokens)
  • Total estimated: 71,500 tokens
  • Recommended agent: opus

Difficulty

high

Dependencies

  • Blocked by: #155 (COORD-009)
  • Blocks: #157 (COORD-011)

Acceptance Criteria

  • Main orchestration loop implemented
  • Issue queue processing with priority sorting
  • Integration with context estimator
  • Integration with agent assignment
  • Integration with Quality Layer API
  • Completion handling (rejection and approval)
  • Unit and integration tests (85% coverage minimum)

Testing Requirements

  • Mock issue queue with priority-sorted issues
  • Test full orchestration flow
  • Test quality gate integration
  • Test rejection and continuation flow
  • Test approval and next-issue flow
  • Coverage: 85% minimum
## Objective Build the main orchestration loop that coordinates issue queue processing, agent assignment, and quality verification. ## Implementation Details Implement orchestration flow from Part 3: Orchestration loop: 1. Read issue queue (priority sorted) 2. Estimate context for next issue 3. Assign cheapest capable agent (50% rule) 4. Monitor agent context during execution 5. On completion claim, delegate to Quality Layer 6. Handle rejection (inject continuation) or approval (move to next issue) This is the core coordinator that ties all components together. ## Context Estimate - Files to modify: 2 (coordinator.py, main.py) - Implementation complexity: high (30,000 tokens) - Test requirements: high (15,000 tokens) - Documentation: heavy (5,000 tokens) - **Total estimated: 71,500 tokens** - **Recommended agent: opus** ## Difficulty high ## Dependencies - Blocked by: #155 (COORD-009) - Blocks: #157 (COORD-011) ## Acceptance Criteria - [ ] Main orchestration loop implemented - [ ] Issue queue processing with priority sorting - [ ] Integration with context estimator - [ ] Integration with agent assignment - [ ] Integration with Quality Layer API - [ ] Completion handling (rejection and approval) - [ ] Unit and integration tests (85% coverage minimum) ## Testing Requirements - Mock issue queue with priority-sorted issues - Test full orchestration flow - Test quality gate integration - Test rejection and continuation flow - Test approval and next-issue flow - Coverage: 85% minimum
jason.woltje added the apiapip0phase-4 labels 2026-01-31 21:04:52 +00:00
jason.woltje added this to the M4.1-Coordinator (0.0.4) milestone 2026-01-31 21:10:03 +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 phase-4
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#150
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?