Skip to content
Control Plane Labs

Editorial Policy

Last updated July 27, 2026

Purpose

This policy exists so that readers — and the ad networks that serve this site — can understand exactly how content is produced, sourced, reviewed, and corrected on Control Plane Labs. It applies to every article, every tool page, every cheat sheet, and every programmatic reference page on the site.

Sourcing standards

For any factual technical claim on this site:

  • Primary sources only. We link to the source specification (RFC, IETF draft, W3C spec), the primary vendor documentation (AWS docs, GCP docs, Kubernetes docs, CNCF project docs), or the primary vendor engineering blog.
  • No secondary blogs as primary sources. We may link to a well-written secondary explainer for context, but the load-bearing citation must be primary.
  • Numbers get sources. Every performance number, benchmark, pricing figure, or historical date is cited to a specific source. If we cannot source a claim within two searches, we cut it.

Review workflow

Every article follows the same workflow before publish:

  1. Outline. A named editor (Ben Ennis on pillar posts, Ben Ennis on all news pieces) writes an outline with the keyword, thesis, and required sources.
  2. Draft. The draft is written by the named editor or, on tool explainers and news round-ups, by AI-assisted drafting following the outline. Every draft cites its sources inline as it is written; sources are not bolted on afterward.
  3. Fact-check. A named editor reads every factual claim aloud against its source. Claims that cannot be re-derived from the linked source are removed.
  4. LLM-tell sweep. The draft is checked for common AI-writing tells (the words “delve”, “leverage”, “utilize”, “landscape”, filler transitions like “in today’s fast-paced world”). These are removed.
  5. Publish. The article ships with the named byline of the editor who fact-checked it, not the byline of the person or system that drafted it.

AI-assistance disclosure

Some articles on this site are drafted with AI assistance. When that is the case:

  • The byline is the human editor who fact-checked the piece, not an AI system.
  • The editor is a real person with a public profile.
  • Every factual claim in the draft is re-verified against a primary source by the named editor before publish.

We do not publish AI-generated text that has not been fact-checked by a named human editor. We do not use AI to generate quotes attributed to real people. We do not use AI to fabricate research or benchmark numbers.

Corrections

If we publish something incorrect:

  1. We correct the article in place.
  2. We add a dated “Correction” note at the bottom of the article describing what was wrong and what changed.
  3. Silent edits are never allowed on substantive factual claims. Typos and grammar edits do not require a correction note.

To request a correction, email ben@ennis-studio.com.

Updates vs. corrections

If we substantially rewrite an article — for example, because a spec has moved on or a vendor has renamed a feature — we bump the updatedAt date and add an “Updated” note describing the change. This is separate from a correction and does not imply the previous version was wrong at the time of writing.

Advertising and sponsored content

  • Display ads on this site are served by the ad networks disclosed in our privacy policy.
  • Sponsored posts, when they exist, are labeled “Sponsored by [advertiser]” above the fold and are excluded from our RSS feed and newsletter.
  • Advertisers do not see drafts before publication and cannot influence editorial coverage.

Conflicts of interest

Ben Ennis is the founder of Ennis Studio, which also operates CertIndex (a Certificate Transparency data API) and GuardHound (a domain security monitor). Some tools on this site are backed by CertIndex data. Where that is the case, the tool page carries an inline “Data from Certificate Transparency logs via CertIndex” footer. Articles that discuss Certificate Transparency in general disclose the relationship when relevant.

Contact

Editorial questions: ben@ennis-studio.com Corrections: ben@ennis-studio.com