# Cheaper Mechanics Never Substitute for Editorial Judgement ## Claim When a tool makes publishing something cheaper, the remaining hard problem is still deciding what deserves to be published. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds wherever a capability's cost — implementation effort, tooling friction, time — was previously the binding constraint on whether it happened at all. - Breaks where cost was genuinely the only obstacle and the editorial answer was already settled beforehand — a bulk migration, for instance, where "what" is fixed and only "how" was expensive. - Does not claim editorial work is harder than mechanical work in absolute terms, only that it doesn't shrink when mechanical work does. ## Evidence The MCP protocol's 2026-07-28 revision makes running a stateless MCP server cheap enough for static and edge-hosted sites — the last structural implementation objection is gone. What the revision does not resolve is which capabilities any given site should actually expose to agents. > [!quote] > The protocol got simpler. The editorial question is untouched, and it was always the real work. ## Links - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — because applies-in; agent-facing interface decisions are exactly where this recurs. - [[3. Resources/Permanent Notes/Canonical Sources Reduce Interface Drift]] — because applies-in; picking a canonical source doesn't decide what belongs in it — that's the same editorial gap this note names. - [[3. Resources/Permanent Notes/The Agent That Captured Everything Is the Wrong Reader to Find the Story]] — has evidence from: capture and story-finding need different readers (Meyer). ## Tests / falsifiers - Find a case where a genuine capability-cost reduction (not merely implementation-cost) also resolved the corresponding editorial question — for example, a tool that made a *bad* publishing decision structurally impossible, not just cheaper to reverse. That would be a counterexample. - If site operators who adopt a cheaper publishing tool ship materially better editorial decisions than before (not just more output), the claim weakens. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Literature Notes/MCP 2026-07-28 the spec catches up with the static web]] — reports the protocol simplification and states this as its closing thesis.