claim candidate goes to: this-edition T town planner
The bonus test: if nobody will put their name or their bonus on it in production, it is not ready to be in line
HBR's test for a chief executive, would your team accept a bonus tied to how this tool performs in production, is the town planner's accountability by another name: the moment someone takes the code and answers for it. The industry already says whoever ships code is responsible for it however it was written: the Linux kernel's rules say AI agents must not add Signed-off-by tags and only humans can certify the Developer Certificate of Origin, and Fedora's proposal says the contributor is always the author and fully accountable. An explorer cannot be made accountable for code they never read; the team the work is handed to can, and the town planners above all.
Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).
Where it comes from
- Who will fix your mess? An answer to HBR's "deployment gap" from what this site has already published The bonus test is accountability (newsroom)
- Explorer coding Villagers and town planners (newsroom)
What it answers in the 2018 book
- Are you a pionner, Settlers or Town Planners answered outline, Life Patterns
- Don't touch production answered outline, Security
Where it goes
Chapter Explorer coding, not vibe coding, and the handover, part The frame (drafting); topic Explorers, villagers and town planners (Wardley's frame).
Other ideas proposed for the same chapter: Explorer coding: what people call vibe coding, done as exploring, The deployment gap is a handover, and the prototype is the best brief, Design, the design canon and Christopher Alexander: the villager's and town planner's craft, Gen ZX are developers: coding with agents the explorer coding way, which is what vibe coding should be called, A villager move: no new features while you move, or nobody can tell which change broke what, 'Nobody knows how it is built' is fixable: make the agents leave a record, a mandate, a memory and a graph, An explorer-coded app is a brief, not a product: not ready to be in line, and the further towards commodity the fewer agents in line, Every product needs an explorer version, with paid conversions to a villager product and a town planner one.
Node idea:the-bonus-test-is-accountability in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.