The problem
Generating a draft is easy. Knowing where its claims came from and whether someone has reviewed it is harder. That’s the part I wanted this workflow to handle.
What I built
The workflow suggests angles, gathers sources, writes an article, and adapts it for three other channels. A claim-to-excerpt map keeps each claim beside its source. The checks flag unsupported claims and formatting problems before review.
How review works
A content manager requests the work, and a different editor approves the revision. Open blocking flags stop approval. I kept separate states for queued, manual, sent, and failed posts so a queued draft doesn’t look like a successful publication.
Where the project stands
The build records include a generated content pack, gate tests, database tests, and concurrency checks. It was built locally and didn’t have a hosted URL at that point. The source and test records are linked here.
What testing caught
Three bugs came down to the same thing: the code calculated one result and saved another. I had to check that the review gate and the stored record agreed.
Recorded build evidence · September 2026. The figures here come from those test records.