How We Publish
Editorial Standards
Robotic Lifestyle combines automated drafting with human oversight. Every build runs editorial QA gates that block duplicate paragraphs, empty headings, unused sources, taxonomy drift, and duplicate event coverage before changes ship.
Verification
Every story must carry required metadata (title, slug, category, published date) and either cite at least one source or be explicitly labeled as an opinion piece with no external sources.
Source Integrity
Sources only appear when they are cited in the body. Extra links are clearly labeled as Further Reading and are not presented as reporting inputs.
Structure
Our QA gate removes empty headings and duplicate paragraphs, and it fails the build if near-duplicate blocks or empty sections remain.
Taxonomy
Sections are validated against a canonical allow-list. Mismatches (for example, consumer robot stories tagged as humanoids) are rejected and corrected before publishing.
Duplicate Events
Stories published within a 72-hour window are clustered by similarity. Only the canonical version is promoted in feeds; superseded versions are archived with a redirect note.
Style
We block filler ledes, vague endings, and rhetorical questions at the open and close. The lede must state who did what, when, and why it matters within the first two sentences.
Corrections
Each article can carry a changelog with timestamps. Published and updated dates are displayed alongside a dedicated Corrections page that explains how to request fixes.
What we run before publishing
- qa:editorial — fails on duplicate paragraphs, empty headings, unused sources, missing metadata, taxonomy drift, and unresolved duplicate-event clusters.
- qa:style — warns (or fails in strict mode) on filler ledes, rhetorical questions in the first/last paragraph, lazy endings, and missing concrete ledes.
- Unit tests, linting, and type checks for both the API and frontend.
See the Corrections page for how to request changes to a published article, or email corrections@roboticlifestyle.com with the URL and issue.