A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
routing-recommendations
Routing recommendations derived from measured cost
4issuesdevtask.milestone
0readydevtask.milestone
3blockeddevtask.milestone
0activedevtask.milestone
0completedevtask.milestone
The milestone
devtask.milestone- Title
- Routing recommendations derived from measured cost
- Outcome
- The profile a task should run under is recommended from measured cost per accepted outcome, and the recommendation names the data it came from.
- Status
- BLOCKED
- Rank
4- Depends on
- Waiting on
- Holds back
- Record
.ai/repo/project/milestones/routing-recommendations.yaml- Its issues
- Every issue of this milestone
Where the work is
- Ready
- —
- Blocked
- Waiting
- Active
- —
- In review
- —
- Completion blocked
- —
- Complete
- —
- Cancelled
- —
What holds the most back
What may run at the same time
Nothing here can be started now.
Every issue
| Readiness | Status | Issue | Title | Wave | Priority | Waiting on | Holds back |
|---|---|---|---|---|---|---|---|
| waiting | BLOCKED | I0501 | Group comparable work from what the records already carry | 0 | p3 | 3 | |
| blocked | BLOCKED | I0502 | Recommend a profile from measured cost, naming the measurements | 1 | p3 | 2 | |
| blocked | BLOCKED | I0503 | Return no recommendation where the data is too thin, and say why | 2 | p3 | 1 | |
| blocked | BLOCKED | I0504 | Prove the recommendation is advisory and publish it as such | 3 | p3 | 0 |
Findings
Nothing is wrong with these records.