v0.12.91: @newsroom.writer: Who will fix your mess?

A new article answering Harvard Business Review's "Turn Vibe-Coded Prototypes Into Tools Your Company Can Actually Use" (16 October 2026, Parra Moyano, Schmedders, Laplace and Torben-Nielsen) from articles this site has already published. It works from the article's public summary and Olivier Laplace's post about it, since the full text is behind a paywall, and checks the McKinsey 32% figure the post cites against McKinsey's report.

The argument: the deployment gap is the handover from explorers to villagers and town planners; the prototype is the best brief, not the mess; agents that keep a mandate, a memory and a graph make the architecture knowable; the bonus test is the town planner's accountability; build where it is cheap to undo; the specialist may be an expert founder and should be the villager underneath your explorers; and open source means more than one party can fix it. New figures: the post's points mapped to the articles that answer them, and the deployment gap on a Wardley map; it reuses seven figures from the articles it cites and a screenshot of the graphs page.