Why Rewind Exists—And How We Built It to Last

Static Edge Hosting on Azure SWA

Every entry and Saturday Morning TV schedule compiles ahead of time via Astro Content Collections and Pagefind into pure static HTML, CSS, and binary search shards deployed to Azure Static Web Apps—no live database to crash under traffic spikes and zero runaway server bills.

How the Anti-Slop Curator Pipeline Works

Telling an LLM to crank out 500 articles from memory produces bland, hallucinated filler. Instead, Rewind uses an offline, human-in-the-loop workflow (pipeline/cli.mjs + the rewind-curator Antigravity skill):

1. Queue Topics: Add toys, cartoons, commercials, or junk foods to pipeline/queue.json.
2. Ground Facts First: Run npm run pipeline -- research <slug> to pull Wikipedia summaries, Wikimedia Commons CC-licensed photography, and Internet Archive commercial embeds into pipeline/drafts/<slug>.research.json.
3. Draft in Authentic Voice: Author via the workspace rewind-curator skill (or npm run pipeline -- generate <slug>) following our strict editorial style guide.
4. Lint Against Slop & Hotlinks: npm run validate verifies Zod schemas, citation links, allowed media hosts, and rejects banned AI clichés both locally and in GitHub Actions CI before deploying to Azure SWA.
5. Human Review & Promote: npm run pipeline -- promote <slug> graduates reviewed drafts into src/content/entries/.