What to include
Page URL, what looks wrong, what you expected instead, and if possible a reference point that shows the mismatch clearly.
Corrections
If something is wrong, the site should say so and fix it fast.
The Patch is still in active cleanup. The right response to a bad value, stale event line, or incorrect pet metadata is not to hide it. It is to surface it, verify it, and update the site.
What happens next
The report should be reviewed, checked against the shared data or source page, and then fixed publicly if the report is valid.
Where to send it
Right now the most reliable public routes are the site repository and the publication on Substack, because both already exist and are active.
Public site repository
Use the repository when the issue is specific to a page, dataset, or implementation detail.
Open repositoryPublication feedback route
Use the publication when the issue is more editorial, strategic, or tied to broader site direction.
Open SubstackEditorial policy
If the issue is really about what should count as current guidance, what should be archived, or how updates should be disclosed, use the editorial policy as the reference point.
Open editorial policyParent guide
If the concern is family-facing safety, scam awareness, or calmer trading habits for younger players, the parent guide is the better starting page.
Open parent guide