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

Build Gate Rejection Response Handler #139

New Issue
Closed
opened 2026-01-30 23:43:30 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-30 23:43:30 +00:00
Owner
Copy Link

Implement system for rejecting premature done claims and communicating failures to agents.

Objective: Reject agent done claims with clear, actionable failure messages.

Rejection Response Format:

  • Status: REJECTED
  • Reason: Quality gates failed
  • Failed gates list with specifics
  • Required actions before retry
  • Forced continuation prompt

Response Examples:
REJECTED: Quality gates failed

  • Build: 12 compilation errors (requires 0)
  • Lint: 509 errors, 344 warnings (requires 0 errors, max 50 warnings)
  • Tests: 73 failures (requires 100% pass)

You must fix ALL issues above before claiming done. Continue working.

Response Delivery:

  • Inject into agent context as system message
  • Non-negotiable tone (cannot be ignored or deferred)
  • Specific numbers and thresholds
  • Clear success criteria
  • Forces immediate continuation

State Management:

  • Track rejection count per task
  • Alert after N rejections (possible infinite loop)
  • Escalate to user if agent stuck
  • Log rejection history for analysis

Related: L-015, #134 (orchestrator), #136 (gates), #137 (continuation prompts)

Acceptance Criteria:

  • Rejection response format defined
  • Clear, actionable messages generated
  • Integrated with orchestrator workflow
  • Agent receives and processes rejection
  • Rejection history tracked
  • Escalation to user after threshold
  • Cannot be bypassed or negotiated by agent
Implement system for rejecting premature done claims and communicating failures to agents. Objective: Reject agent done claims with clear, actionable failure messages. Rejection Response Format: - Status: REJECTED - Reason: Quality gates failed - Failed gates list with specifics - Required actions before retry - Forced continuation prompt Response Examples: REJECTED: Quality gates failed - Build: 12 compilation errors (requires 0) - Lint: 509 errors, 344 warnings (requires 0 errors, max 50 warnings) - Tests: 73 failures (requires 100% pass) You must fix ALL issues above before claiming done. Continue working. Response Delivery: - Inject into agent context as system message - Non-negotiable tone (cannot be ignored or deferred) - Specific numbers and thresholds - Clear success criteria - Forces immediate continuation State Management: - Track rejection count per task - Alert after N rejections (possible infinite loop) - Escalate to user if agent stuck - Log rejection history for analysis Related: L-015, #134 (orchestrator), #136 (gates), #137 (continuation prompts) Acceptance Criteria: - Rejection response format defined - Clear, actionable messages generated - Integrated with orchestrator workflow - Agent receives and processes rejection - Rejection history tracked - Escalation to user after threshold - Cannot be bypassed or negotiated by agent
jason.woltje added the p0apiapi labels 2026-01-30 23:43:30 +00:00
jason.woltje added this to the M4-LLM (0.0.4) milestone 2026-01-30 23:45:34 +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-LLM (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#139
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?