A significant development has emerged in Nevada’s Business Court involving Energy Enhancement System LLC (“EES”). During recent proceedings, EES admitted that it does not currently possess the original human-readable source code underlying the technology that forms the foundation of its lawsuit against Jason Shurka and software developer Robert Religa.
This admission has altered the legal posture of the case in a substantial way. At issue is not branding language, public relations, or business positioning. It is ownership. And ownership, as the court made clear, must be proven.
The Court’s Central Focus: Proof of Creation and Ownership
During hearings earlier this month, Judge Timothy Williams emphasized that the dispute turns on a fundamental requirement in intellectual property law: the ability to establish authorship and ownership of the asset in question. As the judge stated from the bench, the issue “goes to the very essence of the claims for relief.” He further stressed that a party asserting intellectual property rights must demonstrate “ownership… creation… something.” He continued by stating, “if you don’t have the source code, that’s a problem”.
EES’s lawsuit asserts intellectual property rights in its technology and alleges misappropriation and defamation tied directly to that claimed ownership. Yet without the original source code, the evidentiary foundation for those claims becomes significantly more complex.
The source code is not merely technical documentation. It is the human-readable programming that would reveal what the software actually is, who created it, when it was created, how it evolved, and whether it is meaningfully distinct from other systems, including the Synchronicity Engine developed by Robert Religa in the 1990s and early 2000s. Without access to that underlying code, those questions cannot be resolved through direct comparison. This is where EES’s case fails.
Admission That the Code Is No Longer in Possession
In sworn declarations and court filings referenced during proceedings, EES stated that the original source code is no longer in its possession. Descriptions provided in the record have included that the code was lost, stolen, or otherwise unavailable.
This is not a procedural technicality. In intellectual property litigation, the asset itself typically serves as the central piece of evidence. When a company brings claims asserting ownership of proprietary software, the original source code is ordinarily the primary proof of authorship and originality.
The court underscored this point during the hearing, pressing that if ownership is claimed, production of the source code is expected. The absence of that code raises immediate questions about how ownership will be demonstrated.
Conflicting Accounts Raise Evidentiary Questions
An additional layer of complexity involves the timeline surrounding the disappearance of the source code. According to a declaration cited in court, the code was reportedly lost or stolen during a 2016 home invasion involving Sandra Rose Michael’s brother, the only other person who claimed to have possession of the code.
However, correspondence from EES’s attorney in 2017 referenced Dr. Michael possessing an “extensive archive of documentation and copyrights dating back to 1999.” The apparent tension between those statements has been raised by defense counsel as part of their argument that the evidentiary narrative is inconsistent.
Whether those accounts can be reconciled remains for the court to determine. But the existence of differing explanations for the status of the code has added scrutiny to the issue.
The Scope of the Claims
EES’s complaint includes claims of intellectual property ownership, allegations of technological misappropriation, defamation claims tied to public statements about that ownership, and requests for injunctive relief.
Each of these claims relies, at least in part, on establishing that EES owns the technology it asserts was misrepresented or misused. Without the source code, it becomes more difficult to demonstrate original authorship, technical distinctiveness, and the specific content that was allegedly defamed.
These are not peripheral issues. They are central to whether the lawsuit can meet its evidentiary burden.
A Case at a Critical Juncture
During the most recent hearing, EES offered technical explanations regarding executable files, Java-based structures, and file-driven systems. Yet the court’s central concern remained focused on proof of ownership. Judge Williams acknowledged that if the source code cannot be produced, that circumstance “potentially… has an impact on all of plaintiffs’ claims for relief.”
That observation underscores the significance of the development. The inability to produce the core asset underlying the claims does not automatically resolve the case. But it reshapes it.
Why This Matters Beyond the Courtroom
EES has marketed its technology as proprietary and grounded in original invention. In court, however, the focus shifts from branding to documentation and proof.
The absence of the original source code does not constitute a verdict. It does, however, shift attention squarely onto how ownership will be established without it.
For observers, customers, industry participants, and licensees, the proceedings highlight the distinction between marketing narratives and evidentiary requirements. Courts require proof. In intellectual property cases, that proof often begins with the underlying code.
What is now clear from the record is that the original source code is not currently available for examination. How that reality affects the outcome of the case will be determined in the months ahead.
In intellectual property litigation, the absence of the claimed asset is never a minor detail. It is a foundational one.
