Notion as the Human Control Plane for Local-First Content Ops
maps Notion receipts onto joelclaw's local-first Brain/NAS evidence loop without making Notion canonical
wizard-content-os is the Badass Courses namespace for local-first content operations around wzrrd.sh. The useful bit is the boundary: Brain and local artifacts are canonical evidence, while Notion is the shared human control plane.
That’s a clean split. Notion can coordinate strategy, status, and receipts without becoming the place where raw transcripts, large media, or privileged media bytes go to rot. Those stay on the three-body NAS under the local /Volumes/Home/video/badass/... path, which keeps the expensive, private shit where it belongs.
The repo is also a proving ground before anything graduates into wzrrd. apps/marker-rig handles the local Stream Deck marker rig, apps/notion-worker handles the Notion Workers sandbox, and future Pi extensions or skills can grow out of the same loop.
This is useful because it treats content production like infrastructure: local evidence, shared control plane, operator receipts, and promotion only after the tool proves itself. Boring in the right way.
Key Ideas
Brainand local artifacts are the source of truth;Notionis only the shared control plane.- Raw transcripts, large media, and privileged media bytes stay off
GitHuband live on thethree-bodyNAS. apps/marker-rigkeepsStream Deckinput close to recording and highlight workflows.apps/notion-workergivesNotionadapters a sandbox before they become durable operator tooling.wzrrdstays generic;Wizard ShitorBadass Coursesspecifics prove themselves here first.- The stack is intentionally strict:
pnpm,Turborepo,TypeScript,tsgo,Ultracite,Oxlint, andOxfmt.