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

BLOCKED wave 2 · p3 · debugging profile · runs alone

Part of routing-recommendations — Routing recommendations derived from measured cost.

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.

Current state

The command recommends from whatever measurements exist.

Desired state

Below the threshold the command returns no recommendation and names what it would take to have one; above it, the recommendation carries its denominator.

Scope

• lib
• test/cases

Out of scope

• A weaker recommendation with a caveat attached

Dependencies

• I0502BLOCKED Recommend a profile from measured cost, naming the measurements

What waits on this

• I0504BLOCKED Prove the recommendation is advisory and publish it as such

Acceptance criteria

• 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

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

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.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I0503.yaml. Read it back with majordomus plan show I0503.