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
I0502
Recommend a profile from measured cost, naming the measurements
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- BLOCKED
- Wave
1- Waiting on
- Holds back
- Behind it in all
2- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| issue | I0501 | I0501 is not DONE |
| milestone | routing-recommendations | the milestone routing-recommendations waits on an outcome of its own |
Moves
plan.transitionWhat it is
- Objective
- Add the command that recommends a profile for a class of work from measured cost per accepted outcome, and prints the measurements the recommendation was derived from alongside it.
- Why
- A recommendation whose basis is not printed is an opinion with a command around it. Naming the measurements is what makes it checkable, and being checkable is the only thing that separates this from advice.
- Now
- Cost per accepted outcome is reported per outcome. Nothing recommends anything.
- Wanted
- Asking which profile a class of work should use returns a profile, the measurements behind it, and the group they came from.
- Done when
- unknown: the record declares no `completion`
- Risk
- Following a recommendation produces the data that justifies it; the output has to record that the measurements postdate earlier recommendations.
Acceptance
- Every recommendation lists the accepted outcomes and figures it was derived from
- The recommendation names the group and how the group was derived
- The command reads records and computes nothing that the cost layer already computes
- Validation
bash test/run.sh- Evidence required
suite- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
libbin- Not
Invoking a model, or choosing a provider on a worker's behalf- Depends on
- Priority
- p3
- Profile
- implementation
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-04
- Updated
- 2026-09-04
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.