A Human Approval Gate for AI-Generated History Fact Cards
An agent generates fact cards in Sanity and I'm the approval gate in the middle. Generating a card, checking it against Exa source excerpts, rejecting it with feedback, then approving and publishing.
Transcript
this is California Black Stories My Sanity Challenge Path Two Project I run a Facebook page about Black history in my home state, and I built this app to prepare fact cards with their sources and review decisions attached. The public library lets me find posts, read their captions and citations, and download the card image. It includes drafts as well as published posts.
I start with broad topics and ask for five specific claim ideas. These are candidates, not verified facts. I can choose an idea or enter a topic of my own. Verification happens before I create a card. Exa finds source excerpts, and the fact checker breaks the claim into checkable parts.
Each part is labeled supported, unsupported, or contradicted. Supported means an excerpt backs it. Unsupported means supplied excerpts don't address it. Contradicted means an excerpt conflicts with it. The linked Exa sources stay visible with excerpt previews and publication dates when available, so I can inspect the evidence myself.
If part of the claim isn't supported or conflicts with the sources, The app suggests a correction while keeping the supported details. Retry Source checking is available when I want more evidence that adds sources while retaining the earlier excerpts. If I edit a suggested correction, the edited wording needs verification. Applying this suggestion uses the findings already on screen.
It doesn't run another search or audit. I can inspect the corrected fact before creating the card, and it still needs my editorial approval. Now I create the card and submit it for review. The image is a template rendered 1080 by 1080 PNG, not AI generated artwork. Sanity stores the fact, caption, citation, source URL, template id, and uploaded image as structured fields.
The workflow moves the completed post to in review. Let's open this post in studio. Let's look at the Facebook caption. The question at the end is have you ever visited this iconic site? Publishing is gated by the workflow's actual approval. If I reject a post I leave feedback and a background Sanity function handles the revision.
Here I'm changing only the engagement question so it keeps the fact, source, and card image. The workflow shows a temporary warning while the background step runs. It clears when the revised post is ready for review. An image only request re renders the existing fact while a factual change goes through source verification. The app updates the existing post and sends it back to review.
I can then approve or request another revision. Let's just look back in the editor to see if that question was changed. It has. What do you find most fascinating about the history of the Watts Towers? Once I'm satisfied I approve the post, Then I use Studio's Publish button.
A background function automatically completes the workflow, so I don't need a second confirmation in the workflow view. This publishes the document to Sanity. This demo doesn't send a post to Facebook or Instagram. My biggest learning was that a content workflow needs more than a status dropdown. Sanity Workflows let me model approval, rejection with feedback, and what happens next.
Customizing Studio brought generation and review into the same workspace. I built this with Codex and refined it by testing real claims and the full editorial loop. AI helps prepare the posts. I make the approval decision.