Skip to content
C.W.K.
Stream
Lesson 02 of 04 · published

Compare Without Ranking

~11 min · diff, stats, no-scores

Level 0Cold Stick
0 XP0/41 lessons0/14 achievements
0/100 XP to next level100 XP to go0% complete

A Ruler Is Not a Judge

firebrand diff aligns two sessions by step: request hashes, calls, tokens, timings, stop reasons. firebrand stats rolls up steps, calls, tokens, cuts, wall clock, tool errors. Those two are the rulers. There is no firebrand bench verb. None of these emit a quality score. Lifecycle facts only. A number that pretends to rank souls is the thing this family already refused on the workshop side — repair is reader-triggered, not scanner-ranked.

Blind comparison is N seats, N profiles, one brief. Judges, when they exist, sit in the instrument, not in this CLI. Firebrand-versus-Firebrand is still two notebooks, not a trophy.

Alignment is a fact. A winner is an editorial. If the command printed a score, you would start farming the score. The record would stop being a notebook and start being a contest.

What Replay Proves, Again

Replay proves the same recorded request normalizes the same way, or it proves it does not. It does not prove tomorrow's sample. A small-model cell that went 3/3 on one daemon release and 2/3 on another is two rows, both kept. Averaging them into 'the model is a B' is ranking by another door. Keep both rows. Name the daemon. Let a reader decide whether the work is done.

Code

Rulers, not trophies·bash
firebrand diff <session-a> <session-b>
firebrand stats <session>
# no firebrand bench
# no score field
# no 'winner'
# stop reasons and hashes are the output

External links

Exercise

Take two records that differ by one stop reason. Write the diff sentence. Then write the ranking sentence you will not publish. The second sentence is the defect.
Hint
The ranking sentence usually contains 'better' or a letter grade.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.