Field Notebook · Vol. 1
The notebook.
A working journal. Field notes from the AI workspace. Bugs, decisions, gotchas, infrastructure I've built and re-built. The kind of stuff I'd write in a paper notebook if my desk wasn't already covered.
Entries
most recent first · 34 of 34 June 2026
April 2026
04 · 15 Building an AI Content Team: 7 Roles, 7 Agents, One Dashboard 04 · 12 GEO Citability: The Goal Isn't to Look Good, It's to Get Cited 04 · 10 Don't Tunnel Dev Servers: A 90-Second Near-Miss 04 · 09 Convergent Logging: Your AI Workspace Has Two Histories 04 · 08 Local-First Cron Architecture for AI Workspaces 04 · 05 9 Ace: A VS Code Extension for Markdown Annotation and Feedback 04 · 03 The Human Is the Orchestrator (and That's Where Mistakes Creep In) 04 · 02 Autonomous Agents Need a Director
March 2026
03 · 30 Master Source vs. Living Copies 03 · 29 What I Check Before Shipping a Workspace 03 · 27 VS Code's CustomTextEditorProvider Is the Right API for Preview Extensions 03 · 25 My Workspace Is a Harness (and Anthropic Just Wrote the Retro) 03 · 21 Automatic Model Routing Doesn't Exist Yet 03 · 17 Cost-Proportional Context Injection 03 · 17 I Built a Pipeline That Couldn't Deploy Itself 03 · 12 MCPs Are a Transitional Technology 03 · 11 iCloud Path Resolution Breaks AI Tool State 03 · 11 macOS Python Quirks for AI Workspaces 03 · 09 Git Branches Don't Belong in Brain Repos 03 · 08 Your AI Coding Assistant Forgets Everything. Here's How to Fix That. 03 · 08 Suggest, Don't Block: AI-Assisted Product Management 03 · 03 A Goal System Your AI Can Read
February 2026
January 2026
What this is. The Notebook is a separate surface from /writing. Writing is for finished arguments. The Notebook is for the working stream: the bug I just hit, the architecture decision I just made, the gotcha that cost me an afternoon. Lower polish, higher frequency, narrower audience. If you build with AI tools, this is the surface you'll want.