• *Come back* has no flow and no FEAT — nothing brings an owner back on Monday except the dread; a Sunday-evening line ("3 visits uncovered tomorrow") is queued by the 8pm rule and needs PAT-4's *say when*
• the carer who won't install anything — one owner in nine; no flow serves the phone-only carer

4 primitives underneath (color.<hue>.<step>) — referenced by these names, never by a screen.

Checks the pairs the tokens declare, not what the page renders — text over an image, a gradient or a translucent overlay composites at runtime and stays not checked. A pair that fails is a token-system finding: fix it in docs/design/tokens.json and every screen moves.

• Clear space: the height of the mark on every side
• Minimum size: 16px on screen, 6mm in print; below that the mark alone, never the lockup
• Colour: kettle copper on paper · white on the accent · one colour (text.body) for print; never on a photograph
• With the tagline: *Cover found before the kettle boils* sits with the wordmark on the landing page only; nowhere inside the app
• Misuse: stretched · a gradient · recoloured to a signal colour · below minimum

• Base unit: 4
• The ramp: inside a control `space.2` · between controls `space.3` · between sections `space.6`
• Grid anatomy: the laptop is one column of rows at 720px max with a 240px rail on the left; the phone is one column edge to edge with `space.4` margins; the day view is one column of visits in time order
• Breakpoints: `breakpoint.phone` 480 · `breakpoint.laptop` 960 — two, because there are two surfaces that change shape
• Responsive techniques: reflow (the visit row stacks its who under its when on the phone) · resize (the button fills the width on the phone) · keep (the chip never changes) · re-architect (the rail becomes the phone's bottom bar); hide is not allowed — nothing an owner needs is hidden on the phone
• Density: one

breakpoint.* tokens: breakpoint.phone 480px · breakpoint.laptop 960px. target.min 44px.

• QuietNotice — new — a line on the owner's day view after 8pm saying when the queued asks will go out ("3 asks go out at 7am"). No existing component says *when* something will happen; the disabled AskCard says it to the carer, and the owner has nothing. docs/design/components/QuietNotice.md

The next /design-review answers each: reuse, adjust, or new. A request that names a behaviour no existing part has is the only kind that becomes a file.

One word per concept, in props too: the visual variation → variant (never type, kind, style) · the primary action handler → onAsk (never onClick, onPress) · the off state → disabled (never isDisabled, inactive) · the loading state → loading (never isLoading, pending)

Not checked, for every component: reads to 320px · a screen reader announces it · every string is in the copy layer · a person has used it. Nothing on disk answers those; a rendered page and a person do. /design-review after says the same not checked rather than pass.

A review finding can say violates PAT-n instead of re-arguing the rule. These are the ones worth showing a designer — and the ones the agent is handed at the write.

The only rung an agent can act on. A principle above that never produced a row here isn't steering anything yet.

Cut, and kept: a note to the carers — asked for in the first version; nobody wrote one — the visit's time and client are the note · pick which three — the owner ranked carers in her head, which is the league table DEC-003 refuses; the three are the ones who could

Cut, and kept: a reason for no — a carer's reason is theirs; the owner never sees it, so it was never needed

Cut, and kept: map the columns by hand — the first nine sheets all had time · client · carer in some order; the parse guesses and step 2 catches it

The one content rule that is mechanically checkable. content-terminology-guard is on — a refused word in a string is caught at the write.

• plain over clever — giving up: personality in the microcopy
• brief over complete — giving up: the reassurance a longer message would give
• the owner's words over ours — giving up: consistency with what the industry calls things

Buttons: verb first, two or three words, sentence case — *Ask*, *Confirm Priya*, *Keep it* · Errors: what the owner should do, not what the system failed at · Empty states: what to do next, not "nothing here"

• Contrast: body text ≥ 4.5:1, large text ≥ 3:1 — check the *token pairs*, not screenshots
• Every interactive element has a visible focus state (2px `color.action.primary` outline, 2px offset)
• `prefers-reduced-motion` honored by every animation
• Nothing communicated by color alone — the chip is a shape first

8 declared text-on-surface pairs, 0 under AA — the table is in Colour → Contrast, once. A pair that fails is a token finding: fix it in docs/design/tokens.json and every screen moves.

• Focus — every interactive element has a visible focus state
• Keyboard — every flow completes without a pointer
• Screen reader — names, roles, the order things are announced
• Colour alone — nothing is communicated only by hue
• Motion — prefers-reduced-motion honoured by every animation
• Text over an image, a gradient, a translucent overlay — composites at runtime; the token pairs cannot see it
• 320px — reads and works at the narrowest width

Each needs a rendered page or a person. /design-review after walks them against shipped UI and writes not checked where it cannot see — the same word as here, never a pass by omission.

Counts, not verdicts: a decision handed is a screen that stayed on-system without anyone opening this page; an unanswered question is a fork nobody justified. What this cannot see is a write that diverged in a situation nothing ever decided — that is a hole above, not a number here.

Read it by rung: every observed method that says never is a design decision resting on a guess. The EVID record's method: field is what this reads.