Step 1
Source watchlist
Add official pages here first. A page needs a category, priority, frequency, and reason before it becomes part of coverage.
/sources
Method
The workflow is intentionally simple: official sources first, fixed intake fields, impact scoring, then a public note or a digest item only when there is something a seller can act on.
Step 1
Add official pages here first. A page needs a category, priority, frequency, and reason before it becomes part of coverage.
/sources
Step 2
Every discovered change gets a source URL, snapshot, raw diff, change type, and first-read note before it becomes public content.
Obsidian intake template
Step 3
Only publish changes that score at least 6, have a 3-point risk dimension, or touch deadlines, fees, account health, funds, or seller protection.
/method
Step 4
A public note must explain what changed, who should care, why it matters, what to check, and the official source.
/change-log and /alerts/[slug]
Step 5
Digest items reference public alert slugs first, so the email, archive, and site stay in sync.
/digest and Buttondown
Impact scoring
A change becomes publishable when it scores at least 6, has a 3-point risk dimension, or touches deadlines, fees, account health, funds, listing risk, or seller protection.
Could it affect violations, AHR, deactivation, appeals, or enforcement?
Could it affect listing approval, suppression, restricted products, IP, or catalog edits?
Could it change fees, reimbursements, held funds, protection eligibility, or margin?
Could it change an operating clock, queue cadence, evidence step, or SOP?
Does it affect a narrow category or a broad seller/operator segment?
Can a seller check, route, edit, train, or escalate something now?
Current bridge