Editorial checklist

Use this before publishing a new page or major update.

Basics

[ ] Title is short and specific: max 100 characters, no em-dashes/en-dashes (hard rule; python3 scripts/audit_titles.py --check enforces it in scripts/build.sh). Nav titles and H1s carry the NAME, not the thesis; the thesis belongs in the opening paragraph.
[ ] Links are clickable Markdown links
[ ] Sources are linked inline
[ ] Page has the right section (Groups / People / Ops / Tools / Patterns / Notes / Blog)
[ ] Tags are added when useful

[ ] Recent entries title states the FINDING a reader cares about (plain-language claim about the vulnerability, campaign, or technique), never the scanning process (no sweep ordinals, high-water bookkeeping, "new page + folds" work-status, feed-head/KEV tracking, or commit hashes). Operational detail lives in the linked page and source-index. (Dean request, 2026-11-10)
[ ] Facts are separated from inference
[ ] Primary name follows operator, maintainer, project, or other firsthand usage when durable public sourcing supports it
[ ] Alternate names are attributed to the vendor or report that used them
[ ] Motivation is phrased carefully
[ ] Tooling is described at the right level of detail
[ ] People pages only name individuals who are clearly supported by public sources
[ ] Team dynamics are only stated when the sources support them
[ ] No unsupported human attribution