How Source Checks and Fact Review Work at 420.place

1. Build a risk-based queue

Articles are prioritized by subject risk, age, source state, legal or medical change signals, and whether a prior review receipt exists.

2. Check sources without overstating the result

A successful request shows that a page responded; it does not prove that the page still supports the claim. Timeouts, access limits, and TLS failures are indeterminate. Replacement sources must be checked for claim equivalence.

3. Map material claims

For each changed high-risk claim, the evidence record identifies jurisdiction, effective date, supporting source, and whether support is direct, partial, contradicted, unverified, or indeterminate.

4. Separate review roles

Source retrieval, editing, independent criticism, verification, and release approval are separate responsibilities. Medical or legal specialist review is recorded only when a qualified reviewer and exact-version receipt exist.

5. Publish with evidence and readback

The release is tied to a clean commit, content hash, immutable package hash, explicit target and deletion scope, rollback information, and post-deployment checks.

The process is designed to make limitations visible. It does not guarantee that educational content is complete or suitable for an individual decision. See Editorial Standards and Responsible Use.