A Portfolio That Lints Its Own Content

Portfolios rot in a specific way: a path moves, a poster is renamed, a video is swapped for a better cut — and some page keeps pointing at the old file. Nothing crashes. The page just quietly gets worse.

This site now lints its own content. Every project, note, and studio edition lives in a content layer (JSON on disk today, a database behind the same contract when needed), and a verification script walks all of it before a change ships: every published media path must exist, slugs must be unique, and the curated links between works and journal notes must point at things that are real and published.

A project can only join the walk by carrying both an editorial priority and a verified poster + direct loop; the script fails the build check if either half is missing. That is what keeps the walk honest — the route cannot silently render an empty room or a broken frame, because the failure happens at review time, in text, where it is cheap.

Two smaller pieces close the loop. New journal entries are scaffolded as drafts — published: false by construction — so nothing reaches the live journal without an explicit editorial pass. And the weekly newsletter runs the same philosophy in reverse: an automation proposes a draft from the freshest published work, and only a human confirm can send it. The pattern is the same everywhere: machines verify and propose; a person decides what goes out.