{"slug": "notes-on-the-twelve-factor-app-for-the-ai-age-part-1", "title": "Notes on the Twelve-Factor App, for the AI Age (Part 1)", "summary": "A developer revisits the Twelve-Factor App methodology from 2011 in the context of modern AI coding agents and AI-native applications, finding that while the original factors remain valid, the environment around them has changed significantly. The notes walk through each factor with concrete actions tagged for machine or human audit, emphasizing that most AI safety properties require human oversight. The piece includes falsifiable expiry triggers for each claim, acknowledging that current constraints will evolve.", "body_md": "Adam Wiggins wrote the Twelve-Factor App in 2011 for stateless web processes on a PaaS, and it held for over a decade. I recently sat down and re-read it in the era of AI coding agents and AI-native apps, and took notes along the way: which factors still hold, which bend under the new load, and a few concerns the original never had to name.\n\nWhy I wrote this: I kept seeing teams (mine included) apply the twelve factors to AI systems as if nothing changed, and other teams throw them out as if everything did. Neither felt right. Nothing here retires a 2011 factor. The environment around them changed, not their truth, and that seemed worth writing down carefully.\n\nTwo premises drive the notes:\n\nFrom there I walk through all twelve factors and end each one with concrete things to do, tagged by who can actually check them: a machine at build time, or a human via audit. Most safety properties of AI systems fall in the second bucket, and pretending otherwise is, in my opinion, the characteristic failure of this era.\n\nThese notes are dated. Read them as of 2026. Every durable claim carries a falsifiable expiry trigger, because most current constraints won't age well, and I'd rather be checkable than right-sounding.\n\nFull piece here: [Notes on the Twelve-Factor App, for the AI Age (Part 1)](https://farhat-hadi.medium.com/notes-on-the-twelve-factor-app-for-the-ai-age-part-1-ac4fde34da3c)\n\nPart 2 will cover what the twelve don't govern at all: the input, the evaluator, the acting agent, per-call economics, and data lineage through a model call.\n\nIf you disagree with any of the expiry triggers, that's exactly the feedback I'm hoping for.", "url": "https://wpnews.pro/news/notes-on-the-twelve-factor-app-for-the-ai-age-part-1", "canonical_source": "https://dev.to/hadifrt20/notes-on-the-twelve-factor-app-for-the-ai-age-part-1-4dn", "published_at": "2026-07-18 12:01:51+00:00", "updated_at": "2026-07-18 12:29:09.669884+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "ai-safety", "ai-infrastructure", "ai-products"], "entities": ["Adam Wiggins", "Twelve-Factor App", "Farhat Hadi"], "alternates": {"html": "https://wpnews.pro/news/notes-on-the-twelve-factor-app-for-the-ai-age-part-1", "markdown": "https://wpnews.pro/news/notes-on-the-twelve-factor-app-for-the-ai-age-part-1.md", "text": "https://wpnews.pro/news/notes-on-the-twelve-factor-app-for-the-ai-age-part-1.txt", "jsonld": "https://wpnews.pro/news/notes-on-the-twelve-factor-app-for-the-ai-age-part-1.jsonld"}}