Atom
Trend
Which way the record is going. 72 instances across 16 screens, always inside rec and never anywhere else. Without it the count is not evidence.
31 of 36 says what the agent's record is; was 34 of 36 says which way it is moving, and the direction is the whole of what CLAUDE.md calls calibrated trust: that the trust is earned and visible rather than asserted. A record with no trend is a number the analyst has to remember last week's value of, forty times over, which is precisely the failure mode the riskiest assumption in this project names.
Anatomy
dark, shipped
light, the pair
.wasthe whole component. Aspanon all 72, insiderecdisplay: blocka block inside an inline parent, on purpose.recis one grid cell and the trend takes the line below the count rather than sitting beside it, so the column of counts stays a column. Inline, every cell would be a different width and the digits would stop lining up
The bench is 288px wide because the pane is. The detail pane is 320px below 1560 and its content is 288, and at that width the tenant name wraps to two lines and the whole row is two lines tall. A bench wider than the pane would show a component that does not occur: design/kit/checks/geometry.mjs reported the row 2.19px short until the bench was narrowed to the real thing.
Variants
None, and the interesting empty cell is the one where a number is missing.
| What varies | Uses | Where it is decided |
|---|---|---|
was 34 of 36 | 62 | the sentence. The previous window's count, in the same form as the current one |
too few to compare | 10 | Voice, not a variant, and it is the fourth voice rule rendered: say what is true about the machine, including what it did not find. A tenant with four decisions has no trend, and inventing one would be the worst thing this component could do |
| direction | – | Prohibited. It does not colour whether the record went up or down. See rec: a trend painted good or bad decides for the analyst what she is being asked to judge |
When to use it
Inside a record, always, and nowhere else. The pairing is the component: a count without a trend and a trend without a count are each half of an argument, and the fleet exists to make the whole argument readable at a glance.
Where she meets it. When deciding whether to give the agent more rope on a tenant, which is the third of the three MVP jobs and the one CLAUDE.md calls a bet rather than a qualified job. If that bet is wrong, this is the component that was carrying it.
Rule and anti-rule
Do
Say there is no trend when there is none. A tenant with four decisions is the case this component is most likely to be wrong about, and the honest string is shorter than the dishonest one.
Do not
Not a trend built from three decisions. It is true, it is useless, and it reads exactly like a trend built from three hundred, which is how a number in this interface stops being evidence.
States
It has none, and it is not interactive.
dark, shipped
light, the pair
What it reads, and where it stands
| Role | Surface | Dark | Light |
|---|---|---|---|
--text-secondary | ink 4.5:1 |
Secondary ink and 11px: it is the second line of an argument whose first line is the count, and it must not compete with it.