Judgment detail
One signal, fully reasoned: what goal it was meant to move, how good the work is on its own terms, and whether it was the highest-leverage use of capacity.
FLOW-188 · Migrate legacy reporting macros
Low-priority backlog ticket, To Do for 6 weeks. No deadline, not linked to any active epic.
What the engine inferred
The three scores
never a single numberDimension breakdown
how output value was earnedNothing wrong — but nothing happening either. To Do for 6 weeks.
No deadline, no linked epic, no acceptance criteria.
Ladders to a 0.15-weight goal at best.
Judgment trace
question → finding- 1
What goal was this meant to move?
Legacy reporting migration — the lowest-weighted unit goal. It hasn't moved in 6 weeks.
- 2
How good is the work on its own terms?
Can't judge work that hasn't started; the signal here is the staleness.
- 3
Was this the highest-leverage use of capacity?
No. This is a candidate to drop, not to schedule.
Narrative
A 6-week-stale ticket on the lowest-priority goal. The intelligence here isn't about the work — it's that this is dead weight in the backlog masquerading as planned work. Either kill it or attach it to a real outcome.
Action ladder
how far the engine will goMove FLOW-188 to icebox. If legacy reporting matters, give it a deadline and a linked epic; otherwise stop carrying it on the board.