← ALL COLLECTIONS

FIELD GUIDE 001 · Publishing systems

The anti-slop publishing stack

Five rules for using automation without sanding the judgment, evidence, and useful friction out of editorial work.

Automate evidence and production work. Keep the question, thesis, and final claim in human hands.

THE READER QUESTION

Which parts of an editorial workflow can be automated without turning the result into generic content?

Start with a reader, not a topic

A topic is an area. A reader question is a job. The second gives an editor a reason to reject material that may be popular but does not help anyone decide or act.

Write the reader and the decision question before research starts. If a draft cannot name both, it is not ready for prose.

Map claims before writing sentences

Polished language can hide a thin evidence base. A claim map makes the gap visible while it is still cheap to fix: what is fact, what is interpretation, what is advice, and what remains unknown.

Draft from the map. If a source disappears, every claim that depends on it should become visible at once.

Show who made it and how

A byline alone does not explain the work. Readers should be able to see who owns the final judgment, how automation helped, when the page changed, and which sources support it.

This is useful editorial context first. It also leaves a clean record for search systems and future editors.

Keep one canonical work

A newsletter, social post, partner embed, and search page do different jobs. They should share the approved evidence and update record, but they should not repeat the same block of copy.

The canonical page holds the complete argument. Each other surface earns its place by inviting, summarizing, excerpting evidence, or leading the reader back to the full work.

Make automation earn authority

The first useful automation removes repeat work: intake, deduplication, source labels, claim checks, formatting, and version tracking. Publication is a different right.

Keep final approval human during the pilot. Expand authority only after the system has passed several full cycles without unsupported claims or review debt.

SOURCE LEDGER

Read the evidence

  1. primary guidance

    Creating helpful, reliable, people-first content

    Google Search Central · accessed 2026-08-10

    OPEN SOURCE
  2. primary guidance

    Google Search's guidance on using generative AI content on your website

    Google Search Central · accessed 2026-08-10

    OPEN SOURCE
  3. technical standard

    Article

    Schema.org · accessed 2026-08-10

    OPEN SOURCE

UPDATE HISTORY

What changed

First approved edition. Added the source map, role labels, creation note, and publisher embed contract.