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
cost-per-accepted-outcome
Cost per accepted outcome, only on measured data
4issuesdevtask.milestone
0readydevtask.milestone
3blockeddevtask.milestone
0activedevtask.milestone
0completedevtask.milestone
The milestone
devtask.milestone- Title
- Cost per accepted outcome, only on measured data
- Outcome
- The cost of an accepted outcome is computed from measured telemetry and the finish contract that accepted it, and is reported only where both exist.
- Status
- BLOCKED
- Rank
3- Depends on
- Waiting on
- Holds back
- Record
.ai/repo/project/milestones/cost-per-accepted-outcome.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 | I0401 | Define an accepted outcome, and join it to its measurements without storing the join | 0 | p2 | 3 | |
| blocked | BLOCKED | I0402 | Report cost only where measurement and acceptance both exist | 1 | p2 | 2 | |
| blocked | BLOCKED | I0403 | Make a thin denominator say so rather than average it away | 2 | p2 | 1 | |
| blocked | BLOCKED | I0404 | Publish the cost-per-outcome claim with its unit defined beside it | 3 | p3 | 0 |
Findings
Nothing is wrong with these records.