# Moats of Context Blog

Opinionated essays and notes about context, AI agents, durable value, and the judgment required to use generated work well.

## Posts
- [Drift Is Contextual Tech Debt](https://moatsofcontext.com/posts/drift-is-contextual-tech-debt/): Vibe coded systems often drift because the context guiding future changes falls out of sync with the code.
- [Monorepos Pool Context](https://moatsofcontext.com/posts/monorepos-pool-context/): For AI-assisted development, a monorepo can be useful because it pools related project context in one visible, versioned place.
- [Codex Usually Does Not Need Memory](https://moatsofcontext.com/posts/ai-memory-usage/): Persistent AI memory should be turned on for a clear reason, because repo context is often a better source of truth for Codex-style software work.
- [Is AI-Generated Code Copyrightable, and Does It Matter?](https://moatsofcontext.com/posts/is-ai-generated-code-copyrightable-does-it-matter/): AI makes code easier to regenerate, so the durable value is less often the code itself and more often the context, data, trust, and execution around it.
- [Good, Fast, Cheap, and the AI Agent Tradeoff](https://moatsofcontext.com/posts/good-fast-cheap-ai-agents/): AI agents make fast and cheap easier, but they make human judgment about what counts as good more important, not less.
- [Astro First for AI-Managed Sites](https://moatsofcontext.com/posts/astro-first-ai-managed-sites/): Why this proof of concept starts with Astro instead of a more opinionated digital-garden generator.
- [Is Your SaaS Resistant to Being Replaced by AI Agents?](https://moatsofcontext.com/posts/is-your-saas-resistant-to-ai-agents/): A practical framework for evaluating whether a SaaS product can survive when customers use AI agents with their own data and context.

## Notes
- [AI Resistance Signals](https://moatsofcontext.com/notes/ai-resistance-heuristic/): A practical lens for judging whether a SaaS product can be replaced or bypassed by AI agents.