How This Site Works: Obsidian, AI Agents, and Safe Publishing

The problem

I learn and build in short sessions, but the useful parts end up scattered across notes, chats, screenshots, and repositories. Maintaining a portfolio as a separate activity would quickly become another unfinished project.

A private-first pipeline

Obsidian remains the capture layer. New notes and phone uploads enter a private inbox and are never public by default. An AI-assisted review turns selected material into a draft, removes sensitive context, and proposes a visual treatment.

Publication requires explicit metadata confirming that the item is public, reviewed, cleared, and unrelated to company material. The build fails when that contract is missing.

Why the safety gate matters

Convenience should not make publishing careless. The company project vault is useful context for private reasoning, but it is not a content source. Keeping capture and publication separate lets the workflow stay fast without turning every note into a disclosure risk.