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

[COORD-003] Validate 50% rule #143

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

Objective

Validate the 50% rule prevents context exhaustion by blocking oversized issue assignments.

Implementation Details

Test the core principle from Part 1:

The 50% rule: Issues must not exceed 50% of target agent's context limit.

Test scenarios:

  1. Oversized issue (120K estimate) → Should REJECT assignment
  2. Properly sized issue (80K estimate) → Should ACCEPT assignment
  3. Edge case (exactly 100K estimate) → Should ACCEPT assignment
  4. Multiple medium issues in sequence → Should complete without exhaustion

Context Estimate

  • Files to modify: 2 (test file, validation script)
  • Implementation complexity: low (10,000 tokens)
  • Test requirements: high (15,000 tokens)
  • Documentation: medium (3,000 tokens)
  • Total estimated: 40,300 tokens
  • Recommended agent: glm

Difficulty

low

Dependencies

  • Blocked by: #144 (COORD-002)

Acceptance Criteria

  • Test case: Oversized issue blocked from assignment
  • Test case: Properly sized issue accepted
  • Test case: Edge case (exactly 50%) handled correctly
  • Test case: Sequential issues complete without exhaustion
  • Validation report documenting 50% rule effectiveness
  • Tests pass (85% coverage minimum)

Testing Requirements

  • Create test issues with known context estimates
  • Validate assignment rejection/acceptance logic
  • Measure actual context usage vs estimates
  • Document validation results
  • Coverage: 85% minimum
## Objective Validate the 50% rule prevents context exhaustion by blocking oversized issue assignments. ## Implementation Details Test the core principle from Part 1: **The 50% rule:** Issues must not exceed 50% of target agent's context limit. **Test scenarios:** 1. Oversized issue (120K estimate) → Should REJECT assignment 2. Properly sized issue (80K estimate) → Should ACCEPT assignment 3. Edge case (exactly 100K estimate) → Should ACCEPT assignment 4. Multiple medium issues in sequence → Should complete without exhaustion ## Context Estimate - Files to modify: 2 (test file, validation script) - Implementation complexity: low (10,000 tokens) - Test requirements: high (15,000 tokens) - Documentation: medium (3,000 tokens) - **Total estimated: 40,300 tokens** - **Recommended agent: glm** ## Difficulty low ## Dependencies - Blocked by: #144 (COORD-002) ## Acceptance Criteria - [ ] Test case: Oversized issue blocked from assignment - [ ] Test case: Properly sized issue accepted - [ ] Test case: Edge case (exactly 50%) handled correctly - [ ] Test case: Sequential issues complete without exhaustion - [ ] Validation report documenting 50% rule effectiveness - [ ] Tests pass (85% coverage minimum) ## Testing Requirements - Create test issues with known context estimates - Validate assignment rejection/acceptance logic - Measure actual context usage vs estimates - Document validation results - Coverage: 85% minimum
jason.woltje added the apiapip0phase-1 labels 2026-01-31 21:03:05 +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-1
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#143
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?