infrastructure

The five-step evolution of how I reach the development environment on the Mac Mini from an iPhone in a playground. The useful insight is that where you build shapes what you build.

Long-running tasks fail silently if the session dies before the result is ready. This is the runner I built to make "email me when done" actually mean that. Retry loop, fallback email paths, and a last-ditch file.

What backups, what intentional exclusions, and a sequence that reconstitutes the whole personal AI operating environment in under an hour. The honest version, including the accepted gaps.

What happens when one person uses an AI coding assistant as the primary interface to a real physical and operational life, and systematically fixes every failure that occurs along the way.

Every automated helper I built to make my system more reliable ended up making it less reliable. Why, with dated incidents and what I run instead.

The difference between using AI a lot and being AI-native: infrastructure as the binding constraint, not model capability.