10 to the 23 AI logo

Domain Atlas

Content moderation & editorial AI

This domain covers two AI deployments that both decide what the public sees: automated content moderation on platforms, and AI-drafted editorial content in newsrooms. In moderation, machine classifiers remove content proactively — often before any user has seen it — at a scale no human review could match, and the governing fact is that the human review and appeals path is the error-correction loop, not an optional add-on. A platform's own natural experiment made this concrete: when human reviewers were sent home during the pandemic and the platform deliberately chose over-enforcement, automated removals more than doubled, appeals roughly doubled, and the reinstatement rate on appeal jumped from about a quarter to about half — direct evidence that the automation was making roughly twice the rate of catchable errors, visible only because the appeals queue caught them. Two things follow. Proactive removal acts before anyone sees the content, so an over-broad takedown is invisible unless an appeals path surfaces it — and in documented cases automated removal destroyed evidence of war crimes with archival access declined, an irreversible action with no correction loop at all. And over-enforcement versus under-enforcement is a chosen trade-off: when you cannot review everything, you are choosing which error to make, and that choice is a governance decision, not a technical default. In the newsroom, AI-drafted articles published under a human byline without disclosure are an accountability failure of a different shape — one outlet's audit found it had to correct a large share of its AI-written articles, so the review that a byline implies was not actually performed. The Lab networks model only the deploying organization — its classifiers or drafting tools, its reviewers, editors, and appeals functions, and its enforcement or publication records; the people whose content is moderated or who read the articles sit outside the dynamics, and no user or reader outcome is computed on any diagram.

Use cases

What AI is doing here

Automated content enforcement

Predictive

Machine classifiers and hash-matching that remove content proactively — often before any user has seen it — at a scale no human review could match, where the removal happens before there is any signal it was wrong, so an over-broad takedown is invisible unless an appeals path surfaces it.

Appeals & the error-correction loop

Predictive

The human review, appeals queue, and external-oversight functions that catch the errors automated enforcement makes at scale — the error-correction loop a natural experiment showed is load-bearing, since removing human review roughly doubled the rate of removals later reinstated on appeal.

Editorial AI drafting

Generative

AI that drafts published editorial content, often under a human byline — where the byline implies a review the reader trusts, and an outlet's own audit finding it had to correct a large share of its AI-written articles shows that review was not actually performed and the AI use was not disclosed.

Case files

What has gone wrong and right

Documented deployments, presented as model organizations calibrated to the evidence, with full citations.

System map

Who is in the system and what pushes on it

Who is in the system

  • Frontline workers. Caseworkers, screeners, eligibility staff — the operator network whose judgment the system augments or erodes.
  • Supervisors & QA. The institutional correction layer: overrides, second reads, quality review.
  • Agency leadership. Owns procurement, policy, and the authority map; answers for the system publicly.
  • Served people & families. Those the decisions land on. Deliberately outside the PAN dynamics — their outcomes are measured, never simulated.
  • Regulators & oversight bodies. Boards, auditors, data-protection officers, inspectorates — external correction capacity.
  • Advocates & community organizations. Surface harms institutions do not see; historically the earliest accurate signal.

Dominant pressures

  • Reviewer bottleneck. One fixed-capacity checking stage sits between AI output and consequence; everything queues behind it.
  • Austerity & recovery incentives. Cost-cutting and overpayment-recovery targets tilt the system toward denial and enforcement errors.
  • Vendor opacity. The deploying institution cannot inspect the model, data, or update pipeline it is accountable for.
  • Data & policy drift. The world, the intake process, and the rules change under a system trained on how things used to be — two mechanisms with different remedies: the statistical properties of what the system processes move (concept drift), or the mixture of inputs arriving in deployment differs from the mixture it was trained on (covariate shift).
  • Compliance over substance. Paper controls (sign-offs, checklists) satisfy audits while the behavior they describe erodes.

Governance

Questions leaders should be asking

  1. 1. Automated enforcement removes content at a scale no human review could match, and often before anyone has seen it — so is the human review and appeals path resourced as the error-correction loop it actually is, or treated as an optional add-on to an automated decision that is really the decision?
  2. 2. When you cannot review everything, over-enforcement and under-enforcement are a chosen trade-off — you are deciding which error to make — so is that choice being made deliberately and owned as a governance decision, or defaulting to whatever the classifier does at the threshold someone set once?
  3. 3. A proactive takedown acts before any user sees the content, so an over-broad removal is invisible unless an appeals path surfaces it — and some removals (evidence of atrocities, for instance) are irreversible with no preservation path; is anyone measuring the errors the automation makes before they are seen, and preserving what cannot be un-removed?
  4. 4. An AI-drafted article published under a human byline implies a review that the byline stands behind — so when a large share of such articles later needs correction, was the review actually performed, and is the use of AI disclosed to the reader who trusts the byline?

For the actions behind these questions, see the Practice Library.

Seeing your organization in this domain? Mapping its actual pathways, pressures, and correction capacity is engagement work.

Work With 1023AI