First-Principles Reduction

What problem does it solve?

Question, delete, and simplify BEFORE optimizing or automating — Musk's Algorithm in strict sequence. Trigger on: 'let's automate this', 'we need to optimize', 'this is too complex', 'how do we scale this?', feature bloat, process overhead, any instinct to improve something that might not need to exist.

Core Features & Use Cases

Five steps, in mandatory sequence. Each must complete before the next. The most common mistake: doing them in reverse. Core inversion — adding feels productive, deleting feels destructive. Optimizing feels intelligent, questioning feels ignorant. Automating feels modern, manual feels primitive.

• Step 1 — Question the requirements
• Step 2 — Delete the Part or Process
• Step 3 — Simplify and Optimize
• Step 4 — Accelerate Cycle Time
• Step 5 — Automate Sequence Diagnostic — for any proposed improvement, identify which step it represents. If it's at Step N but Steps 1 through N-1 haven't been performed — stop and go back. Inversion Test — for any system you're about to improve: write what you want to do, invert: what could you DELETE instead?, invert again: what REQUIREMENT could you question? If the inversion reveals a simpler path, take it. Anti-Patterns Premature automation, Optimization worship, Addition bias, Requirement inertia, Sunk cost preservation, Selective application Connections
• Signal Discrimination — Step 2 (deletion) IS signal discrimination applied to components and processes
• Deep Deliberation — Step 1 (questioning requirements) demands deliberation before action
• Constraint Propagation — each deletion propagates; trace effects before and after
• Coherence Design — the algorithm produces coherence by removing elements that don't strengthen the whole
• Tools for Thought — Step 5 (automate) raises the amplification vs. automation question: should this be automated or should users retain understanding?

Quick Start

Apply the five-step first-principles reduction to a project by questioning requirements, deleting unnecessary parts, simplifying the remaining design, accelerating cycle time, and only automating if justified.