# AI-native software delivery

Essays and notes tagged AI-native software delivery.

- [The AI-native SDLC: when typing code stops being the bottleneck](https://muthub.org/writing/the-ai-native-sdlc.md) (Jul 28, 2026): AI has made writing code cheap. Verification, trusted context and human judgment are now the scarce resources, and teams that redesign their lifecycle around them will pull away from teams that only add assistants.
- [If you can't prove why an AI wrote it, you can't ship it](https://muthub.org/writing/if-you-cant-prove-why-an-ai-wrote-it.md) (Feb 24, 2026): Shipping AI-generated code without recording where it came from is unmanaged risk. Regulated teams need deterministic provenance for non-deterministic models: line-level attribution, Git-native session history and AI bills of materials.
- [Three architectures for AI coding agents, and how enterprises should choose](https://muthub.org/writing/three-architectures-for-ai-coding-agents.md) (Dec 16, 2025): Platform-embedded, sandboxed and evolutionary coding agents each earn trust in a different way. Then the editor became a fleet manager. Choose and govern agents by how their work will be verified.
- [Spec-driven development for regulated industries: audit the contract, not every line](https://muthub.org/writing/spec-driven-development-for-regulated-industries.md) (Oct 21, 2025): For complex work in regulated sectors, prompt-to-code cannot pass an audit. Making the specification the contract an AI must fulfil can, provided the spec stays anchored to the code and machines check conformance.
- [From pair programming to fleet management](https://muthub.org/writing/from-pair-programming-to-fleet-management.md) (Dec 15, 2025): Editors now run local, background and cloud agents side by side. The leadership job shifts from writing code to designing the system that writes it.
- [Beyond vibe coding: specs as executable artifacts](https://muthub.org/writing/spec-kit-beyond-vibe-coding.md) (Sep 8, 2025): Ad-hoc prompting yields code that looks right but misses intent. Making the spec the gated source of truth is how AI-assisted delivery becomes repeatable.
- [Technical debt is an architectural liability](https://muthub.org/writing/technical-debt-is-an-architectural-liability.md) (Jun 23, 2025): Technical debt is a strategic risk rather than messy code. Coding agents make continuous paydown affordable inside everyday work.

---
Muthukrishnan (Muthu) Bommiah · https://muthub.org · Views are my own and do not represent my employer.