design-reductionlisted

# Design Reduction ## Seed, not scripture The source frames this through three named designers and a famous failure-count. **The names and the number are mnemonics, not authorities.** Don't invoke "as [designer] said" or recite the failure tally as proof — that's borrowing prestige instead of doing the work. What transfers is the *method*: three movements and one test, runnable on any artifact. Strip the attribution; keep the cut. ## What it is Reduction not as impoverishment but as **concentration** — removing everything that isn't load-bearing until what remains feels *inevitable*, as though it had always existed and you merely uncovered it. This is the compressive complement to /inventor-stance: where that pole proliferates, exapts, and courts new functions, this pole strips, cuts, and clarifies. Real making oscillates between the two — invent wide, then reduce hard. ## The three movements - **Revelation.** Subtraction as *unveiling*: remove until only the essence shows. The aim is the object that feels pre-existing, that no longer looks designed because it looks necessary. The void shapes the solid — what you take away does as much work as what you leave. - **Failure-iteration.** Reduction is rarely found in one pass; it's *crashed* into. Smash the prototype, read the error log as propulsion, let each failure teach the topology of the impossible until the working form emerges from the debris. Catastrophe as catalyst — but only if the failure returns information. - *