SFX

Editorial methodology

This page explains exactly how the technology analysis on this site is produced, so you can judge it on its process rather than on its tone.

Where stories come from

Candidate stories are collected from a fixed registry of trusted publishers — primarily the official engineering and research blogs of the organisations that build the technology, plus recognised standards bodies and security advisories. Secondary technology publications are used for context, never as the sole basis for a claim. No source outside that registry is ever fetched.

The role of automation

Discovery, source verification, drafting, translation, image generation and quality checking are automated. There is no routine human editorial review before publication. I state this plainly rather than implying an editorial desk that does not exist. I remain responsible for the system, its source registry and its quality thresholds, and I correct errors when they are reported.

Facts before prose

Before anything is written, each accepted story is reduced to a fact dossier: the primary claim, the primary source, supporting sources, exact dates and figures, named products and organisations, and any unresolved uncertainty. Article generation may only use facts recorded in that dossier. Quotes, benchmarks, prices, dates and release states are never invented — if a detail is not in the dossier, it does not appear in the article.

Quality gate

Every draft is scored on factual support, source quality, originality, usefulness, duplication, language quality and SEO safety. A draft must clear a high numeric threshold and every hard gate — sourced claims, no duplicate topic, no clickbait, valid structured data, clean links — or it is rejected. Rejection is the default outcome when anything is uncertain. Fewer articles is always preferred over a weak one.

Translation

The factual master version is written in English and validated first. Only then is it translated into the site’s other seven languages. Names, numbers, dates, URLs and technical terminology must survive translation unchanged, and each translation is validated for that parity before it is published. A translation that fails validation is not published.

Corrections

If you find an error, tell me and I will correct or withdraw the article. Every article links its sources so any claim can be checked independently.

Report an error