Sleuth Report: The Incompetence Defense: When Government Failure Begins to Look Like Sabotage

Cybersecurity researcher and disinformation analyst Jackie Singh offers a useful framework for examining institutional failure in The Incompetence Defense. Her central argument is captured in a phrase she calls Singh’s Law: “Any sufficiently advanced incompetence is indistinguishable from sabotage.”

Singh’s essay does not discuss Jeffrey Epstein or the Epstein files. Its relevance to EpsteinWiki lies in the analytical method it proposes. When failures become repeated, foreseeable, measurable, and resistant to correction, investigators should stop treating incompetence as a complete explanation. They should document outcomes, identify decision makers, compare failures with stated goals, and examine who benefits from the resulting disorder.

This framework is particularly useful for evaluating the Justice Department’s troubled Epstein files disclosure. Missing records, shifting page totals, files removed after publication, inconsistent redactions, exposed survivor information, broken downloads, and unexplained gaps may each be described as mistakes. Taken together, however, they demand a more serious institutional inquiry.

Key Takeaways

• Jackie Singh argues that incompetence can become operationally indistinguishable from sabotage.
• Singh’s Law does not prove intent. It establishes a threshold for deeper investigation.
• The essay warns that Hanlon’s razor can become an excuse for ending inquiries too early.
• Singh recommends focusing on observable outcomes rather than trying to read the minds of decision makers.
• Repeated failures should be measured through incident reports, access logs, missing records, reversals, costs, delays, and beneficiaries.
• Singh’s article does not mention Jeffrey Epstein and should not be presented as direct evidence about the Epstein files.
• Her framework can be applied to the Justice Department’s Epstein disclosure because the failures are repeated, documented, and consequential.
• The correct investigative question is not simply whether officials were incompetent. It is whether their conduct repeatedly produced the same protective or obstructive result.

Who Is Jackie Singh?

Jackie Singh is a cybersecurity professional, disinformation researcher, and former campaign security specialist. Her work frequently examines information systems, institutional accountability, cybersecurity failures, and the way unsupported claims become accepted as facts.

In The Incompetence Defense, Singh begins with a problem involving the provenance of her own words. Google’s artificial intelligence summary reportedly described her aphorism as widely attributed to her even though she could not find evidence of that wider attribution.

Singh argues that the system did not discover a documented consensus. It generated the appearance of consensus and presented that appearance as established fact.

Her response was to create a primary source documenting when she first published the phrase and what she intended it to mean.

That lesson is immediately relevant to archival investigations. A claim repeated across hundreds of websites does not become primary evidence. Investigators must locate the original statement, document, recording, or database record.

What Is Singh’s Law?

Singh’s Law states that any sufficiently advanced incompetence is indistinguishable from sabotage.

The phrase adapts the structure of Arthur C. Clarke’s observation that sufficiently advanced technology can become indistinguishable from magic. It also responds to Hanlon’s razor, the familiar advice against attributing to malice what can be adequately explained by stupidity.

Singh does not claim that every institutional failure is sabotage. Her argument is that there is a point at which the distinction becomes less useful to the investigator.

If an institution repeatedly creates the same harmful result, receives warnings, reverses its decisions, destroys its own operational capacity, and continues using the same methods, incompetence cannot serve as the end of the analysis.

The wreckage is observable even when intent remains disputed.

Why Hanlon’s Razor Can Become an Investigative Sedative

Hanlon’s razor can be a useful warning against conspiracy thinking. It reminds investigators not to infer secret intent from every error.

Singh argues that the principle can also be abused. Officials responsible for destructive outcomes can invoke confusion, haste, technical limitations, or poor communication to prevent further scrutiny.

Under that version of the incompetence defense, every incident is treated as an isolated mistake. The inquiry ends before investigators examine whether the same people, procedures, or political interests repeatedly benefited from the failure.

Singh calls her formulation an anti razor. Instead of choosing incompetence or malice at the beginning, investigators document the pattern first.

That approach is particularly valuable when the available evidence proves what happened but does not yet establish why it happened.

The Historical Meaning of Sabotage

Singh traces the word sabotage to the French verb saboter, which referred to clumsy or poor work. The popular story about workers throwing wooden shoes into machinery is probably apocryphal.

The more relevant historical meaning involved the deliberate performance of inefficient work. Workers could limit production, follow procedures so rigidly that work stopped, or make an operation fail while maintaining the appearance of ordinary labor.

Singh also points to the United States Office of Strategic Services Simple Sabotage Field Manual. The manual described methods that could obstruct organizations while appearing to be routine incompetence.

Those methods included sending decisions through unnecessary channels, referring matters to committees, demanding excessive caution, debating precise wording, and multiplying procedural obstacles.

The power of those techniques came from their deniability. Each action could be defended as normal administration.

Observable Damage Matters More Than Claimed Intent

Singh draws a distinction between malice and sabotage. Malice exists inside a person’s mind. Sabotage can be studied through results.

A cybersecurity investigator does not need to prove a person’s private emotional state before documenting downtime, missing files, unauthorized access, altered logs, or a security breach.

The same principle applies to public records investigations. Researchers can document which files existed, when they disappeared, which page numbers are missing, who authorized a release, which warnings were ignored, and whether corrective action occurred.

Intent may later become relevant in court, congressional testimony, or an inspector general investigation. It should not prevent the collection of evidence now.

The Epstein Files Provide a Real World Test

The Justice Department’s handling of the Epstein files presents precisely the type of institutional pattern Singh’s framework is designed to examine.

The Justice Department Epstein Library warns that portions of the collection may not be electronically searchable and that search results may be unreliable. Individual data set pages also acknowledge that sensitive personal information may have been published inadvertently because of the volume of material.

Those warnings establish that the Department anticipated technical and privacy failures.

The Department announced that it had published nearly 3.5 million pages. However, a forensic page count audit found that the Bates numbered EFTA production ends at EFTA02858498.

The final document is EFTA02858497, and it contains two pages. That creates a maximum of 2,858,498 uniquely numbered EFTA pages.

The Justice Department has not published a complete accounting explaining how it calculated its larger total.

This numerical discrepancy does not prove sabotage. It does demonstrate why incompetence cannot be accepted as a complete answer without further documentation.

The Failures Are Not Limited to One Page Count

The controversy includes more than a disagreement over arithmetic.

The Justice Department acknowledged that tens of thousands of files were taken offline for further review. Some files were removed after their initial publication. Other documents moved between data sets, creating broken links and unstable citations.

The Department also warned that the collection might contain inadvertently disclosed survivor information and other sensitive material.

At the same time, lawmakers, journalists, survivors, and researchers reported redactions that appeared to conceal the identities of powerful people or obscure the context needed to understand particular records.

These two failures point in opposite directions. Information requiring protection was exposed, while information important to accountability was sometimes concealed.

That combination is precisely why the pattern requires a serious audit.

The Data Set 9 Warning Is Evidence of Foreseeability

The Justice Department Data Set 9 page states that reasonable efforts were made to review and redact victim information. It also warns that the website may contain nonpublic personally identifiable information or sensitive sexual material.

This warning matters because it shows that privacy risks were foreseeable.

When an agency knows that its publication process may expose survivors, investigators should examine the controls used before release. They should identify who approved the workflow, how quality assurance was performed, what error rate was accepted, and what happened when sensitive information was discovered.

A foreseeable failure followed by inadequate safeguards is more significant than an unpredictable technical accident.

The Justice Department Claimed Multiple Layers of Review

Deputy Attorney General Todd Blanche said the Epstein records passed through multiple layers of review and quality control.

That claim creates a testable question. If the review was extensive, why did sensitive records require removal after publication? If records were removed for additional review, were they counted among the pages described as publicly released? If the original process was inadequate, who authorized it?

The Department’s January 30, 2026 letter to Congress said that more than 6 million pages had been collected and that the number of nonduplicative responsive pages was significantly smaller.

The letter reported the release of more than 3 million additional pages and a cumulative production of nearly 3.5 million pages.

What remains missing is a complete reconciliation of the collected material, duplicates, nonresponsive records, legally withheld files, removed files, native media, and pages actually available to the public.

One Failure Can Be a Mistake

A misplaced file can be a clerical error.

A broken download can be a technical problem.

An incorrect redaction can be an isolated human mistake.

A page total can be based on a poorly defined internal calculation.

A delayed release can result from an overwhelming workload.

Each explanation is individually plausible. Singh’s argument becomes relevant when those explanations accumulate without producing transparency, correction, or accountability.

At that point, investigators must study the system rather than excuse each incident separately.

A Pattern Requires a Pattern Analysis

A responsible investigation should not leap from repeated mistakes to a conclusion of intentional sabotage. It should compare the mistakes and determine whether they produce a consistent result.

Researchers should ask whether missing or removed files disproportionately concern particular people, allegations, institutions, or periods.

They should compare redaction practices across similarly situated individuals. If one person’s identifying information remains visible while another person’s information is concealed, the difference should be documented and explained.

Investigators should also record when files were published, changed, moved, removed, restored, or replaced. Cryptographic hashes can establish whether a restored file is identical to the original.

The result is an evidence based chronology rather than a collection of suspicions.

Who Benefits From Disorder?

Singh’s framework directs attention toward outcomes and beneficiaries.

A chaotic disclosure can protect powerful people even when no investigator can yet prove that protection was the stated purpose. An unstable archive makes citations harder to preserve. Inconsistent redactions make relationships harder to trace. Massive unorganized releases can bury important evidence beneath millions of irrelevant or duplicate pages.

At the same time, careless publication can harm survivors by exposing names, contact details, medical information, or descriptions of abuse.

The powerful gain ambiguity. Survivors inherit the risk.

That result deserves investigation whether it arose through incompetence, political interference, deliberate obstruction, or some combination of all three.

The Difference Between Evidence and Inference

The available evidence establishes that files were removed, links changed, sensitive information was exposed, records were redacted, and the government’s public page count has been challenged.

It does not automatically establish that every error was ordered for a corrupt purpose.

A proper EpsteinWiki Sleuth Report must preserve that distinction.

The documented incidents are evidence. The claim that those incidents were coordinated to protect particular people remains an inference unless supported by communications, testimony, access logs, directives, or a consistent selective pattern.

Singh’s Law does not eliminate the need to prove intent. It prevents the absence of proven intent from becoming an excuse to stop investigating observable conduct.

Evidence Investigators Should Preserve

Researchers should preserve the original Justice Department file URL, the date and time of access, the Bates number, the data set number, the file size, and a cryptographic hash.

If a file disappears, the researcher should retain the original copy and capture the government page showing that it is unavailable.

If a replacement appears, both versions should be compared. Changes to redactions, pagination, metadata, and embedded text should be recorded.

Researchers should also preserve public statements by Justice Department officials. Those statements establish what officials claimed about quality control, completeness, victim protection, and compliance.

The Epstein Data full text corpus provides a searchable archive for comparing documents and Bates numbers. The Epstein Data page archive allows researchers to examine individual extracted pages.

Questions Congress and the Inspector General Should Ask

Congress should ask who designed and approved the Epstein files review process.

Officials should identify the quality control systems used to prevent exposure of survivor information. They should explain why records were removed after publication and disclose whether those records were counted as released.

The Department should provide a complete accounting of collected pages, duplicate pages, nonresponsive pages, withheld pages, removed pages, native files, and publicly accessible pages.

Investigators should also request access logs showing who changed or removed files. They should determine whether particular names, subjects, or allegations received different treatment.

The Justice Department Inspector General audit is expected to examine how the Department identified, collected, redacted, released, and addressed concerns involving the Epstein records.

That review should evaluate the structure of the failures, not merely whether individual employees made mistakes.

Applying Singh’s Law Without Overstating the Evidence

Singh’s Law should function as an investigative threshold, not a verdict.

The threshold is crossed when institutional failures become repeated, foreseeable, measurable, and resistant to correction.

The Epstein files disclosure appears to satisfy those conditions. The public record includes unstable files, privacy failures, inconsistent redactions, disputed totals, delayed compliance, and incomplete explanations.

That does not prove a coordinated sabotage operation. It proves that the phrase “they were simply incompetent” cannot close the inquiry.

The next step is evidence collection.

Why This Framework Matters to EpsteinWiki

EpsteinWiki exists to preserve evidence, identify relationships, document institutional decisions, and distinguish verified records from allegations.

Singh’s essay provides a valuable rule for that work. Researchers should not waste years trying to determine whether an official privately felt malicious before documenting the official’s conduct.

We can count missing pages. We can compare file versions. We can identify decision makers. We can preserve removed records. We can examine whether errors consistently protect power while exposing survivors.

Intent can be investigated later. The wreckage should be documented now.

Readers can explore additional records through the EpsteinWiki Knowledge Base and search primary materials through Epstein Data.

Sources

• Jackie Singh, The Incompetence Defense
• United States Office of Strategic Services Simple Sabotage Field Manual
• Justice Department Epstein Library
• Justice Department Data Set 9
• Justice Department announcement of 3.5 million responsive pages
• Justice Department January 30, 2026 letter to Congress
• Justice Department Inspector General audit of Epstein files compliance
• Epstein Data forensic page count audit
• Epstein Data final EFTA document
• Epstein Data full text corpus
• Civil Rights Litigation Clearinghouse, Phang v. Blanche