# AI Can Extend a Plugin But Not Own Its Accountability ## Claim AI can write, extend, and troubleshoot a plugin's code, but accountability for that code running on a live site — the responsibility a customer is actually renewing for — stays with a human vendor. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds for commercial software where a customer relies on someone being answerable when something breaks in production — security, compatibility, data integrity. - Doesn't claim AI-written code is lower quality; the claim is narrower — that responsibility is a relationship, not an output, and AI has no standing to hold it. - Weakens where "accountability" itself becomes contractually assignable to an AI vendor or insurer, which would move the responsibility rather than eliminate the distinction. ## Evidence Casey Burridge, arguing about what a WordPress plugin license actually pays for as AI erodes documentation-based support and routine feature updates, names accountability as the value that survives: a customer can get AI to extend or patch a plugin, but when it breaks on their production site, AI isn't who they call, and it isn't who's liable. > [!quote] > "AI can extend a plugin, but it can't take responsibility for it." ## Links - [[Product & Startup Instincts MOC]] — the line between what a product's AI can do and what its owner still answers for - [[3. Resources/Permanent Notes/AI Erodes the WordPress Plugin Value Props Pushing Monetization Toward SaaS and Services]] — because extends; that note maps where plugin monetization is heading (SaaS/services), this one names the specific non-transferable value driving the shift. - [[3. Resources/Permanent Notes/A Mature Plugin License Can Cost Less Than Rebuilding Its Integration Network]] — because contrasts; that note locates durable value in integration depth, this one locates it in accountability — two different (compatible) answers to the same "what am I paying for" question. - [[3. Resources/Literature Notes/Reconsidering the WordPress business model (Casey Burridge)]] — because evidence-for; the source case this claim is drawn from. ## Tests / falsifiers - Watch whether AI vendors start offering indemnification or liability products for AI-generated code changes — if that becomes normal and trusted, accountability itself becomes purchasable from an AI vendor, and this claim's boundary shifts. - Survey plugin customers on renewal decisions: if "who do I call when it breaks" isn't actually a stated reason people renew, the claim's practical weight (not its logical structure) weakens. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/Reconsidering the WordPress business model (Casey Burridge)]] — names accountability as the plugin-license value AI cannot replicate.