---
{
  "n": 59,
  "title": "Every viewer heading and label says plainly what it is about",
  "abstract": "",
  "refs": [],
  "seen": [
    "agent"
  ],
  "data": {
    "keywords": [
      "heading",
      "label",
      "FormField",
      "SectionHeading",
      "wording"
    ],
    "keywords_in": "text",
    "environment": "main",
    "injected": true,
    "files": {}
  },
  "created": 1791268019.038537,
  "updated": 1791287306.236265,
  "deleted": 0.0,
  "completed": 0.0,
  "outcome": "",
  "type": "rule"
}
---
The user, messages 16499, 16839, 16844, 16989, 16992 and 16993 (2026-10-06), after 'Where the words count', 'Watch for the words in', 'This project', 'This browser' and 'Stop the journal' as tab names: viewer text reads like Linear, GitHub or Vercel. A place (page, tab, group, sidebar item) is a short noun: Settings, Project, Browser, Services, Updates, Plugins; never 'This project' or a phrase. A button is a verb for what happens: Stop, Install, Copy link, Pause the plan. A heading names what the reader looks at, and its options finish its sentence: 'Trigger when' / 'A word is written'. Plain literal words: no metaphor or whimsy ('kettle on, waiting'), no app speaking as I, none of the journal's internal words (row, hook, nudge, engine, slate). One word for one thing everywhere, sentence case, as short as it can be while clear. Applies to designers' prototypes, helpers' builds, the viewer's JavaScript lists, feature details, and shipped sequence and trigger titles alike.