Field notes, not thought leadership.
Short notes from the principals who build content platforms, search visibility, and AI systems. Each gives you a check to run.
9 published
AI Rescue · · 2 min read
Your AI-built app passes login. Can it keep accounts apart?
Sign in as one test account and try to open another account's private record. The app should refuse.
Enterprise Content Platforms
Contentful and Sitecore architecture, design, build, hosting, and integration. Content platforms that survive year three.
- 3 min read
Your CMS belongs in the production incident timeline
Add CMS activity to your incident timeline so responders can spot a content change that broke production.
- 2 min read
Before you reuse a CMS entry, decide who can change it
Ask an editor to change one branch's hours and predict every page that will change.
Search & AI Visibility
Technical SEO, analytics, and GEO (Generative Engine Optimization). Be found by people and cited by the AI answering them.
- 2 min read
AI search starts with a question your page can answer
Take one question buyers ask and read your page's answer on its own. Could they act on it?
- 2 min read
Use Core Web Vitals to investigate customer friction
Put a performance change beside customer behavior and release dates, then decide what to investigate.
AI Engineering
AI products and AI-native delivery. We build with the tools we sell. It's why a three-person studio ships like thirty.
- 2 min read
Review an agent skill like a software dependency
Trace what a shared agent skill can run and access before your team installs it.
- 2 min read
Treat a model upgrade like a permission change
Before switching models, give both the same task on a safe copy and compare what each tries to change.
- 2 min read
Stopping an AI agent means checking what can still run
Cancel a harmless test run, then check every system it touched for work or access that is still live.
- 2 min read
Your fallback model needs the same data rules
Make your approved AI model unavailable in a test and see where a sensitive request goes next.
