Skip to content
andydataguy
AI & SYSTEMS

My content system rewrites failed paragraphs while keeping approved text

Each paragraph has its own database record and receives checks before assembly.

Each paragraph is stored as its own row, so fixing one that sounds like AI leaves every approved paragraph untouched.

An AI writer pays out a long draft with one weak stretch. The draft is stored as a tower of rows, one per paragraph. A check reads each row; the row that sounds like AI slides out, is rewritten and slides back while every other row stays still.
~90%
less context per edit (design estimate)
1 row
per paragraph, each with its own status
5
passes: strategy, structure, drafting, refinement, assembly
0
approved paragraphs changed by a fix
Case Studies

Context

A project of my own that took two years: finding out why AI writing loses quality over a long document. I wanted long-form content (novels, courseware, complex proposals) that could beat expert human work on nuance, literary devices and structural coherence, at scale.

Problem

Large models are bad at holding quality across thousands of tokens.

Approach

I borrowed the idea from compilers, which break code into small units before optimizing it. My system parses inputs (research, user notes, job posts) into one database row per paragraph, each with its own status.

Stack

  • Python
  • SQL, one row per paragraph
  • Checks for style, AI-sounding lines and logic
  • Modular backends for Markdown, PDF, and HTML

Result

1 paragraph
targeted per failed check

It generates content node by node. Five passes (strategy, structure, drafting, refinement, assembly) build a document, and the refinement pass checks each sentence and paragraph on its own for cadence, passive voice, logical flow and lines that sound like AI before anything is compiled. A paragraph that fails is regenerated on its own instead of re-rolling the whole draft.

Impact

A fix touches one paragraph and leaves every approved paragraph exactly as it was. By my design estimate, an edit needs about 90% less context than re-rolling the whole draft.

Lessons

Give the model one paragraph at a time. It writes a brilliant paragraph far more often than a brilliant chapter, so the document is built and checked a row at a time.

Who this is for

For teams whose long AI-written documents read as machine-made in places, and who want those places fixed without touching what's already approved.

Get a quote
On this page

The method behind this result