claim candidate goes to: this-edition V villager
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
An explorer-coded app may look and feel like an application, but nobody has read the code or validated the architecture, so it is not ready to be in line, in the path of work other people depend on. Dependence comes quickly: once something is used it is mission critical, even for one person if it replaced how they work, and from then on new versions cannot break it. The direction is set by where the code sits on the map: the further towards commodity, the fewer agents in line and the more deterministic the code; a model has no place in line on a mission-critical path.
Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).
Note. Pairs with the-handover (the move itself) and the-bonus-test-is-accountability (who answers for it). 'A model has no place in line on a mission-critical path' is quoted in the article from Dinis's code review piece.
Where it comes from
- Explorer coding Not ready to be in line; Villagers and town planners (newsroom)
What it answers in the 2018 book
- Legacy Applications answered outline, Concepts
- 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, The bonus test: if nobody will put their name or their bonus on it in production, it is not ready to be in line, Every product needs an explorer version, with paid conversions to a villager product and a town planner one.
Node idea:not-ready-to-be-in-line in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.