Elon Filter
The Elon Filter is a structured decision-making framework inspired by the engineering and operational principles described in the Book of Elon, while extending them to serve the mission of Open Source Ecology. It combines first-principles reasoning, simplification, rapid iteration, accountability, and evidence-based decision making with additional principles of radical transparency, open documentation, reproducibility, modularity, and distributed production. Each filter poses a concrete question, defines a measurable pass condition, and specifies supporting evidence. Together, the framework guides contributors toward practical technologies that are not only effective and rapidly developed, but also openly shared, locally reproducible, and capable of expanding resilient, regenerative, and abundant productive capacity for everyone.
The Elon Filter synthesizes Elon Musk's engineering heuristics with Open Source Ecology's principles of open-source development and distributive economics, creating a framework for building an open-source civilization.
| Filter | Core Question | Pass Condition | Evidence | Score 1–5 |
|---|---|---|---|---|
| Purpose Filter | Does this directly advance the OSE mission and make an open-source civilization more achievable? | Produces a clear, measurable contribution to distributed production, abundance, resilience, or human capability. | Mission outcome, beneficiary, measurable impact | |
| Utility Filter | Does this solve a real and important problem? | Creates practical value rather than merely generating discussion, novelty, or activity. | User need, deployment case, performance result | |
| First-Principles Filter | Are we reasoning from physical, economic, and human constraints rather than precedent? | Requirements can be traced to necessary constraints rather than convention or inherited assumptions. | Cost model, physical limits, test data, explicit assumptions | |
| Requirement Filter | Who created each requirement, and why is it necessary? | Every requirement has a named source, defensible rationale, and measurable purpose. | Requirement owner, justification, consequence of removal | |
| Deletion Filter | What parts, features, steps, meetings, or rules can be removed completely? | Unnecessary complexity has been deleted before optimization begins. | Deleted components, reduced process steps, eliminated overhead | |
| Simplicity Filter | Is this the simplest system that can reliably achieve the intended result? | The design minimizes parts, dependencies, special cases, and cognitive load. | Part count, process steps, dependency count, assembly time | |
| Build Filter | What working artifact exists? | The proposal has produced a prototype, testable implementation, physical build, or other inspectable artifact. | Prototype, CAD, code, test unit, demonstration | |
| Evidence Filter | What experiment or measurement can resolve uncertainty? | Major claims are supported by tests, measurements, or direct observation. | Test protocol, measured result, comparison data | |
| Replication Filter | Can an independent person or community reproduce this? | A competent external builder can replicate the result using available documentation and tools. | Build instructions, BOM, source files, replication report | |
| Modularity Filter | Does this create a reusable and interoperable module? | The contribution can be combined, replaced, repaired, or reused without redesigning the entire system. | Interface specification, modular CAD, standard connections | |
| Transparency Filter | Can a newcomer understand what was done, why it was done, and how to reproduce it? | Decisions, assumptions, failures, source files, and procedures are openly documented. | Decision log, source repository, documentation, test history | |
| Proximity Filter | Are decision-makers directly connected to the work and its users? | Important decisions involve people who build, operate, maintain, or use the system. | Direct observation, operator feedback, build participation | |
| Velocity Filter | What useful result will ship in the current work cycle? | The work has a short feedback loop, a dated deliverable, and no avoidable waiting. | Demonstration date, iteration duration, completed milestone | |
| Ownership Filter | Who is the single accountable owner? | One person is responsible for the next measurable deliverable, even when many people contribute. | Named owner, deadline, acceptance criteria | |
| Automation Filter | Has the process been validated, deleted, simplified, and accelerated before automation? | Automation is applied only to a stable and necessary process. | Validated workflow, cycle-time data, automation rationale | |
| Abundance Filter | Does this increase access to essential productive capacity? | Reduces the cost, scarcity, skill barrier, or dependency associated with producing essential goods. | Cost reduction, accessibility gain, local production capability | |
| Civilization Filter | Does this strengthen distributed, open, regenerative, and locally autonomous production? | Builds long-term public capacity rather than creating avoidable centralization or dependency. | Open licensing, distributed deployment, repairability, local sourcing |