A note on why I am publishing this now: I have had a number of people reach out wanting to engage with this work—to collaborate, to contribute, to produce their own analysis in a similar vein. I appreciate the interest. It is validating to know this work reaches people.

However, I have also observed a pattern. Many who are attracted to systems analysis are not yet equipped to do it. They have absorbed the conclusions and the vocabulary, but not the methodology. Engaging with them—gently redirecting, explaining why a particular approach will not hold up, sometimes urging them not to publish something that will be easily discredited—takes time I do not have. It bogs down the actual work.

This field guide is my attempt to address that problem at scale. It codifies what I have learned about how to do this work well, and it names the failure modes I have seen repeatedly. My hope is that it will serve as both an invitation and a filter: an invitation to those who are prepared to meet the standard, and a filter that saves both of us time when collaboration is not the right path.

After several years of investigating how power operates in West Virginia, I have developed an approach that distinguishes between the journalism that makes us feel good and the analysis that actually maps the machine. I am publishing this framework now because I have watched too many people mistake one for the other—sometimes from inexperience, sometimes from impatience, and sometimes from a desire to skip the hard work and jump straight to the conclusions.

The work I do is slow and unglamorous. Tracing money through donor-advised funds, reading 990 forms, mapping personnel overlap between think tanks and legislative bodies—none of this makes for exciting reading. The temptation to shortcut it, to reach for an emotional hook that makes the audience feel something without showing them the architecture, is constant. But shortcuts do not build understanding. They build reactions. And reactions fade.

This field guide is my attempt to codify what I have learned. It is also, frankly, a filter. I have learned that not everyone who is attracted to this work is prepared to do it.

Most investigative journalism fails to create structural change because it focuses on scandals—individual bad acts—rather than systems—incentive structures.

The press covers the “crime” but ignores the “design.” Individuals are punished, but the machinery continues uninterrupted.

The Dichotomy

The Scandal (Narrative Mode)

Focus: Individual bad actors. Timeline: Days to months. Causation: Linear. Resolution: Climax and closure. Legality: Usually illegal. Outcome: Emotional satisfaction.

The System (Structural Mode)

Focus: Incentive structures and legal frameworks. Timeline: Years to decades. Causation: Circular feedback loops. Resolution: None—the machine keeps running. Legality: Usually legal. Outcome: Understanding.

Why We Miss The System

Systems lack villains. Narratives need a face. Systemic capture is a decentralized network of faceless nonprofits and legal frameworks. No single “bad guy”—just a web of aligned interests.

The timescale mismatch. News covers what happened this week. Systems evolve over decades. The arc from Buckley v. Valeo (1976) to AFP v. Bonta (2021) is a 45-year story. No newsroom covers 45-year arcs.

The expertise gap. Mapping a system requires specialized knowledge in campaign finance law, tax law, and network analysis. The economic model of news cannot support this.

The lack of closure. Systems do not end. A dark money network capturing a court is not breaking the law—it is using the laws it helped write. There is no climax, only ongoing function.

Common Failure Modes

Over the years, I have watched many people attempt systems analysis and slip back into narrative mode without realizing it. The failures follow predictable patterns.

The Borrowed Villain

When an analyst lacks the evidentiary foundation to demonstrate how a current system operates, they reach for a historical comparison that carries pre-loaded emotional weight. “This is like the robber barons.” “This is like the company towns.”

The tell is extensive disclaimers. “I am not saying they are the same, but...” If you have to spend paragraphs explaining what you are not saying, you have already lost the argument. The disclaimers signal that you know the comparison is problematic, but you made it anyway because you did not have anything stronger.

The Vague Menace

Words like “dark money,” “corporate slush funds,” “manipulation,” and “shadowy networks” gesture at systemic problems without identifying specific mechanisms. They are the vocabulary of systems analysis without its substance.

Systems analysis names things precisely. It identifies the specific statute, the court case, the donor-advised fund, the personnel who moved from think tank to regulatory agency. If you find yourself using vague terms, stop and ask: Can I name the specific mechanism? If not, you are doing atmosphere, not analysis.

The Missing Feedback Loop

Narrative analysis is linear: bad actors do bad things, we should be upset. Systems analysis asks: How does this outcome make the next iteration easier?

A network funds a judicial campaign. The judge wins. The judge rules on donor privacy in a way that makes the network harder to trace. The network funds more campaigns. This is a feedback loop. If your analysis has a beginning and an implied end, you are telling a story, not mapping a system.

The Aesthetic of Rigor

The most dangerous failure mode. Some writers adopt the vocabulary—”architectures,” “mechanisms,” “structural capture”—without the underlying work. The language sounds sophisticated, but the evidence is absent.

The only test: Where are the receipts? Where are the tax filings, the court documents, the traced funding streams? If these are absent, you are looking at performance, not analysis.

This failure mode is dangerous because it discredits the methodology. Sloppy work that claims to be systems analysis provides ammunition to those who want to dismiss all such analysis as conspiracy theorizing.

Building On This Work Versus Appropriating It

I welcome collaboration. But collaboration requires shared standards.

Building on this methodology means engaging with the evidentiary standard. It means doing your own primary research—filing your own FOIA requests, reading your own tax documents. It means extending the analysis with new evidence, citing sources, acknowledging intellectual debts. It means being willing to be wrong.

Appropriating this methodology means taking conclusions and repackaging them in less rigorous form. It means borrowing the emotional resonance without contributing to the foundation. It means skipping the hard work and jumping straight to proclamation.

If you read this field guide and think “I am already doing this,” look again at the failure modes. The people most confident they have mastered the methodology are often the ones most deeply embedded in narrative thinking.

The systems I map are defended by sophisticated communications operations. These professionals find the weakest criticism and treat it as representative.

When someone publishes sloppy analysis that claims to be systems work, they hand ammunition to those whose job is to discredit all criticism. A poorly reasoned comparison, an unsupported assertion—any of these can be isolated and used to dismiss not just the individual writer but the entire enterprise.

This is why I am protective. Not gatekeeping for its own sake, but recognition that underdeveloped analysis actively harms the broader effort.

Methodology: How to Map a System

Phase 1: Map the network, not the incident. Do not start with the scandal. Start with the power node. Who decides who holds this power? Trace the commission, the appointments, the affiliations, the funders. Find the connective tissue—shared addresses, shared board members, shared funding sources.

Phase 2: Follow the money backward. Standard reporting: Donor → Candidate → Favor. Systems reporting: Outcome → Who benefited? → Who funded the actors? → Where did the money originate?

Phase 3: Identify the feedback loop. Stop looking for a beginning and end. Look for the circle. The output of the system becomes the input for its next iteration.

Phase 4: Name the architecture. Do not describe corruption as moral failing. Describe it as legal framework. “These politicians are corrupt” invites outrage. “The combination of Citizens United, McCutcheon, and AFP v. Bonta allows unlimited anonymous spending” identifies the levers that must be pulled.

The Citizen Investigator Checklist

When reading political news, ask:

* Does this story have a villain? Look for the people behind the villain who are not in the headline.

* Is the behavior illegal? If legal but harmful, it is a system. Systems operate within laws their beneficiaries helped write.

* Who wrote the rules? Who funded the people who wrote the laws that allow this?

* What is the timescale? If framed as recent, look for deeper history.

* Where is the feedback loop? How does this outcome make it easier for the same group to act again?

“Systems change when enough people can see them.”

The machine runs in the dark. It relies on complexity, opacity, and the assumption that nobody has time to trace all the connections. It relies on our preference for narratives over systems, for villains over architectures, for closure over understanding.

I have been doing this work for several years. I intend to continue. If you are prepared to meet the standard—to do the slow work, to build the evidence, to resist the shortcuts—I welcome your collaboration. If you are not yet there, I welcome your readership and your support. Both matter.

But I will protect this methodology from those who would dilute it. The stakes are too high to do otherwise.

This Substack is reader-supported. To receive new posts and support my work, consider becoming a free or paid subscriber.

This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit carrieclendening.substack.com