Each current watch item carries a dated review log. This board shows where each one stands: its status, when it was last reviewed and when the next review is due, whether it is overdue, the authoritative source to check, the next action, and which public pages it appears on. It is read-only and deterministic — dates come from the committed review log, nothing is fetched, and no current number is asserted.
- Overdue items are flagged and presented publicly as "Needs review", never as fresh.
- Next action tells you exactly what to re-check and update.
- Route impact shows the blast radius of a review on the public site.
✓ No overdue reviews at the current reference clock.
All watch items
Review packet — fill this in for every add/update
The discipline for keeping the watchlist honest. Full prose template: docs/watchlist-review-packet.md. If a fact is not source-backed, do not publish it.
- Item id: The watch-item id being added or updated (e.g. oil-hormuz).
- Source checked: Which authoritative free source you actually opened.
- Source URL: The deep link you reviewed.
- Date checked: ISO date you reviewed the source — becomes lastReviewed.
- What changed: Cautious note. If no new number is source-backed, say so — do not invent one.
- What did not change: What you confirmed is unchanged (e.g. scenario stays assumption-based).
- Numeric data source-backed?: Yes/No. If No, publish no number — keep it qualitative.
- Scenario links need update?: Whether the related scenario/briefing links still resolve and fit.
- Caveats: Confidence and limits — what this does not establish.
- Keep active / watch / quiet / retire: The editorial status after this review.
- Routes affected: Which public routes this item appears on (blast radius).