# Legal Analysis and Strategic Memorandum: LexCore v. Adrian & Evidentia **To:** LexCore Executive Leadership **From:** Litigation Team **Re:** Emergency Action Against Former Product Director Adrian and Competitor Evidentia ## Executive Summary & Recommendation LexCore faces a high-stakes situation involving potential trade secret theft, breach of confidentiality, and improper customer solicitation. While the facts suggest substantial wrongdoing by Adrian, LexCore’s proposed emergency relief requests contain significant legal vulnerabilities that could undermine our position or expose us to liability. **Recommendation:** Do not file for the full scope of remedies requested initially (specifically the non-competes and broad product bans). Instead, seek a narrow Temporary Restraining Order (TRO) focused on: (1) prohibiting the use/disclosure of specific identified trade secret files; (2) enjoining solicitation of customers with whom Adrian had material contact; and (3) securing immediate forensic preservation of Adrian’s personal devices. Pursuing a broad non-compete ban is legally doomed under local law and risks damaging our credibility for a TRO hearing. --- ## 1. Trade Secret Qualification Under Rule 1, information must derive economic value from secrecy and not be readily ascertainable. The 80GB of copied data presents a mixed bag: * **Likely Trade Secrets:** * **Internal Model-Evaluation Datasets:** Access limited to 32 employees. Highly specific, economically valuable, and restricted. Strongest claim. * **Pricing Models & Renewal Forecasts:** Limited to ~70 employees. Contains forward-looking economic data not publicly known. * **Public Docs + Internal Annotations:** While the documents are public, the "LexCore annotations" likely constitute unique analysis derived from the software. If these annotations reveal proprietary logic or strategy, they qualify as trade secrets. * **Weak or Non-Trade Secrets:** * **Product Roadmaps:** Accessible to 400 employees (~10% of workforce). This weakens the "generally known" defense. While valuable, an argument can be made this is general knowledge within the company. * **Public Statutes/Court Rules:** Do not qualify. * **Customer Contact Spreadsheet:** Qualifies only if it includes non-public data (e.g., purchase history, decision-makers) beyond simple public contact info. ## 2. Reasonableness of LexCore’s Protections Rule 2 and Rule 3 require reasonable measures to preserve secrecy. Our position is mixed: * **Strengths:** Confidentiality agreements, annual security training, password-protected systems, and specific prohibitions against external storage. * **Weaknesses:** Inconsistent labeling of documents; some internal links had no expiration; access for former employees was sometimes disabled days after departure. * **Analysis:** Courts evaluate measures "in context." Our NDA and training likely satisfy the baseline requirement despite technical imperfections (e.g., expired links). However, the delay in revoking Adrian’s credentials creates a vulnerability. We must argue that the *policy* of revocation existed, even if the technical execution lagged slightly due to administrative processes, though the 5:08 p.m. breach is harder to defend as "reasonable." ## 3. Misappropriation and Breach Claims ### A. The Initial Copying (2 Days Prior) Adrian copied data while technically authorized. Under Rule 4, misuse of information obtained through valid access is not "unauthorized access" under the computer-access statute. However, it is a **breach of contract/confidentiality duty**. Since he knowingly violated the policy prohibiting unapproved external storage to take proprietary data to a competitor, this constitutes civil misappropriation under Rule 3 (use/disclosure knowing duty to maintain secrecy). ### B. The 5:08 p.m. Downloads This is critical evidence of misconduct. Rule 4 states access *after* credentials are revoked is unauthorized. Even if Adrian claims "cached credentials" or "automation," the server-side revocation occurred at 5:00 p.m. Accessing proprietary files (specifically regarding the next release) minutes after termination constitutes **unauthorized computer access** and reinforces the intent to steal data despite termination of employment relationship. ### C. Threatened Misappropriation Rule 5 states inevitable disclosure is insufficient; we need concrete evidence of likely use. * **Evidence:** Evidentia announced a feature similar to our roadmap 6 weeks after Adrian joined. While they claim independent development, "technical choices in its final product resemble experiments reflected in LexCore’s evaluation data." * **Conclusion:** The similarity in specific technical choices (which are trade secrets), combined with the timing of the clean-room adoption (after he started), provides concrete evidence of likely use. We can argue threatened misappropriation based on this overlap, not just his knowledge. ## 4. Customer Solicitation Claims * **Enforceability:** The 12-month non-solicitation is enforceable under Rule 6, provided it is limited to customers with "material contact." * **Conduct:** Adrian told a customer: *"You should see what Evidentia is launching. It solves the workflow problem LexCore kept postponing."* Under Rule 7, this crosses from passive response to active inducement/solicitation by disparaging our product roadmap ("kept postponing") to induce business movement. * **Scope:** We cannot ban contact with *all* customers (overbroad). Relief must be tailored to the specific customers Adrian had material contact with or where he actively solicited. ## 5. Evidentia’s Defenses & Development Records Evidentia will argue independent development and clean-room protocols. * **Independent Development:** Their records showing work began nine months prior (before Adrian joined) are a significant hurdle. It proves the *general concept* was not stolen. However, it does not protect specific technical choices resembling our evaluation datasets. * **Clean Room:** The protocol was adopted two weeks *after* Adrian started as Product Lead. This suggests the clean room was a remedial measure implemented after suspicion arose, rather than a preventative one. It provides weak protection for Evidentia against claims that Adrian seeded his work with stolen data immediately upon arrival. ## 6. Consequences of Wiping the Drive Adrian destroyed evidence after receiving a C&D letter. * **Rule 11:** Destruction after a duty to preserve arises supports sanctions. Secure-erasure software implies intent, countering an "accidental loss" defense. * **Strategic Impact:** While we must prove intent to deprive (Rule 11) for an adverse inference instruction at trial, the *act* itself damages Adrian’s credibility immediately. It suggests consciousness of guilt regarding the trade secrets on that drive. ## 7. Irreparable Harm and TRO Requirements Under Rule 9, a TRO requires likely success, irreparable harm, balance of hardships, and public interest. * **Likely Success:** Moderate. We have strong breach claims (copying/wiping), but the Non-Compete request is void (Rule 8). The trade secret overlap is strong enough for limited relief. * **Irreparable Harm:** The loss of trade secret value (head start, technical advantage) and customer relationships caused by active disparagement is generally considered irreparable because it cannot be fully calculated in damages. * **Public Interest:** Favorable to us; protecting proprietary innovation encourages investment. However, public interest disfavors stifling competition via void non-competes. ## 8. Analysis of Requested Restraints (Overbreadth) * **Preventing Adrian from working on competing products:** **Void.** Rule 8 explicitly states non-competition restrictions unrelated to a sale of business are void. Seeking this will immediately lower our "likely success" score with the judge and brand us as overreaching. * **Bar release of Evidentia’s feature:** Likely Overbroad/Unsuccessful. Since Evidentia has prior records (9 months), they may have a valid claim to the general feature. Banning release entirely hurts public interest and innovation. We should seek an injunction against *using our specific secrets* in that feature, not banning the feature itself unless we can prove it is inseparable from stolen data. * **Imaging Evidentia’s systems:** **High Risk.** Rule 10 mandates proportionality. Imaging a competitor's servers risks exposing *their* trade secrets to LexCore counsel, which creates liability and delays proceedings. This should be a "last resort" or limited to specific drives associated with Adrian only. * **Prohibiting contact with all customers:** **Overbroad.** Rule 6 limits this to customers with material contact. ## 9. Strategic Risks of Unsuccessful Application 1. **Reputational Damage:** An aggressive, overreaching TRO application that fails (especially on the non-compete) may portray LexCore as bullying a smaller competitor or trying to suppress competition rather than protect secrets. 2. **Discovery Exposure:** If we push hard for Evidentia’s system imaging and lose, or if the court narrows it significantly, Evidentia may be less inclined to settle, emboldening their defense. 3. **Cost vs. Recovery:** Emergency litigation is expensive. If the court denies the TRO, we still incur costs while Adrian works freely for a few weeks pending further hearing. ## 10. Recommended Scope of Relief and Settlement Strategy **Temporary Relief (TRO):** 1. **Preservation Order:** Immediate preservation of all data on Adrian’s personal devices (laptop, phone, cloud) under seal to prevent destruction. 2. **Injunction Against Use/Disclosure:** Bar Adrian from using or disclosing the *specific* directories copied (roadmap, eval datasets, pricing). 3. **Customer Restriction:** Bar Adrian and Evidentia from actively soliciting customers for whom Adrian had material contact (approx. list of top X clients), but allow them to respond passively if contacted by customer. 4. **Forensic Exam:** Do not seek immediate imaging of Evidentia’s corporate network. Instead, request an order compelling Adrian to hand over his devices for forensic inspection by a neutral third party under court supervision. **Expedited Discovery:** Focus on the timeline of the "clean room" adoption and specific technical choices in Evidentia's new feature vs. LexCore's eval data. Seek production of logs showing access to files at 5:08 p.m. **Settlement:** Given Adrian wiped the drive (damaging his defense) and made disparaging comments, he is vulnerable. Evidentia may wish to avoid "taint" allegations that could delay their product launch regardless of legal merit. * **Leverage:** The risk of a public trial regarding their 5:08 p.m. access and Adrian’s data wiping. * **Goal:** Secure immediate cessation of the specific feature release (via negotiation) or buyout of Adrian's contract, rather than broad non-compete litigation. ## 11. Immediate Action Plan **Should we seek a TRO immediately?** **Yes, but narrow.** A delay allows further data migration or product launch. However, **do not include the void non-compete provisions.** **Drafting Strategy:** File for a TRO focusing exclusively on **Trade Secret Misappropriation** and **Covenant Breach**. * Request immediate seizure of Adrian's personal devices (under Rule 10 proportionality, his devices are less invasive than corporate servers). * Explicitly concede we seek no non-competition restraint to align with Rule 8 and demonstrate good faith. * Argue that the 5:08 p.m. access proves ongoing unauthorized conduct, justifying emergency intervention. **Conclusion:** LexCore has a winning case on confidentiality breach and specific solicitation misconduct, provided we narrow our scope. Pursuing a blanket ban on Adrian's employment or Evidentia's product is legally fatal and strategically dangerous. Focus on the "5:08 p.m." unauthorized access and the drive wiping to prove bad faith, securing a court order that prevents further specific theft while allowing us to negotiate from a position of procedural strength.