Home / Articles / Who will fix your mess? An answer to HBR's "deployment gap" from what this site has already published / Versions / v1.6.0
Who will fix your mess? An answer to HBR's "deployment gap" from what this site has already published: what changed in v1.6.0
From v1.5.0 (2026-10-19, d303ce0f1) to v1.6.0 (2026-10-27, db67c5ce1), paragraph by paragraph.
0 paragraphs added, 0 removed, 10 changed in place, 46 unchanged. About 0 words added and 240 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names.
2 unchanged paragraphs
!shot hb-map.webp | images/ | The points in the HBR article's public summary and in Olivier Laplace's post, oneach thematched left, andto the article on this site that answers each one, on the right: explorer coding, the citizen developer, knowledge that maintains itself, how cheap it is to undo, the expert founders, software vendors as villagers and the fork next door.it. | comparison
15 unchanged paragraphs, under In short {#in-short}, What they argue {#argument}, The prototype is not the mess {#brief}
!shot ec-handover.webp | images/ | Explorer coding and theits handover that makes it last:handover: explorers build by talking to an agent, and what they build is the brief;build, villagers maintain it, with policies, data handling and tests;maintain, town planners own the code in production. From Explorer coding. | architecture
3 unchanged paragraphs, under The gap is a handover {#handover}
!shot hb-wardley.webp | images/ | The deployment gap on a Wardley map: the prototypehandover infrom genesis,explorers builtto byvillagers explorers; the tool people rely on, made reliable by villagers; the platform it runs on, owned byto town planners. The gap is the handover from explorer to villager. | architecture
1 unchanged paragraph
!shot cz-path.webp | images/ | From the spreadsheet to the town planners: theThe citizen developer's path,path from what people built with what they controlled, to the application they need,spreadsheet to the villagers and town planners who make it last. From The citizen developer. | architecture
3 unchanged paragraphs, under "Nobody knows how it is built" can be fixed {#record}
!shot kq-loop.webp | images/ | Knowledge that maintains itself: sources kept in their own vocabularies,sources, agents that keep a semantic graph of them up to date, and people and agents briefed from the graph. From Knowledge that maintains itself.it. | architecture
1 unchanged paragraph
!shot hb-graph.webp | images/ | One article as a graph, as this site publishes it for every article: Explorer coding's twelve nodes, from "vibe coding, the word" to "town planners own it", with the edges between them and the quotes that carry them. A screenshot of theThe graphs page on newsroom.sgit.ai.newsroom.sgit.ai, showing Explorer coding as a graph of twelve nodes, with edges and quotes. | medium | comparison
!shot rf-board.webp | images/ | A prototype that is ready for the villagers: Mondweep Chakravorty's SGit × Ruflo run,run: twelve steps, five worked, three safeguards refusedrefused, asone intended, recall by meaning marked asthing not tested. From What if an agent loses its workspace? | comparison
5 unchanged paragraphs, under The bonus test is accountability {#bonus}, Build where it is cheap to undo {#undo}
!shot cu-spectrum.webp | images/ | The spectrum:spectrum across,of how muchcostly itan costsoutput is to undo, from a two-way door to a one-way door; up,against how mature theits controls and the record are, from explorer to town planner. Where an output sits decides how much a person needs to be in the loop. From How cheap is it to undo? | comparison
2 unchanged paragraphs, under Partner with the specialist, and the specialist may be the founder {#specialist}
!shot ef-playbooks.webp | images/ | Two playbooks: the outsider who finds a gap, raises firstgap and hires the experts;experts, and the expert who lives the problem and builds it with agents. From The expert founders. | comparison
2 unchanged paragraphs, under The specialist should be the villager underneath you {#villagers}
!shot vt-map.webp | images/ | A product as explorers, villagers and town planners: users explore on top, talking to the app and writing the best brief the vendor will get;explore, the vendor maintains the customisations, and runs the platform. From Software vendors should become villagers and town planners. | architecture
12 unchanged paragraphs, under And who will fix your mess? {#fix}, What this does not claim {#limits}, Where this comes from {#sources}