# Memorandum: Emergency Relief Assessment — LexCore v. Adrian & Evidentia **To:** LexCore General Counsel / Board **Re:** Viability and scope of emergency action against former product director and Evidentia **Bottom line:** LexCore has a genuine, provable core case on a narrow set of assets and a serious spoliation problem for Adrian. It does not have the case it wants. The relief LexCore has asked for — barring Adrian from competing work, enjoining a product launch, imaging a competitor's systems, and blanket customer contact bans — is substantially overbroad and, if sought as filed, is likely to produce a partial or total denial that will damage LexCore's position for the remainder of the case. The recommended course is a narrow, tightly documented TRO application (or an agreed standstill order) focused on the fourteen post-revocation files, the customer-contact spreadsheet, the evaluation datasets, and forensic preservation, paired with aggressive expedited discovery. --- ## 1. Which categories likely qualify as trade secrets The nine copied directories do not stand or fall together. Pleading them as a single 80-gigabyte block is the single most dangerous framing choice available, because it invites the court to reason from the weakest category to the whole claim. **Almost certainly not protectable:** - **Public statutes and court rules.** Generally known and readily ascertainable. Zero value from secrecy. - **Publicly available court documents** as such. The underlying documents are public. **Protectable only in part:** - **LexCore's internal annotations on public court documents.** The annotation layer — how LexCore tags, classifies, weights, or characterizes public filings — can be a trade secret if it reflects non-obvious analytical judgment and is not reconstructible from the public source. LexCore must be prepared to describe the annotation schema with specificity and explain why an outsider could not readily replicate it. If the annotations are essentially docket summaries, this category collapses. - **Product roadmaps.** Roadmaps have real competitive value, and a rival's knowledge of what LexCore will ship and when is economically significant. But 400-employee access is a serious problem for this category specifically (see §2). Roadmaps are also perishable and frequently discussed with customers, analysts, and prospects. Expect Evidentia to argue that the relevant roadmap item was publicly signaled. **Strongest categories:** - **Internal model-evaluation datasets and feature-ranking experiments.** This is LexCore's best asset. Negative know-how — which approaches were tested and failed, and which configurations outperformed others — is classic trade secret material. It is not ascertainable by inspecting LexCore's product, it represents substantial sunk R&D cost, and access was restricted to 32 employees. Critically, this is also the category with independent corroboration: the resemblance between Evidentia's technical choices and LexCore's experiments. - **Pricing models.** Not published prices, but the underlying model — discount architecture, floors, margin assumptions, deal-structuring logic. High value, not ascertainable from quotes in the market. - **Customer usage statistics, renewal forecasts, and the customer-contact spreadsheet.** Compiled customer intelligence — who is at churn risk, what they actually use, what they will pay, who the decision-makers are — has direct competitive value even where customer identities are known in a small market. 70-employee restriction supports this. The contact spreadsheet's value depends on whether it contains more than names available on LinkedIn; the renewal forecasts almost certainly qualify. **Practical implication:** Plead three to five specific, described assets with particularity. Abandon the public-material categories affirmatively and early. Voluntarily conceding the statutes and court rules costs nothing and materially improves credibility on the categories that matter. --- ## 2. Were LexCore's protections reasonable? Perfect security is not required, and the governing standard is contextual. LexCore's baseline is defensible: confidentiality agreements, annual security training, password-protected systems, an express prohibition on unapproved external storage, and tiered access. That is ordinary, real-world corporate hygiene, and it was in place before the dispute — which distinguishes it from the disfavored practice of labeling information confidential only after litigation begins. **The weaknesses, honestly assessed:** | Weakness | Effect | |---|---| | 400 employees could access the roadmap | Most damaging fact. Undermines the roadmap category specifically. Mitigable only if all 400 were under NDA and the roadmap was access-logged. | | Non-expiring internal links | Suggests information could leak beyond intended tiers without detection. | | Inconsistent document labeling | Weakens knowledge/notice arguments; makes it harder to show Adrian knew a given file was secret. | | Delayed offboarding of former employees | Systemic laxity; also directly relevant to Adrian's "I didn't know access was revoked" defense. | **Assessment:** Reasonableness is likely to be found **category-by-category, not globally.** The 32-employee evaluation datasets and the 70-employee usage/renewal data are supported by genuine tiering — the restriction is evidence that LexCore actually treated these as secret rather than merely saying so. The roadmap is vulnerable. LexCore should lean into the tiering argument and not overclaim uniform security, because a court that catches LexCore overstating its security posture will discount everything else it says. Note the two-edged nature of the offboarding laxity: it supports Adrian's innocent explanation for the 5:08 p.m. downloads, but it is also LexCore's own fault, and LexCore cannot simultaneously argue that its security was tight and that Adrian should have expected his credentials to be cut off precisely at 5:00. --- ## 3. The claims ### Misappropriation by acquisition The initial copying is legally ambiguous. Adrian was authorized to access every file he took; he copied to an unapproved device, violating policy. Policy violation is not automatically "improper means." Adrian's explanation — unreliable remote connection, permitted remote work, routine practice — is plausible if he can show a **pattern** of prior copying. If forensics show this was a one-off transfer two days before resignation, at unusual volume, including directories outside his working scope, the "routine practice" defense fails and the timing becomes powerful circumstantial evidence of intent. **Priority discovery:** Adrian's historical USB/external-device connection logs. This single data point may decide the acquisition theory. ### Misappropriation by use or disclosure Currently **inferential but not empty.** The strongest thread is the resemblance between Evidentia's technical choices and LexCore's evaluation experiments — this is the kind of specific, non-obvious overlap that is hard to explain by coincidence, particularly where negative know-how is involved. The statement to the customer ("you should see what Evidentia is launching; it solves the workflow problem LexCore kept postponing") is itself arguably a disclosure of roadmap-adjacent confidential information, not merely a solicitation. That sentence does real work for LexCore in two claims at once. But six weeks from arrival to announcement, against nine months of documented prior development, is a difficult use case on the feature as a whole. ### Threatened misappropriation The governing law forecloses reliance on inevitable disclosure alone, and this is where LexCore's requested relief is most exposed. LexCore cannot obtain an order barring Adrian from competing work on the theory that he cannot help but use what he knows. However, LexCore is **not** limited to inevitability. It has concrete evidence: unauthorized bulk copying, post-revocation downloads, deliberate destruction of the copied medium after a preservation duty attached, immediate assumption of a directly competing product-lead role, and an affirmative disclosure-flavored statement to a customer. That combination is materially stronger than a bare inevitable-disclosure claim and is the correct frame for narrow injunctive relief. ### Breach of confidentiality agreement **LexCore's most reliable claim.** It does not require trade secret status, does not require proof of use, and is not defeated by the "authorized access" point. Copying to a prohibited external device breaches the confidentiality agreement and internal policy on its face. The remedy is narrower — contractual, damages-focused — but liability is comparatively clean. This claim should anchor the complaint rather than sit beneath the trade secret claim. ### Customer non-solicitation Enforceable for twelve months, limited to **material-contact** customers and only as reasonably necessary. Three customers contacted Adrian first. Customer-initiated contact does not immunize him; the question is whether he actively encouraged or induced the move. - **Customer 1** (the "you should see what Evidentia is launching" customer, which then moved business): This is active encouragement. He disparaged LexCore's execution, pitched a competing product, and business followed. Likely breach if material contact is established. - **Customers 2 and 3:** Depends entirely on what he said. Confirming his new employment and declining to discuss business is not solicitation. LexCore needs the actual communications before characterizing these. LexCore must produce evidence of material contact — account ownership, meeting records, email volume — for each customer it names. It cannot assert the covenant across its whole customer base. ### Unauthorized access statute This claim splits cleanly, and LexCore should say so plainly rather than blur it: - **The original 80 GB copy: no violation.** Adrian had valid access. The statute does not reach misuse of information obtained through authorized access. Pleading otherwise invites a dismissal that costs credibility on everything else. - **The 5:08 p.m. downloads: unauthorized access, if attributable to Adrian.** Access after revocation is unauthorized. The defense is automation plus lack of knowledge. This is a factual dispute LexCore can likely win with forensics — an automated sync process has a signature: it runs on a schedule, syncs whatever changed, and does not selectively retrieve fourteen files all concerning the next product release. That subject-matter concentration is the tell. Whether the statute requires knowledge of revocation is the live legal question; the delayed-offboarding culture supports Adrian's ignorance claim. --- ## 4. Significance of the two access events These two events should be argued **separately and for different purposes.** **The initial copying** carries the litigation's factual weight but the least legal clarity. Its significance is contractual and circumstantial: it establishes breach, establishes the volume and content of what left, and — through its timing two days before resignation — supplies intent evidence that colors everything after. **The 5:08 p.m. downloads** are legally the cleanest wrong and rhetorically the most valuable. Eight minutes after scheduled revocation, via a cached credential, fourteen files all concerning the next product release. The narrowness and topical coherence of the selection is what makes it damning; a sync process does not curate. Any TRO application should lead with this event, because it is discrete, documented, and requires no trade secret finding to be alarming to a court. Together they answer the "so what has actually happened here?" question that judges ask at TRO hearings. --- ## 5. Evidentia's prior development work and its clean-room protocol **The nine months of prior development is genuinely good evidence for Evidentia** and should not be dismissed. Contemporaneous development records predating Adrian's arrival are strong independent-development proof on the **general feature**. It substantially defeats any claim that Evidentia's roadmap was stolen wholesale, and it undercuts the temporal inference LexCore would otherwise draw from the six-week timeline. **But it does not answer the specific question.** Independent development of a general feature does not establish independent derivation of the **particular technical choices** that resemble LexCore's evaluation experiments. The relevant inquiry is whether those specific choices appear in Evidentia's records *before* Adrian arrived, or only after. That is a discrete, answerable question and should be the primary target of expedited discovery: version control history, commit logs, design documents, and experiment logs with reliable timestamps, compared across the pre- and post-arrival boundary. LexCore should also probe whether prior work accelerated or changed direction after Adrian joined. **The clean-room protocol is a mixed fact that cuts against Evidentia more than it helps.** Adopted two weeks after Adrian started, while he served as product lead from day one, it leaves a two-week window during which the most senior product decision-maker at a direct competitor operated with no containment at all — the precise period in which architectural direction is typically set. The protocol's existence also implies Evidentia recognized the risk, raising the question of what prompted adoption and why not on day one. That said, adopting a protocol at all is evidence of good faith and materially undercuts any claim that Evidentia acted with willful indifference. It supports Evidentia's argument against the extraordinary relief of system imaging. LexCore should demand the protocol's terms, adoption date, trigger, monitoring, and audit records, and should focus its use-claim on the unprotected two-week window rather than attacking the protocol generally. --- ## 6. Consequences of wiping the drive **This is LexCore's most valuable single fact and the reason a court will take the case seriously.** The preservation duty attached on receipt of the cease-and-desist letter. Adrian erased the drive afterward, using secure-erasure software — a deliberate act, not a stray deletion or reformat. His explanations are internally weak: personal tax and medical records could have been segregated or the drive preserved intact and sequestered under protective order, and the belief that "LexCore already had every file" does not explain destroying the evidence of *what he took and when*, which is precisely the disputed issue. **Consequences:** - Sanctions are available for destruction after a preservation duty arises. - An **adverse inference requires intent to deprive.** Secure-erasure software post-letter is about as strong an intent showing as is realistically available at this stage, though Adrian will argue his intent was privacy, not deprivation. - Practically, spoliation partially substitutes for the proof it destroyed. A court asked whether LexCore is likely to succeed will weigh the fact that the defendant destroyed the best evidence of the answer. **Do not overplay it.** Spoliation is not liability. It does not establish that the roadmap was a trade secret or that Evidentia used anything. Overclaiming here — arguing the wipe alone justifies imaging a competitor's entire infrastructure — is exactly the overreach that gets applications denied. Use it for two purposes: strengthening likelihood of success generally, and justifying forensic examination of **Adrian's** devices and cloud accounts. **Immediate step:** Determine whether copies survive elsewhere — cloud backup, replacement drives, Adrian's personal computer, email, personal cloud storage, or Evidentia-issued hardware. Preservation demands must go to Adrian, Evidentia, and any relevant third-party providers today. --- ## 7. Irreparable harm **Partially provable, and weaker than LexCore assumes.** Supporting irreparable harm: the copied medium was destroyed, so LexCore cannot know what remains outstanding; the information is of a type whose value is destroyed once disclosed, and cannot be restored by damages; customer relationships and renewal positioning are difficult to quantify; and the volume of material remaining in unknown locations is itself a continuing risk. Undercutting it: one customer moving *part* of its business is a quantifiable, compensable loss. The roadmap is perishable and partly stale. Six weeks have passed since the Evidentia announcement, and any delay by LexCore in moving will be read as inconsistent with emergency. Evidentia's documented prior development weakens the claim that its launch harms LexCore through misappropriation at all. **Framing:** LexCore's honest harm case is about **unknown residual copies and untraceable future use**, not about the announced feature. Anchoring irreparable harm to the feature launch is a mistake — that is the element where Evidentia's evidence is strongest. --- ## 8. Which requested restraints are overbroad | Requested relief | Assessment | |---|---| | **Bar Adrian from working on competing products** | **Clearly overbroad; do not request.** Adrian signed no noncompete, and noncompetes unrelated to a business sale are void here. This is a de facto noncompete achieved through injunction, resting on inevitable disclosure, which is insufficient. Requesting it signals to the court that LexCore is seeking competitive advantage rather than protection of secrets — and taints the requests that are defensible. | | **Bar release of Evidentia's feature** | **Overbroad on this record.** Enjoining a competitor's product launch is among the most drastic remedies available. Nine months of documented prior development defeats likely success on the feature as a whole. Balance of hardships strongly favors Evidentia. | | **Image Evidentia's systems** | **Overbroad as framed.** Emergency forensic relief must be proportionate and must avoid needlessly exposing the new employer's own confidential information. Wholesale imaging of a competitor's infrastructure hands LexCore access to Evidentia's trade secrets — a self-defeating optic. A targeted, neutral-expert protocol is obtainable; full imaging is not. | | **Bar contact with all LexCore customers** | **Overbroad.** The covenant reaches only material-contact customers and only as reasonably necessary. A blanket ban across the customer base is unenforceable and will likely be rejected outright. | Requesting all four together creates a real risk the court denies the application wholesale rather than editing it down. Judges are more inclined to narrow a request that is nearly right than to rescue one that is fundamentally overreaching. --- ## 9. Strongest defenses **Adrian:** 1. No noncompete; noncompetes are void here. Any work restriction is unenforceable indirectly. 2. Authorized access defeats the computer-access claim on the 80 GB copy. 3. Routine remote-work copying with an unreliable VPN — plausible, and stronger if a historical pattern exists. 4. The 5:08 downloads were automated sync, and LexCore's own inconsistent offboarding made revocation timing unknowable. 5. Customers initiated contact; he did not induce them. 6. The wipe was privacy-motivated, not deprivation-motivated — attacking the intent element for an adverse inference. 7. Much of the material is public or widely accessible; the roadmap's 400-person circulation is not secrecy. 8. Delay: LexCore waited while the announcement occurred. **Evidentia:** 1. Documented independent development predating Adrian by nine months. 2. Clean-room protocol demonstrating good faith and no willful conduct. 3. Representation that Adrian has no access to LexCore-derived files. 4. Disproportionality of imaging and exposure of Evidentia's own confidential information. 5. No evidence Evidentia knew of or induced any improper acquisition. 6. Severe hardship from a launch injunction. --- ## 10. Strategic risk of an unsuccessful application The downside is real and asymmetric. - **Adverse findings become sticky.** A ruling that the roadmap was not adequately protected, or that LexCore's security was lax, will follow LexCore through summary judgment, into any future case against any departing employee, and into every negotiation. - **Settlement leverage collapses.** A denial converts LexCore from credible threat to a plaintiff whose best shot missed. - **Own-house discovery exposure.** Litigating reasonable measures opens LexCore's security practices, access logs, labeling failures, and offboarding history to scrutiny. The non-expiring links and delayed access revocation will be examined in detail. - **Precedent against LexCore's own program.** A finding of inadequate measures undermines LexCore's confidentiality regime company-wide. - **Fees and possible bond/wrongful-injunction exposure** if relief is granted then dissolved. - **Distraction and reputational cost.** An aggressive overreach against a competitor and a departed employee that fails publicly invites the narrative that LexCore litigates rather than ships — a narrative Adrian's own quoted remark already gestures at. - **Customer disruption.** Naming customers in a public filing may itself damage the relationships LexCore is trying to protect. The asymmetry matters: a narrow win preserves nearly all of LexCore's options, while a broad loss forecloses many of them. --- ## 11. Recommended course ### Recommendation: do not file the requested TRO. Pursue a narrow application or, preferably, a negotiated standstill. The right move is to seek immediate **preservation and status quo relief** and defer merits-based restraints until expedited discovery reveals what actually happened. A negotiated standstill order — which Evidentia has strong incentives to accept, given its clean-room posture and its interest in avoiding an imaging order — would achieve nearly everything a realistic TRO would, without the risk of adverse findings. **Today, regardless of filing decision:** - Broad preservation letters to Adrian, Evidentia, and third-party cloud/backup providers. - Internal forensic work: full access logs for the 80 GB transfer and the 5:08 downloads; Adrian's historical external-device connection history; scope and content of the fourteen files; documentation of the tiering for the 32- and 70-employee categories. - Identify with evidence the specific customers with whom Adrian had material contact. - Obtain and preserve the three customer communications. **Most defensible temporary relief (narrow TRO or agreed order):** 1. **Return and sequestration** of all LexCore-derived material in any location, and identification under oath of every device, account, and cloud service to which it was ever copied. 2. **Use and disclosure prohibition** on identified LexCore confidential information — narrowly defined by category, not "all information." 3. **Preservation order** covering Adrian's devices and accounts and the relevant Evidentia development records, with a specific bar on deletion or wiping tools. 4. **Targeted non-solicitation enforcement** limited to the named material-contact customers, for the covenant's remaining term. Consider limiting Adrian to responding to unsolicited contact without discussing LexCore's products, plans, or pricing. 5. **No** work restriction, **no** launch injunction, **no** blanket customer ban, **no** wholesale imaging. **Forensic examination — proportionate design:** - **Neutral court-appointed examiner**, not LexCore's expert. - **Adrian's devices and accounts:** broad access justified by the spoliation. - **Evidentia's systems:** narrowly targeted — search for LexCore file artifacts by hash, filename, and metadata; version-control and design-document history for the specific feature across the pre/post-arrival boundary. Results to the examiner and to counsel under an attorneys'-eyes-only protective order; no LexCore business personnel access. - This design directly answers the proportionality requirement and makes the request far harder to resist. **Expedited discovery priorities:** 1. Evidentia's development records with verifiable timestamps for the specific technical choices at issue. 2. Adrian's historical external-storage usage pattern. 3. Forensic analysis of the fourteen downloads and the sync-automation claim. 4. The clean-room protocol: terms, trigger, adoption date, monitoring, audit trail; and what Adrian did in the first two weeks. 5. All communications between Adrian and the three customers, and between Adrian and Evidentia pre-hire. 6. Recovery of any surviving copy of the wiped drive's contents. **Settlement posture.** This case is well suited to early resolution, and LexCore's leverage is highest now — before any adverse ruling. A realistic package: sworn certification and forensic verification of deletion of all LexCore material; neutral-examiner confirmation of the feature's independent derivation; extension and strict enforcement of the clean-room protocol with audit rights; Adrian's agreement to have no contact with the identified material-contact customers for the covenant's remaining term; a modest payment reflecting the customer's partial defection and LexCore's forensic costs; and mutual non-disparagement. LexCore should treat the spoliation as its principal negotiating asset — the leverage it creates is worth more in settlement than the adverse inference is likely to be worth at trial. ### Sequencing File a narrow application only if Evidentia refuses a standstill within a short, defined window — days, not weeks, to preserve the urgency narrative. Move quickly, because delay is Adrian's cheapest defense; but move narrowly, because breadth is the only thing that can turn a winnable case into a public loss.