Skip to content
Cockpit0.29.0
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

I0503

Return no recommendation where the data is too thin, and say why

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
routing-recommendations
Milestone status
BLOCKED
Wave
2
Waiting on
I0502milestone:routing-recommendations
Holds back
I0504
Behind it in all
1
Evidence
0 of 1
In the waySubjectDetail
issueI0502I0502 is not DONE
milestonerouting-recommendationsthe milestone routing-recommendations waits on an outcome of its own

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0503

majordomus plan verify I0503

majordomus plan done I0503

What it is

Objective
Make insufficient data produce no recommendation rather than a weak one, with the threshold declared as data and the reason printed, proved by cases on both sides of it.
Why
The failure mode of every routing feature is a confident answer from three data points. Refusing to answer is the behaviour that has to be tested, because it is the one that will be pressured away.
Now
The command recommends from whatever measurements exist.
Wanted
Below the threshold the command returns no recommendation and names what it would take to have one; above it, the recommendation carries its denominator.
Done when
unknown: the record declares no `completion`
Risk
A threshold nobody can reach makes the whole command dead code; if the case shows the bar is unreachable in practice, that is a finding about the milestone, not a reason to lower it quietly.

Acceptance

  • The threshold is declared as data and printed with every answer and every refusal
  • Below it, no profile is named at all
  • Cases cover both sides of the threshold
Validation
bash test/run.sh
Evidence required
suite
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
libtest/cases
Not
A weaker recommendation with a caveat attached
Depends on
I0502
Priority
p3
Profile
debugging
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.