Project Loom
A Research Framework for Understanding Why Governance Fails — and How to Fix It
What Is Project Loom?
Project Loom is an open research initiative that maps, analyzes, and improves governance mechanisms through transparent systems modeling, implementation analysis, and decision support. It treats governance as an empirical object of study—something that can be dissected, measured, and rebuilt.
Loom is not a think tank. It is not a consultancy. It is a research operating system: a set of conceptual tools, case study protocols, and analytical frameworks designed to answer one question with surgical precision:
Why do announced policies fail to become actual outcomes?
The gap between political ambition and institutional capacity is not a bug in the system. It is the system. Project Loom exists to make that gap visible, measurable, and—eventually—bridgeable.
Why Does This Exist?
American governance is optimized for announcements, not outcomes. Politicians promise. Agencies procure. Contractors bill. Citizens wait. And somewhere in the machinery between the press conference and the drinking water, things fall apart.
Loom builds its analysis from documented cases:
- Student Loan Forgiveness — how a legally vulnerable pathway collapsed under judicial review
- Healthcare.gov — how operational incapacity destroyed a politically supported policy
- Flint Water Crisis — how institutions with information and authority still failed to act
- Operation Warp Speed — how temporary capacity assembly can bypass institutional debt
- California High-Speed Rail — how long-horizon projects outlast their political and financial foundations
- United States Digital Service — how a governance system can build durable self-correction capacity after catastrophic failure
Each case follows a standardized diagnostic protocol. Each tests the ontology against real-world outcomes. The goal is not to score points but to build a vocabulary for the thing we are all experiencing but cannot name.
How Did This Start?
Project Loom emerged from a simple observation: the machinery of American governance is failing in predictable, repeatable ways. The same patterns appear across domains, administrations, and political coalitions. The failures are not random. They are structural.
Loom began as an attempt to name those structures. It has evolved into a multi-module research program with a core ontology, a growing case library, and applied frameworks for intervention design.
The EROS Governance Analysis Framework
EROS (Executive Reversal Operating System) is one module under the Loom umbrella. It provides a six-stage sequential methodology for analyzing governance mechanisms and designing transitions:
| Stage | Question |
|---|---|
| 1. Institutional Mapping | How do power, authority, funding, and decision-making actually flow? |
| 2. Dependency Analysis | Which systems depend on which others, and what breaks if one changes? |
| 3. Capacity Assessment | Can the responsible institutions actually perform the required work? |
| 4. Implementation Design | What are the administrative, legal, and operational steps required? |
| 5. Transition Risk Modeling | What are the foreseeable failure modes, bottlenecks, and capture pathways? |
| 6. Accountability & Resilience Evaluation | How do we embed oversight, transparency, and recovery into the design? |
This framework is politically neutral. It studies governance mechanisms, not ideology. The same analytical tools apply regardless of administration or policy domain.
Who Is This For?
| You are… | Loom can help you… |
|---|---|
| A researcher or academic | Develop rigorous, cross-domain frameworks for studying institutional failure and transition |
| A policy professional or legislative staffer | Design implementation pathways that account for capacity constraints and political fragility |
| An organizer or advocate | Map the dependency chains and veto points that determine whether a campaign’s demands can actually be executed |
| A journalist | Analyze governance failures with conceptual precision rather than narrative convenience |
| A technologist or designer | Build tools, databases, and interfaces that make institutional machinery visible and navigable |
| A citizen | Understand why the systems that affect your life behave the way they do |
What You Will Find Here
- Case Studies — Detailed analyses of governance failures and successes, each following a standardized ten-stage diagnostic protocol
- The Ontology — Canonical definitions of Loom’s core concepts and their relationships
- The Framework — Documentation of the EROS Governance Analysis Framework and its application
- Projects & Outputs — Active research projects, intervention designs, and public-facing writing
- Literature Notes — Sourced material, research references, and theoretical foundations
A Note on Method
Project Loom does not start from theory and look for examples. It starts from cases and builds theory. Every concept in the ontology must earn its place by explaining something that actually happened. If a concept cannot be operationalized—if it cannot be tested against a documented case—it does not belong in the framework.
This is empirical research, not opinion journalism. The goal is to build tools that are useful, not to build a brand that is popular.
Loom Is Being Built in Public
The research system itself is under development. We distinguish between what has been built, what is being tested, and what is only planned.
For a quick explanation: What Loom Is Building
For researchers, auditors, developers, and contributors: Research & Contributor Roadmap
These pages document the development process rather than presenting unfinished capabilities as established ones.
Explore
Project Loom investigates why policies fail even when well-intentioned, using cross-case analysis of systemic breakdowns.