How a public playlist link becomes a shareable personality read — in four diagrams. Each isolates a different layer of the system, drawn in one visual language.
AI passes turn a raw tracklist into a shareable read. The two writing passes are each wrapped in a deterministic, code-based verifier — not another model — that either ships valid output or feeds the exact failure back and forces a corrective regeneration. The card deck ships first; the long-form essay is generated later, in its own worker.
Intake returns in milliseconds. The slow work — fetching tracks, three AI passes, rendering a mosaic — is handed to detached CLI workers that run off-request while the browser polls for state. No queue, no Redis, no cron. The read self-drains; nothing is scheduled.
Every read carries three independent status fields, each advanced only by code. The main lifecycle streams fine-grained progress to the loader; the deep-dive and mosaic run on their own. An atomic claim stops two triggers double-running the same job — and a job stuck past 300s becomes reclaimable.
After the cards land, a detached worker builds the share image with zero AI — pure PHP GD. It pulls an album cover for every track, sorts them by brightness, tiles the brightest into the playlist's name in a flowing script, dims the rest into the backdrop, and composites the letterforms at pixel resolution so the cursive stays fluid.