## Memorandum to LexCore Litigation Team **Re: Adrian / Evidentia — trade secrets, customer solicitation, unauthorized access, spoliation, and emergency relief** ### 1. Bottom line LexCore has a credible case, but it is strongest on **narrow, fact-specific grounds**, not on the broad emergency package LexCore currently wants. The strongest claims are: 1. **Breach of confidentiality / trade-secret misuse** as to certain nonpublic materials copied to the external drive, especially the internal model-evaluation datasets, feature-ranking experiments, next-release product information, pricing models, and customer usage/renewal analytics. 2. **Customer non-solicitation breach** as to at least the customer to whom Adrian made the “you should see what Evidentia is launching” statement, assuming Adrian had material contact with that customer. 3. **Unauthorized access** for the 5:08 p.m. downloads after Adrian’s credentials were revoked, though the automated-sync defense limits the practical significance. 4. **Spoliation / adverse-inference leverage** because Adrian deliberately and securely wiped the external drive after receiving a cease-and-desist letter. The weakest parts of LexCore’s current position are: - The request to bar Adrian from working on competing products, which is effectively a **noncompetition restraint** and likely void. - The request to bar Evidentia’s entire feature, especially where Evidentia has production records showing a nine-month head start on the general feature. - Full imaging of Evidentia’s systems, which is likely overbroad and disproportionate. - A ban on all contact with all LexCore customers, which exceeds the enforceable scope of the customer non-solicitation agreement. **Recommendation:** LexCore should seek **immediate but narrowly tailored emergency relief**, not the broad four-part order described in the facts. The emergency request should focus on: - preservation and no destruction of evidence; - a targeted forensic protocol; - no further solicitation of a defined list of material-contact customers; - no use or disclosure of specifically identified LexCore trade secrets in connection with Evidentia’s relevant product work; - a limited clean-room or independent-development audit as to the specific feature/technical choices at issue. LexCore should avoid framing the case as a noncompete, an inevitable-disclosure case, or a case about 80GB of copied files generally. The case should be framed as: **Adrian took identifiable confidential business information, may have already influenced a competitive feature in a narrow way, is soliciting customers, and destroyed evidence after being put on notice.** --- ## 2. Which information likely qualifies as trade secrets Under the governing law, trade-secret status requires: 1. actual or potential economic value from not being generally known or readily ascertainable, and 2. reasonable measures to preserve secrecy. The copied 80GB should not be treated as a single trade secret. The categories must be separated. ### A. Strong trade-secret candidates #### 1. Internal model-evaluation datasets **Likely strong trade secret.** These datasets were limited to 32 employees, suggesting LexCore treated them as sensitive. If they contain nonpublic benchmarks, test data, evaluation methodologies, or results that would be costly to recreate, they likely qualify. This is especially important because the facts state that several technical choices in Evidentia’s final product resemble experiments reflected in LexCore’s evaluation data. That is the most concrete factual bridge between Adrian’s copied materials and Evidentia’s product. #### 2. Feature-ranking experiments **Likely strong trade secret.** Feature-ranking experiments are the kind of internal product-development know-how that often has real competitive value. If they show which features LexCore tested, how it ranked them, what trade-offs it considered, and what technical choices it rejected or favored, they are not readily ascertainable from public sources. Again, the resemblance between Evidentia’s technical choices and LexCore’s evaluation data makes this category central. #### 3. Next-product-release information **Likely strong, especially the 14 files downloaded after revocation.** Roadmaps as a whole may be weaker because approximately 400 employees could access them. But the 14 files concerning LexCore’s next product release, especially if downloaded after Adrian’s access was revoked, likely contain more specific, time-sensitive, and competitively valuable information: feature priorities, release timing, unresolved technical decisions, and product positioning. If those files are not generally known outside a limited group and were not readily ascertainable, they likely qualify. #### 4. Pricing models **Likely trade secret.** Pricing models usually have competitive value if they are not public and are based on internal data, customer segmentation, cost assumptions, discounting strategy, or revenue projections. The fact that Adrian copied them does not alone prove secrecy, but pricing models are often protectable if LexCore did not generally publish them. #### 5. Customer usage statistics and renewal forecasts **Likely trade secret, subject to particularity.** Usage statistics and renewal forecasts were limited to approximately 70 employees. If they contain nonpublic, customer-specific data—churn indicators, renewal risk, usage patterns, expansion opportunities—they likely have economic value from secrecy. These materials also relate directly to the customer-solicitation issue. If Adrian used this information to identify which customers were vulnerable or likely to switch, that supports both trade-secret and non-solicitation claims. #### 6. Customer-contact spreadsheet **Possibly a trade secret, but only if it is more than a simple public contact list.** A basic list of customer names, email addresses, and phone numbers may not qualify if that information is readily available. But if the spreadsheet includes compiled nonpublic information—account owners, recent interactions, renewal risk, usage metrics, notes, opportunities, or internal customer classifications—it may qualify as a protectable compilation. LexCore should identify the specific nonpublic fields in the spreadsheet rather than treating the entire file as secret. #### 7. Public court documents enhanced with LexCore’s internal annotations **The annotations may qualify; the public documents themselves do not.** Publicly available court documents are not trade secrets. But if LexCore’s annotations contain nonpublic analytical insights, proprietary tagging, search patterns, or internal product-development insights derived from the documents, the annotations may qualify if they are not readily ascertainable and have competitive value. This category is likely secondary. It should not be overemphasized. --- ### B. Weak or unlikely trade-secret candidates #### 1. Public statutes and court rules **Not trade secrets.** These are public legal materials. Their mere copying does not support a trade-secret claim. #### 2. Unenhanced public court documents **Not trade secrets.** Only LexCore’s nonpublic annotations, if any, may be protectable. #### 3. General product roadmap information known to 400 employees **Weak to moderate.** A product roadmap may still be a trade secret if it contains future, nonpublic features, timing, and strategy. But the fact that approximately 400 employees could access it weakens the secrecy argument, especially if that number represents a large portion of the workforce. LexCore should avoid relying heavily on broad roadmap access as a trade-secret theory. It is better to focus on the **next-release subset**, especially the 14 files downloaded after revocation, and on the more tightly restricted evaluation and customer data. --- ## 3. Whether LexCore’s protections were reasonable Reasonableness is evaluated in context. Perfect security is not required, but LexCore cannot rely solely on post-dispute characterizations of information as confidential. ### A. Positive factors LexCore has meaningful preexisting safeguards: - confidentiality agreements; - annual security training; - password-protected systems; - access restrictions for certain sensitive data; - a policy prohibiting unapproved external storage; - scheduled termination of Adrian’s access on his final day. The access restrictions are especially helpful for the strongest categories: - evaluation datasets: 32 employees; - customer usage and renewal data: approximately 70 employees. Those limited-access categories are the most defensible trade-secret claims. ### B. Negative factors LexCore has real vulnerabilities: - some internal links had no expiration date; - documents were inconsistently labeled; - former employees’ access was sometimes disabled several days after departure; - approximately 400 employees could access the product roadmap; - the 5:08 p.m. cached-credential download suggests that offboarding was not perfectly immediate or complete. These facts will be used by Adrian and Evidentia to argue that LexCore’s secrecy measures were inadequate, at least for the roadmap and possibly for other materials. ### C. Likely outcome For the **core technical and customer data**, LexCore’s protections were likely reasonable. The restricted access, confidentiality agreements, training, and external-storage prohibition are meaningful. For the **general product roadmap**, the position is weaker. The broad access, inconsistent labeling, and lack of expiration dates may undermine a claim that the general roadmap was sufficiently protected. **Strategic implication:** LexCore should anchor the trade-secret case in the evaluation datasets, feature-ranking experiments, next-release details, pricing models, and customer usage/renewal analytics. It should not overstate the secrecy of public materials or broadly accessible roadmap information. --- ## 4. Misappropriation, threatened misappropriation, breach of confidentiality, customer solicitation, and unauthorized access ### A. Misappropriation Misappropriation can occur through: 1. acquisition through improper means, or 2. use or disclosure without consent by a person who knew or should have known of a duty to maintain secrecy. #### 1. Initial 80GB copying The initial copying is not, by itself, an unauthorized-access violation under the computer-access statute because Adrian had valid access. The governing law says misuse of information obtained through valid access is not unauthorized access. But copying while technically authorized can still breach contract or confidentiality duties. Here, Adrian copied a large volume of files to an encrypted external drive, and the company prohibited use of unapproved external storage. That is significant. If the copied items include trade secrets, the copying may support misappropriation or at least breach of confidentiality. The strongest argument is that Adrian violated the external-storage policy and retained confidential materials after resignation. His work-from-home explanation is plausible only if there is evidence of a consistent pattern of similar transfers for legitimate remote work. The timing—two days before resignation—and the volume make that explanation weak. #### 2. Use or disclosure to Evidentia There is no direct fact showing that Adrian transmitted the drive to Evidentia or that Evidentia accessed LexCore-derived files. That is a gap. But there are facts that can support threatened misappropriation if properly narrowed: - Adrian became Evidentia’s product lead immediately; - Evidentia announced a similar feature within six weeks; - several technical choices resemble LexCore’s evaluation experiments; - the clean-room protocol was adopted only two weeks after Adrian started; - Adrian wiped the external drive after being put on notice. However, the governing law says inevitable disclosure alone is insufficient. LexCore cannot win merely by arguing that Adrian knows too much. It must show concrete evidence of likely use or disclosure of **specific** trade-secret information. The strongest concrete hook is the resemblance between Evidentia’s technical choices and LexCore’s evaluation data. If those choices are not in Evidentia’s preexisting development records and closely track LexCore’s confidential experiments, LexCore has a much stronger threatened-misappropriation claim. #### 3. Likelihood of success on misappropriation - **Strong** as to breach of confidentiality based on the unapproved copying and retention. - **Moderate to strong** as to misappropriation of specific evaluation/next-release materials, depending on particularity and evidence of use or likely use. - **Weak to moderate** as to the general roadmap, especially given the nine-month independent-development records. - **Weak** as to public materials. --- ### B. Breach of confidentiality This is likely one of LexCore’s stronger claims. Adrian signed a confidentiality agreement. He copied a large amount of information to an encrypted external drive in apparent violation of policy, retained it after resignation, and then wiped it after a cease-and-desist letter. Even if some of the copied information is not a trade secret, the copying and retention may still breach the confidentiality agreement if the information was confidential under the agreement. The breach claim is also less dependent on proving that every copied item is a trade secret. It depends more on: - whether the information was confidential; - whether Adrian breached the agreement by taking, retaining, or wiping it; - whether LexCore suffered harm or has a credible threat of harm. The wiping is especially relevant to breach because it occurs after Adrian was put on notice. --- ### C. Customer solicitation The twelve-month customer non-solicitation restriction is enforceable only as to customers with whom Adrian had material contact and only to the extent reasonably necessary to protect legitimate relationships. The facts state that three LexCore customers contacted Adrian after his move and that he responded to each. The customer-initiated nature of the contact does not automatically save Adrian. The question is whether he actively encouraged or induced the customer to move business. The quoted statement is important: > “You should see what Evidentia is launching. It solves the workflow problem LexCore kept postponing.” That is not a neutral response. It affirmatively promotes Evidentia, highlights a supposed LexCore weakness, and invites the customer to evaluate Evidentia’s new offering. It likely constitutes solicitation or inducement, especially where the customer later moved part of its business to Evidentia. For the other two customers, LexCore needs similar evidence. If Adrian merely answered factual questions, the claim may be weaker. If he made similar promotional statements, the claim may be strong. **Key limitation:** LexCore must identify customers with whom Adrian had material contact. As product director, Adrian likely had material contact with many customers, but this must be proved. A blanket ban on all LexCore customers is overbroad. --- ### D. Unauthorized-access claims #### 1. Initial authorized copying The initial copying of approximately 80GB was done while Adrian had valid access. Under the governing computer-access statute, misuse of information obtained through valid access is not unauthorized access. So the initial copying is likely **not** a standalone unauthorized-access claim, even if it may be a breach of confidentiality or trade-secret misuse. #### 2. 5:08 p.m. downloads The 5:08 p.m. downloads are different. Adrian’s access was scheduled to end at 5:00 p.m. A cached credential was used at 5:08 p.m. to download fourteen files concerning LexCore’s next product release. Under the governing law, access after credentials are revoked is unauthorized. That makes this a stronger unauthorized-access issue than the initial copying. Adrian’s defense—that an automated synchronization process caused the downloads and he did not know his credentials had been revoked—is a factual defense. But the line is clear: post-revocation access is unauthorized. The court may consider whether Adrian acted knowingly, whether the process was truly automatic, and whether LexCore’s offboarding was reasonably prompt. Practically, the 5:08 p.m. event is useful for two reasons: 1. it supports unauthorized access as to the 14 next-release files; and 2. it reinforces the inference that Adrian was still trying to retain or obtain LexCore product information at the moment of departure. It is not, by itself, enough to support a broad product injunction, but it is significant. --- ## 5. Significance of the initial authorized copying and the 5:08 p.m. downloads ### A. Initial authorized copying The initial copying is important because it shows: - Adrian removed a large volume of files before resignation; - he used an encrypted external drive, which company policy prohibited; - the copied directories included multiple categories that may be trade secrets; - he retained the drive after resignation until wiping it. This undermines the “routine work-from-home” explanation. Routine work-from-home copying usually does not involve moving 80GB to an encrypted personal drive two days before resignation. However, the initial copying does not establish unauthorized access under the computer-access statute. It establishes a possible breach of policy and confidentiality and, if the copied items are trade secrets, possible misappropriation through improper retention or use. ### B. 5:08 p.m. downloads The 5:08 p.m. downloads are more legally significant for unauthorized access because they occurred after Adrian’s access was scheduled to end. The fact that a cached credential was used raises the question whether the downloads were manual or automatic. If automatic, Adrian may have a defense to knowledge or intent. But the governing law still treats post-revocation access as unauthorized. The 5:08 p.m. event also matters because the files concerned LexCore’s next product release. That makes the episode more serious than a generic after-hours sync. **Overall significance:** The initial copy supports confidentiality breach and trade-secret retention. The 5:08 p.m. downloads support unauthorized access and urgency. Together, they support narrow emergency relief, but not a broad noncompete or product ban. --- ## 6. Evidentia’s preexisting development work and later clean-room protocol ### A. The nine-month development records are a major obstacle to a broad feature injunction Evidentia has produced development records showing that it began work on the general feature nine months before the announcement. Since Adrian had not yet joined at that time, this is strong evidence of independent development for the **general feature**. That fact likely defeats LexCore’s request to bar Evidentia’s entire feature. If the feature is general and Evidentia was already working on it before Adrian arrived, LexCore cannot show that the entire feature came from LexCore’s roadmap or trade secrets. ### B. But the general feature is not the only issue The fact pattern states that several technical choices in Evidentia’s final product resemble experiments reflected in LexCore’s evaluation data. That is the important nuance. A competitor may independently develop a general feature and still misappropriate specific technical details, experimental results, rejected design paths, or implementation choices that are not generally known. So the case should not be: “Evidentia’s feature is like LexCore’s roadmap; therefore Evidentia cannot release it.” The stronger case is: “Evidentia’s independent development of the general feature is not in dispute, but certain specific technical choices closely track LexCore’s confidential evaluation data and were not shown in Evidentia’s preexisting records.” ### C. The clean-room protocol helps Evidentia, but it is not perfect Evidentia claims Adrian has no access to LexCore-derived files and that it established a clean-room protocol. That helps Evidentia. But the protocol was adopted only two weeks after Adrian started. During that first two-week period, Adrian was already Evidentia’s product lead. That gap is significant. A clean room does not automatically erase influence that occurred before the protocol was adopted. If Adrian participated in early product decisions, feature prioritization, or technical direction during the first two weeks, the late clean-room protocol will not be a complete defense. ### D. Practical consequence LexCore should not seek to enjoin Evidentia’s general feature based solely on similarity to the roadmap. Instead, LexCore should seek expedited discovery and a targeted forensic audit to determine whether: 1. the specific technical choices at issue appear in Evidentia’s nine-month preexisting records; 2. those choices were made before, during, or after Adrian joined; 3. Adrian participated in the decisions; 4. the choices closely match LexCore’s confidential evaluation data; and 5. Evidentia’s clean-room protocol was effective as to the first two weeks. If the answer is that the technical choices predate Adrian and are documented in Evidentia’s records, LexCore’s product claim is weak. If the answer is that the choices track LexCore’s data and were influenced by Adrian, LexCore has a stronger claim as to those specific aspects. --- ## 7. Consequences of wiping the external drive Adrian wiped the external drive after receiving a cease-and-desist letter. The forensic report indicates a deliberate secure erase. This is important. ### A. Preservation duty Once LexCore sent a cease-and-desist letter identifying the drive and the disputed files, Adrian likely had a duty to preserve relevant evidence. At the latest, the duty arose when litigation became reasonably foreseeable. ### B. Spoliation and sanctions Deliberate secure erasure after notice strongly supports a spoliation argument. LexCore can seek sanctions, including: - preclusion of Adrian’s explanation for the wipe; - an instruction that the drive contained relevant company files; - an adverse inference that Adrian copied and retained trade secrets; - in the right circumstances, an adverse inference that Adrian used or disclosed the information, though that is a higher hurdle. ### C. The adverse-inference standard Under the governing law, an adverse inference requires intent to deprive. Adrian’s explanation is that the drive contained personal tax and medical records and that he believed LexCore already had every company file. That may limit the scope of the inference. It does not mean he automatically intended to deprive LexCore of evidence. But the facts still favor LexCore: - the wipe occurred after the cease-and-desist letter; - it was deliberate; - it used secure-erasure software; - it destroyed the only physical medium showing what Adrian took; - the drive contained directories that included company information; - Adrian is a former product director moving to a competitor. The wipe may not prove use, but it substantially undermines Adrian’s credibility and supports the inference that he took and attempted to destroy evidence of confidential information. ### D. Attribution to Evidentia Evidentia may argue that Adrian’s personal wiping of a personal external drive is not attributable to the company. That is plausible unless Evidentia directed, encouraged, or ratified the destruction, or unless the drive was used in Evidentia’s business. LexCore should be careful not to overstate Evidentia’s liability for the wipe. The spoliation claim is strongest against Adrian personally, though it may indirectly help LexCore against both Adrian and Evidentia by undermining the defense that no LexCore-derived information was used. --- ## 8. Whether LexCore can prove irreparable harm A TRO requires likely irreparable harm. This is one of the areas where LexCore must be careful not to overstate. ### A. Strengths LexCore can argue irreparable harm based on: 1. **Loss of customer relationships.** One customer already moved part of its business to Evidentia. Adrian is in a position to contact and influence other customers. Continued solicitation may cause ongoing customer loss. 2. **Loss of trade-secret value.** Once confidential evaluation data, pricing models, or next-release information is used by a direct competitor, the harm may not be fully compensable by damages. 3. **Imminent competitive harm.** Evidentia has already announced a similar feature. If specific technical choices derive from LexCore’s evaluation data, continued use could erode LexCore’s product advantage. 4. **Unauthorized post-revocation access.** The 5:08 p.m. download of next-release files shows that competitively sensitive information may already have been exposed. 5. **Destruction of evidence.** The wiping of the external drive increases the risk that LexCore cannot prove the full scope of misuse unless immediate relief and forensic protocols are imposed. ### B. Weaknesses Evidentia will argue that: - the feature was independently developed; - the customer-switch damages are quantifiable; - LexCore has not shown actual use; - inevitable disclosure is not enough; - a broad product injunction would cause Evidentia and Adrian substantial harm. ### C. Likely outcome LexCore is more likely to prove irreparable harm for: - further customer solicitation; - continued use of specifically identified trade secrets; - destruction or concealment of evidence; - limited clean-room/independent-development audit. LexCore is less likely to prove irreparable harm for: - a general ban on Adrian working on competing products; - a ban on Evidentia’s entire independently developed feature; - a global ban on all customer contact. **Conclusion:** LexCore can make a credible irreparable-harm case if the requested relief is narrow and tied to specific threatened harms. --- ## 9. Which requested restraints are likely overbroad LexCore currently wants four things: 1. prevent Adrian from working on competing products; 2. bar release of Evidentia’s feature; 3. image Evidentia’s systems; 4. prohibit contact with all LexCore customers. Each is problematic. ### A. Prevent Adrian from working on competing products **Likely overbroad and likely void.** This is effectively a noncompetition restriction. Under the governing law, a noncompetition restriction unrelated to the sale of a business is void. Adrian did not sign a noncompete, and the facts do not involve a sale of the business. LexCore should not ask the court to enjoin Adrian from working for a competitor generally. It can ask the court to enjoin him from **using or disclosing LexCore trade secrets** in his work. That is different. ### B. Bar release of Evidentia’s feature **Likely overbroad as currently framed.** Because Evidentia has development records showing it began work on the general feature nine months before Adrian joined, a blanket ban on the feature is unlikely to succeed. LexCore may be able to enjoin only specific aspects of the feature that are shown to be derived from LexCore trade secrets. But it cannot enjoin the entire feature merely because it resembles LexCore’s roadmap. ### C. Image Evidentia’s systems **Likely overbroad if it means full imaging.** Emergency forensic relief must be proportionate and should avoid unnecessarily exposing the new employer’s legitimate confidential information. A general order to image all Evidentia systems is likely to be denied. A targeted forensic protocol is much more defensible: limited search terms, specific repositories, Adrian’s devices, relevant product-development files, customer communications, and privilege/confidentiality protections. ### D. Prohibit contact with all LexCore customers **Overbroad.** The non-solicitation restriction is enforceable only as to customers with whom Adrian had material contact and only to the extent reasonably necessary. A ban on all LexCore customers exceeds that scope. Also, a ban on “contact” is broader than a ban on “solicitation.” Customers may initiate contact. The proper restriction is likely to prevent Adrian from actively encouraging or inducing customers to move business, not to prevent all communication. --- ## 10. Strongest defenses available to Adrian and Evidentia ### A. Adrian’s strongest defenses 1. **The information is not a trade secret.** Public statutes, court rules, and unenhanced public court documents are not trade secrets. The general roadmap may be weak because 400 employees could access it. 2. **LexCore’s secrecy measures were inadequate.** Inconsistent labeling, links without expiration, delayed offboarding, and broad roadmap access can be used to challenge reasonableness. 3. **The initial copying was authorized.** Adrian had valid access. Under the computer-access statute, misuse of information obtained through valid access is not unauthorized access. 4. **The work-from-home explanation.** If Adrian can show a pattern of copying files to work from home because remote connectivity was unreliable, that may reduce the inference of bad faith. But the 80GB volume and timing make this a difficult defense. 5. **The 5:08 p.m. downloads were automatic.** If the downloads were caused by an automated synchronization process and Adrian did not know his credentials had been revoked, he may have a factual defense to the unauthorized-access claim. 6. **No evidence of use or disclosure.** Evidentia says Adrian has no access to LexCore-derived files and that a clean-room protocol was implemented. Absent direct evidence, Adrian can argue that LexCore is relying on inevitable disclosure, which is insufficient. 7. **The feature was independently developed.** Evidentia’s nine-month development records are a strong defense to any claim that the general feature came from LexCore. 8. **The customer contact was initiated by the customer.** Adrian can argue that the customers contacted him first and that he merely responded. This is weaker for the customer to whom he made the promotional statement, but it may help for the other two. 9. **The wipe was for personal reasons.** Adrian can argue that he erased the drive because of personal tax and medical records and because he believed LexCore already had the company files. This may limit the adverse inference but is factually weak given the timing and secure erase. 10. **LexCore’s requested relief is overbroad.** Adrian can argue that a noncompete, feature ban, full imaging, and all-customer ban are inappropriate. --- ### B. Evidentia’s strongest defenses 1. **Independent development.** The nine-month development records are Evidentia’s strongest defense to the product claim. 2. **No access to LexCore-derived files.** If Evidentia can show that Adrian did not bring or share LexCore files, and that the clean-room protocol prevented exposure, it can rebut misappropriation. 3. **Clean-room protocol.** The protocol is not perfect because it came two weeks after Adrian started, but it still supports a defense, especially for later development. 4. **Adrian’s individual conduct is not automatically Evidentia’s liability.** Evidentia can argue that Adrian’s personal copying and wiping of an external drive do not make Evidentia liable unless the company directed or ratified the conduct. 5. **LexCore’s trade-secret protections were imperfect.** Evidentia can attack reasonableness, especially for the roadmap and inconsistently labeled materials. 6. **The requested remedies are overbroad.** Evidentia can argue that full system imaging, a feature ban, and a global customer-contact ban would expose its legitimate confidential information and unduly restrict competition. --- ## 11. Risk that an unsuccessful emergency application could damage LexCore strategically Filing a broad TRO carries real strategic risk. ### A. Credibility risk If LexCore asks for a noncompete-like order, a full feature ban, full imaging, and a ban on all customer contact, the court may view the application as overreaching. That can reduce credibility for later requests. ### B. Adverse record risk Although TRO rulings are not usually final merits decisions, the court’s skepticism can shape the case. If the court finds that LexCore cannot show concrete threatened misappropriation, that makes a later preliminary injunction harder. ### C. Competitor momentum A denial may embolden Evidentia and Adrian. Evidentia may accelerate the feature, Adrian may continue customer contact, and the customers may feel reassured that Evidentia is not exposed to LexCore’s claimed trade-secret rights. ### D. Customer-relations risk If LexCore appears to be trying to freeze competition rather than protect specific confidential information, customers may view LexCore as aggressive or unreasonable. ### E. Cost and delay A broad emergency application can be expensive and may consume time that would be better spent on expedited discovery and forensic comparison. ### F. Discovery and confidentiality complications A broad forensic request may lead to a protective-order dispute and force LexCore to expose more of its own claims and trade secrets in the early stages. **Mitigation:** Keep the emergency request narrow, particular, and tied to specific evidence: the copied directories, the 5:08 p.m. downloads, the customer statement, the development records, and the wiped drive. --- ## 12. Most defensible scope of temporary relief, forensic examination, expedited discovery, and settlement ### A. Defensible temporary relief LexCore should seek a narrow TRO or preliminary injunction containing the following: #### 1. Preservation order Adrian and Evidentia should be ordered to: - preserve all devices, external drives, cloud storage, emails, chats, calendars, and communications; - preserve all development records for the feature at issue; - preserve access logs, file-transfer logs, authentication logs, and offboarding logs; - not delete, alter, or destroy relevant evidence; - certify compliance with the litigation hold. This is highly defensible, especially given the wiped drive. #### 2. No use or disclosure of identified trade secrets LexCore should identify trade secrets in an annex with reasonable particularity, for example: - internal model-evaluation datasets; - feature-ranking experiments; - next-product-release files, including the 14 files downloaded at 5:08 p.m.; - pricing models; - customer usage statistics and renewal forecasts; - compiled customer-contact information containing nonpublic fields; - internal annotations to public court documents, if protectable. The order should state that Adrian shall not directly or indirectly use or disclose those identified materials in connection with: - Evidentia product development; - marketing or pricing; - customer solicitation; - competitive analysis; - any product or service that competes with LexCore. This is not a noncompete. It is a protection of specific confidential information. #### 3. Customer non-solicitation as to a defined list LexCore should attach a list of customers with whom Adrian had material contact. The order should state that Adrian shall not solicit those customers for twelve months. The order should avoid banning all customer contact. A better formulation is: - no solicitation of listed customers; - no use of LexCore confidential customer data to identify or target customers; - if a customer contacts Adrian, he may respond factually but shall not encourage or induce the customer to move business to Evidentia; - Adrian shall promptly notify LexCore of any contact involving listed customers, if the court finds that proportionate. #### 4. Limited clean-room / independent-development restriction Rather than barring Adrian from working on competing products, LexCore should seek a targeted restriction: - Adrian shall not participate in development or decision-making for the specific Evidentia feature or features at issue, to the extent they incorporate or may incorporate the identified LexCore trade secrets, until a forensic/independent-development audit is completed; - Evidentia shall maintain or strengthen its clean-room protocol; - Adrian shall not have access to, or influence, any development work that may be based on LexCore-derived information until the audit is complete. This is narrower than a noncompete and directly tied to the trade-secret issue. #### 5. Targeted forensic protocol See below. #### 6. Security bond and contempt provisions The order should include a reasonable bond and clear contempt sanctions for violations. --- ### B. Defensible forensic examination LexCore should not ask for full imaging of Evidentia’s systems. Instead, it should request a proportionate forensic protocol. A defensible protocol would include: 1. **Neutral forensic examiner.** The parties agree on a neutral expert, or the court appoints one. 2. **Limited scope.** The examination should cover: - Adrian’s devices and any remaining forensic traces of the external drive; - LexCore access and file-transfer logs already in LexCore’s possession; - Evidentia repositories, design documents, code commits, meeting notes, and product-management records for the specific feature; - communications between Adrian and Evidentia personnel; - customer communications involving listed LexCore customers; - preservation and deletion logs. 3. **Targeted search terms.** Search terms should be tied to LexCore trade secrets: - specific feature names; - file names and directory names from the copied materials; - technical terms from the evaluation datasets and experiments; - customer names from the material-contact list; - dates around Adrian’s hire, the feature announcement, and the 5:08 p.m. downloads. 4. **Confidentiality protections.** The protocol should use at least two tiers: - “Forensic — Litigation Team Only” for the examiner and necessary counsel; - “Attorneys’ Eyes Only” for highly sensitive material. 5. **No unnecessary exposure of Evidentia’s legitimate confidential information.** The protocol should avoid broad dumping of Evidentia’s unrelated systems, codebases, customer data, or trade secrets. 6. **Expedited timeline.** For example: - forensic protocol agreed within 7 days; - limited collection within 14 days; - forensic report within 30 days; - supplemental protocol if necessary. This approach is much more likely to be granted than a general order to image Evidentia’s systems. --- ### C. Defensible expedited discovery LexCore should seek expedited discovery on the following issues: #### 1. Adrian’s copying and retention - All logs showing files copied to the external drive; - any prior remote-work copying practices; - the purpose of the external drive; - whether it was used after Adrian joined Evidentia; - the circumstances of the wipe; - Adrian’s statements regarding personal files and belief that LexCore already had the files. #### 2. Offboarding and 5:08 p.m. downloads - authentication logs; - offboarding checklist; - credential-revocation time; - whether the 5:08 p.m. downloads were manual or automatic; - the identity and contents of the 14 files; - whether Adrian or a process initiated the downloads. #### 3. Evidentia feature development - complete development timeline; - identification of each technical choice at issue; - whether those choices appear in the nine-month preexisting records; - who made or recommended each choice; - Adrian’s role in each decision; - timing of decisions relative to Adrian’s hire; - clean-room protocol documentation; - evidence that Adrian did or did not access LexCore-derived information. #### 4. Customer solicitation - all communications between Adrian and the three customers; - who initiated each contact; - what Adrian said or sent; - whether the customer moved business; - whether Adrian used LexCore customer data to target or influence the customers. #### 5. Spoliation - forensic report on the drive; - metadata and deletion logs; - Adrian’s explanation; - whether Evidentia knew of or directed the wipe; - whether the drive was used for Evidentia work. This discovery is necessary because the strongest product-related claims depend on specific technical choices, not general similarity. --- ### D. Defensible settlement posture Settlement leverage is strongest after LexCore has: - obtained a narrow preservation and no-solicitation order; - begun targeted forensics; - obtained Evidentia’s development records; - compared Evidentia’s technical choices with LexCore’s evaluation data; - established the customer-solicitation claim; - used the wiping as credibility leverage. A defensible settlement might include: 1. **No admission of liability.** 2. **Adrian individual resolution:** - damages or agreed payment for confidentiality breach, non-solicitation, and unauthorized access; - no further solicitation of listed customers; - continued confidentiality obligations; - release of claims; - no public statements. 3. **Evidentia product resolution:** - independent-development certification for the general feature; - no use of specifically identified LexCore trade secrets; - continued clean-room protocol; - forensic audit of the specific feature or technical choices; - if misuse is found, modification or delay of the specific implicated aspects; - no broad feature ban if independent development is verified. 4. **Mutual releases** for the identified claims. 5. **Confidentiality of settlement terms.** 6. **No noncompete.** Settlement should avoid terms that operate as a void noncompetition restriction. If the forensic audit shows that Evidentia’s technical choices are independently documented, LexCore should consider settling Adrian’s individual claims and allowing the feature to proceed. If the audit shows specific technical choices closely track LexCore’s confidential evaluation data and were influenced by Adrian, LexCore should pursue a targeted product restriction or license/delay solution. --- ## 13. Whether LexCore should seek a TRO immediately or pursue a narrower course LexCore should seek **immediate emergency relief**, but only if the request is narrow and evidence-based. ### A. Why immediate relief is justified There is genuine urgency: - Adrian already wiped the drive after notice; - Adrian is actively responding to LexCore customers; - one customer already moved business; - Evidentia has announced a similar feature; - Adrian is product lead; - the 5:08 p.m. downloads show post-revocation access to next-release materials. Without relief, there is a real risk of further customer solicitation, further destruction of evidence, and continued use of confidential information. ### B. Why the current broad application should not be filed as-is The current request is too broad: - it includes a noncompete-like restraint; - it seeks to bar an independently developed feature; - it seeks full imaging of Evidentia’s systems; - it seeks a ban on all customer contact. As currently framed, the application is likely to be partially or substantially denied, and that could damage LexCore’s credibility and strategic position. ### C. Recommended immediate approach File immediately for a **narrow TRO** or, if the court requires a more developed record, seek expedited discovery plus a preliminary injunction. The immediate TRO should ask for: 1. **Preservation and no destruction.** 2. **Targeted forensic protocol.** 3. **No solicitation of listed material-contact customers.** 4. **No use or disclosure of specifically identified LexCore trade secrets.** 5. **Limited clean-room / independent-development audit as to the specific feature or technical choices at issue.** It should **not** ask for: - a general bar on Adrian working for a competitor; - a ban on Evidentia’s entire feature; - full imaging of Evidentia’s systems; - a ban on all contact with all LexCore customers. ### D. Fallback position If the court is not persuaded that threatened misappropriation of the technical/evaluation data is sufficiently concrete at the TRO stage, LexCore should accept: - preservation; - no further customer solicitation of listed customers; - no use of specifically identified trade secrets; - expedited discovery; - targeted forensics; and then return for a preliminary injunction after the forensic and development-record comparison is complete. --- ## 14. Final practical recommendation LexCore should reframe the case from “Adrian took 80GB and joined a competitor” to: > “Adrian took specific confidential product, pricing, customer, and evaluation information in violation of policy; accessed next-release files after revocation; solicited at least one customer using competitive language; and destroyed the external drive after notice. Evidentia’s general feature may be independent, but certain technical choices need immediate forensic comparison because they resemble LexCore’s confidential evaluation data.” That framing is far more defensible. The most likely path to success is: 1. **Immediate narrow TRO:** preservation, no solicitation of listed customers, no use of identified trade secrets, targeted forensics. 2. **Expedited discovery:** identify specific technical choices and compare them with Evidentia’s nine-month records. 3. **Preliminary injunction only if the record shows specific threatened use** of LexCore’s evaluation data, next-release information, pricing, or customer analytics. 4. **Settlement** if Evidentia’s independent-development record is strong but Adrian’s individual conduct remains problematic. 5. **Damages** for the customer that moved business, unauthorized access, and breach of confidentiality. LexCore should not chase the broad order it currently wants. It should seek the narrowest relief that stops the specific threats: further customer solicitation, further misuse of identified trade secrets, and further destruction of evidence.