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

[COORD-005] Build assignment algorithm #145

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

Objective

Implement intelligent agent assignment algorithm that selects the cheapest capable agent for each issue.

Implementation Details

Build the assignment logic from Part 1 with these priorities:

  1. Must have context capacity (50% rule check)
  2. Must have difficulty capability
  3. Prefer cheapest qualifying agent
  4. Prefer self-hosted when capable

Algorithm filters qualified agents, then sorts by cost to select optimal agent.

Context Estimate

  • Files to modify: 1 (agent_assignment.py)
  • Implementation complexity: medium (20,000 tokens)
  • Test requirements: medium (10,000 tokens)
  • Documentation: medium (3,000 tokens)
  • Total estimated: 46,800 tokens
  • Recommended agent: glm

Difficulty

medium

Dependencies

  • Blocked by: #147 (COORD-004)
  • Blocks: #149 (COORD-006)

Acceptance Criteria

  • Assignment algorithm implemented with priority logic
  • Filters agents by context capacity (50% rule)
  • Filters agents by difficulty capability
  • Sorts by cost (self-hosted preferred)
  • Returns cheapest capable agent
  • Raises error if no agent can handle issue
  • Unit tests (85% coverage minimum)

Testing Requirements

  • Test assignment for low/medium/high difficulty issues
  • Test capacity filtering (50% rule enforcement)
  • Test cost optimization logic
  • Test error handling for impossible assignments
  • Coverage: 85% minimum
## Objective Implement intelligent agent assignment algorithm that selects the cheapest capable agent for each issue. ## Implementation Details Build the assignment logic from Part 1 with these priorities: 1. Must have context capacity (50% rule check) 2. Must have difficulty capability 3. Prefer cheapest qualifying agent 4. Prefer self-hosted when capable Algorithm filters qualified agents, then sorts by cost to select optimal agent. ## Context Estimate - Files to modify: 1 (agent_assignment.py) - Implementation complexity: medium (20,000 tokens) - Test requirements: medium (10,000 tokens) - Documentation: medium (3,000 tokens) - **Total estimated: 46,800 tokens** - **Recommended agent: glm** ## Difficulty medium ## Dependencies - Blocked by: #147 (COORD-004) - Blocks: #149 (COORD-006) ## Acceptance Criteria - [ ] Assignment algorithm implemented with priority logic - [ ] Filters agents by context capacity (50% rule) - [ ] Filters agents by difficulty capability - [ ] Sorts by cost (self-hosted preferred) - [ ] Returns cheapest capable agent - [ ] Raises error if no agent can handle issue - [ ] Unit tests (85% coverage minimum) ## Testing Requirements - Test assignment for low/medium/high difficulty issues - Test capacity filtering (50% rule enforcement) - Test cost optimization logic - Test error handling for impossible assignments - Coverage: 85% minimum
jason.woltje added the phase-2apiapip0 labels 2026-01-31 21:03:35 +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-2
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#145
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?