weekly-watchlisted

# Weekly watch A briefing that a busy reader can act on. One PDF, no more than a page or two, where every item earns its place by changing what the reader should build, buy, or stop planning. The discipline that makes it worth reading is subtractive: most of what happens in a week does not qualify, and the value is in what gets dropped. --- ## Step 0: establish the watch Ask before the first run, and store the answers in the corrections log at the bottom of this file so they are not asked again. 1. **What is the watch about?** The market, technology or industry being followed. 2. **Who reads it, and in what capacity?** This is the question that decides everything else. A person piloting a product, a person buying capacity, a person regulating a sector and a person writing code want four incompatible briefings. Name the capacity explicitly, and name the ones it is not. 3. **What are the standing sections?** Two to four themes, in a fixed order, so the reader learns where to look. 4. **Where should the file go, and under what name?** 5. **Any house style?** Fonts, an accent colour, British or American English. Otherwise the document stays plain. If the reader's capacity is not clear, ask again rather than guessing. Every wrong framing of this watch has come from assuming the reader wanted technique when they wanted market movement, or the reverse. --- ## The materiality test Apply it before the verification gate, because it drops more. An item ea