Evidence and method

Editorial and corrections policy

Every changing technical claim must trace back to a source, a verification date, or a reproducible test.

Last updated:

Source hierarchy

  1. Official Cloudflare developer documentation, product announcements, and observed status evidence.
  2. Runnable, tested minimal examples in this repository.
  3. Third-party comparisons with explicit assumptions, region, and verification date.

Old screenshots, search snippets, and unverified AI output do not substitute for primary evidence.

Verification and freshness

Plans, pricing, limits, compatibility, and dashboard paths change. Relevant pages expose lastVerified; runnable projects also record lastTested. Sitemap dates come from the same verification field rather than build time, avoiding artificial freshness.

AI assistance boundary

Content and code may use AI for drafting, translation, retrieval, or review. AI output is not evidence: publication still requires source allowlists, bilingual pairing, link checks, type checks, tests, and build gates. Pricing, permissions, remote mutations, and destructive commands retain human confirmation gates.

Bilingual synchronization

A Chinese source revision invalidates its English translation hash. The content audit blocks publication until the English meaning is synchronized and the new revision is explicitly accepted.

Corrections workflow

  1. Record the canonical URL, disputed text, and discovery date.
  2. Attach an official source, reproduction steps, or response evidence.
  3. Classify the issue as factual error, staleness, translation drift, or unclear wording.
  4. Fix both languages and regenerate Markdown, OG, and sitemap assets.
  5. Publish reader-significant corrections in the changelog.