Editorial policy

We write for operational usefulness. Every guide should help a reader make a decision, create an artifact, run a test, or improve a real on-call practice.

Principles

01Practical before promotional: Educational pages must stand on their own without requiring a product purchase.
02Disclose relationships: MonoDuty is built by the same team. We disclose that relationship wherever product context matters.
03Date vendor facts: Pricing, feature availability, migration status, and support dates can change. We show the source and review date.
04No invented evidence: We do not publish fabricated statistics, benchmarks, customer quotes, or reliability claims.
05Human review: AI may assist drafting or structure. A named human reviews content before publication, and a page that has not been reviewed says so.
06Corrections: Material corrections include an update note with a date.
07Safety and legal boundaries: Compensation, labour, security, and compliance content is informational and does not replace qualified advice.

The publish gate

A page is not published until it has a clear reader job, a direct answer, a concrete artifact or tool to hand the reader, a source for every dated claim, an assigned author and reviewer, and complete metadata. This is enforced by the build: content that is missing any of these fails to compile rather than quietly shipping.

A page whose review is still outstanding is visible on the site with a notice saying so, and is excluded from the sitemap and from search engine indexing until a named human has reviewed it.

Freshness

Different content decays at different speeds, so each page carries a freshness class that sets its review interval.

Content type	Review interval
Vendor pricing and features	30 days
Migration and deprecation	30 days
Security, legal and compensation	90 days
Tool methodology	90 days
Evergreen guides	180 days
Templates	180 days
Glossary	365 days

An overdue page is not automatically wrong. But where a critical changing claim cannot be re-confirmed from a current public source, we remove it or mark it clearly as not confirmed.

Corrections

Anyone can report a correction. Material corrections are published with a date and a short change note; typographical fixes are not logged separately. If a vendor asks for a correction we ask for a source, and no commercial relationship determines an editorial outcome. If a score methodology changes, its version increments and previously shared results continue to show the version that produced them.