Atom
Argument note
A note about the work, in a register of its own. 75 instances across 40 screens, which makes it the most widely spread component in the product after the block itself.
It is not product copy, and that is the component. Everything else on a screen speaks to the analyst in the second person; this speaks to whoever is reading the case for the argument. voice/docs/voice.md puts an IA node number, a zone label, a WCAG criterion or a count of the product's own parts in here or nowhere, and correcting such a count in product copy preserves the defect rather than fixing it.
Anatomy
dark, shipped
Out of reach actions are shown with the ceiling stated.
Node 4.1 section 3. Hiding them would have made the ladder a list of what the agent can do, and the analyst needs the shape of what it cannot.
Measured at 03b and drawn at 04: reject costs four taps against accept's two, and the fourth is Enter rather than a confirmation step.
light, the pair
Out of reach actions are shown with the ceiling stated.
Node 4.1 section 3. Hiding them would have made the ladder a list of what the agent can do, and the analyst needs the shape of what it cannot.
Measured at 03b and drawn at 04: reject costs four taps against accept's two, and the fourth is Enter rather than a confirmation step.
.anotethe whole component. Apon all 75- the dotted rail1px dotted, in secondary ink. Dotted rather than solid because every other left rail in this product means something structural, and a note about the work is not part of the work
::beforethe WHY label, and it is not a string in the markup. So it cannot be translated, edited, or dropped on one screen out of forty. 11px, weight 700, .14em of tracking
The class is .anote and not .why. .why was the first name written, and it is already owned three times over: by the latitude ladder, the log row and the outage line. The fifth class collision of stage 06 and the first one caught before it shipped.
Variants
None. Two notes in a row are one argument in two paragraphs, not two kinds of note.
| Axis a reader looks for | Values | Why the cell is empty |
|---|---|---|
| kind of note | – | Prohibited. A warning anote and an informational anote would be two registers inside a register that exists to be one. What varies is the sentence |
| emphasis | – | Bold, not brighter. b and strong inside it keep secondary ink and take weight 700. A note that could shout would compete with the screen it is annotating |
| placement | – | It goes where the thing it argues about is: block 55, outage 8, doc 5, body 4, z4 3. That is the parent's decision and there is no modifier for it |
Two values in this file have no token, and both are carried unchanged.
11px on the WHY label is below the 11px floor of the scale, one of only two places in the product that is. line-height: 1.55 is a fourth value against --leading at 1.45 and --leading-tight at 1.25. Neither was collapsed, and the reason is the same for both: an anote is read once, slowly, by somebody who is not working, and it is the one place in this product where a looser line and a smaller label are the right answer. Both are named on the typography page.
When to use it
To say why a screen is the way it is, to a reader who is judging the design rather than using it. It is the mechanism that let stage 05 rewrite every product string without losing the argument behind them: stage 05 owns everything that is not an anote, and an anote belongs to whoever is presenting the case.
Where she meets it: she does not. This is the one component on the stand that is not for Rasha. It exists because the product is a portfolio case as well as a product, and pretending otherwise is how the argument ends up written in the second person inside the interface. Two instruments found that independently: the browser pass called it the dominant defect of stage 05, and a reader with clean context could not tell which sentences were supposed to be rewritten.
Rule and anti-rule
Do
Node 4.4 section 2. Five of six reasons derive the second axis, which is why four taps never became five.
The argument, with its node number, in the register that says it is an argument. Nobody can mistake it for a string the analyst is meant to act on.
Do not
Node 4.4 section 2. Five of six reasons derive the second axis.
Not as a hint. A hint is product copy addressed to the analyst, and a node number in one is a count of the product's own parts standing in the interface, which voice.md forbids in as many words.
States
It has none, and it is not interactive. It is a note about the work and there is nothing in it to press.
dark, shipped
Out of reach actions are shown with the ceiling stated.
Node 4.1 section 3. Hiding them would have made the ladder a list of what the agent can do, and the analyst needs the shape of what it cannot.
Measured at 03b and drawn at 04: reject costs four taps against accept's two, and the fourth is Enter rather than a confirmation step.
light, the pair
Out of reach actions are shown with the ceiling stated.
Node 4.1 section 3. Hiding them would have made the ladder a list of what the agent can do, and the analyst needs the shape of what it cannot.
Measured at 03b and drawn at 04: reject costs four taps against accept's two, and the fourth is Enter rather than a confirmation step.
A link inside one is link and takes its own states, which is the arrangement everywhere in this system: the container never draws the states of what it holds.
What it reads, and where it stands
| Role | Surface | Dark | Light |
|---|---|---|---|
--text-secondary | ink 4.5:1, and the rail |
One role, doing two jobs on two surfaces, and that is allowed only because the rail is not a control boundary: it is a margin rail on a note, so 1.4.11 does not reach it. The ink is real text and answers to 4.5:1, which it clears at 7.56 in dark and 5.89 in light.
Copy this
No heading and no label in the markup: the WHY comes from the stylesheet, on all 75.