Frontmatter
| id | 9971 |
| title | [Agent OS] Downgrade "status: needs-re-triage" priority in DreamService |
| state | Closed |
| labels | enhancementai |
| assignees | tobiu |
| createdAt | Apr 13, 2026, 3:27 PM |
| updatedAt | Apr 14, 2026, 12:32 AM |
| githubUrl | https://github.com/neomjs/neo/issues/9971 |
| author | tobiu |
| commentsCount | 0 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Apr 13, 2026, 3:47 PM |
[Agent OS] Downgrade "status: needs-re-triage" priority in DreamService
Closedenhancementai
🎯 Objective
Update the
DreamServiceSQLite weighting and queue generation logic to heavily downrank or isolate tickets labeledstatus: needs-re-triage.🧠 Architectural Rationale
Our new
ticket-intakeskill (#9969) empowers agents to formally reject stale or mathematically regressive tickets (Negative ROI) by assigning them theneeds-re-triagelabel rather than brutally closing them. This guarantees the architectural anomaly is preserved for human review. However, ifDreamServicecontinues to feed these labeled tickets to the top of the swarm execution loop, the autonomous agents will enter an infinite cycle of validation/rejection.📋 Scope
DreamService.mjs(theQueryReRanker/ SQL execution layer).needs-re-triagelabel payload.runSandman.mjsthat flagged tickets sink below the operational execution threshold while remaining available for analytical review.