We need answer a legal analysis question. Need be careful, likely US state? Governing law provided. We need analyze many points. User asks in English. We must produce final answer. Need think through all issues. Let's deeply analyze. We represent LexCore. Need likely trade secret categories, reasonableness, claims, significance copying and 5:08 downloads, Evidentia preexisting work/clean-room, wiping drive, irreparable harm, overbroad restraints, defenses, strategic risk, most defensible scope, immediate TRO vs narrower. Need craft legal memo perhaps. Need cite governing law principles 1-11. Need balance, realistic. Need note we are LexCore but should assess merits objectively. Let's parse facts. LexCore: litigation-software. Adrian product director resigned to Evidentia competitor. Trade secret law: actual/potential economic value from not generally known/readily ascertainable + reasonable measures. Reasonable measures: context; perfect security unnecessary, but ordinary business confidentiality cannot be established solely by describing info confidential after dispute. Misappropriation: acquiring via improper means or using/disclosing without consent when knew/should have known duty. Copying while technically authorized may still breach contract/confidentiality duties. Under computer-access statute, misuse info obtained through valid access not unauthorized access. Access after credentials revoked is unauthorized. Threatened misappropriation: concrete evidence of likely use/disclosure; inevitable disclosure alone insufficient. Non-solicit: 12-month customer non-solicit enforceable only as to customers with material contact and to extent reasonably necessary to protect legit relationships. Initial contact doesn't automatically defeat solicitation; question whether former employee actively encouraged/induced customer to move business. Noncompetition unrelated to sale of business void. TRO: likely success, likely irreparable harm, favorable balance, public interest. Emergency forensic relief proportionate; avoid exposing new employer legitimate confidential info. Destruction relevant evidence after preservation duty may support sanctions. Adverse inference requires intent to deprive. Facts: - Adrian copied ~80GB from laptop to encrypted external drive two days before resigning. - Directories: public statutes/court rules, product roadmaps, customer usage stats, pricing models, internal model-evaluation datasets, feature-ranking experiments, customer renewal forecasts, customer-contact spreadsheet, public court docs enhanced with internal annotations. - Adrian says routinely copied files to work from home due unreliable remote connection. Company permitted remote work but prohibited unapproved external storage. - Access levels: 400 employees roadmap; 32 eval datasets; 70 customer usage/renewal. - LexCore required confidentiality agreements, annual security training, password systems. Some links no expiration; docs inconsistently labeled; former access sometimes disabled days after departure. - Adrian access scheduled end 5pm final day. 5:08pm cached credential used to download 14 files concerning next product release. Adrian says automated sync caused and didn't know revoked. - After cease-and-desist, Adrian erased external drive. Says personal tax/medical records and believed LexCore already had every company file. Forensic: deliberately wiped using secure-erasure software. - Signed confidentiality and 12-month customer non-solicitation. No noncompete. - Three customers contacted Adrian after move. Responded to each. Told one: “You should see what Evidentia is launching. It solves the workflow problem LexCore kept postponing.” Customer moved part business. - 6 weeks after Adrian joined, Evidentia announced feature similar to confidential roadmap. Evidentia produced development records showing began work on general feature 9 months earlier. Several technical choices in final product resemble experiments in LexCore eval data. - Evidentia states Adrian no access to LexCore-derived files and established clean-room protocol 2 weeks after Adrian started. Adrian product lead immediately upon joining. - LexCore wants order preventing Adrian from working on competing products, barring release of Evidentia's feature, imaging Evidentia systems, prohibiting contact with all LexCore customers. Need analyze. Let's break down. 1. Trade secret categories: Likely: - Product roadmaps: if not generally known, limited access 400 employees but still not public, derive value. But broad access may affect secrecy but not necessarily. Need specific roadmap: next release? 14 files concerning next product release. Roadmaps as a whole may be secret if contain future features, timing, strategy. Public portions not. - Pricing models: likely trade secret if not readily ascertainable; competitive value. - Customer usage statistics and renewal forecasts: likely, limited 70, value in churn, upsell. - Internal model-evaluation datasets, feature-ranking experiments: likely if non-public, costly to create, not readily ascertainable, limited 32; can be especially strong due Evidentia technical choices resemblance. - Customer-contact spreadsheet: maybe trade secret? Customer lists generally can be be trade secret if compiled with additional data, not generally known, and value. But if simple names/contact info readily available? Enhanced with usage, renewal, contact person, interactions maybe. Need qualify as compiled list with confidential annotations. - Public statutes/court rules and public court docs: not trade secrets per se. Public court docs enhanced with LexCore internal annotations: annotations may be trade secret if not readily ascertainable and add value; underlying public docs not. Need separate. - Roadmap maybe too broadly known within company; but limited to 400. Reasonable access. If widely known among employees, still not generally known/readily ascertainable to public. But protection reasonableness may be challenged. Potential trade secrets: next product release details, feature priorities, timing, technical choices, pricing, customer analytics. 2. Reasonableness of protections: - Confidentiality agreements, security training, password systems: positive. - But some internal links no expiration, inconsistent labeling, access disabled days after departure: negatives. But perfect security unnecessary. Need evaluate in context. Could be sufficient if reasonable. 400 employees access to roadmap may be too broad? If 400 of total employees? Need know company size? If small, broad. But access limited to those needing. Evaluation data limited 32 strong. Customer data 70 reasonable. Need note LexCore's failures could undermine claim, especially for roadmap? But trade secret can exist despite imperfect protection. Need not rely on after-dispute labels. Need show measures before departure. The copying to external drive prohibited; policy existed. Confidentiality agreements. So likely reasonable for high-value data, perhaps less for roadmap due broad access and no expiration. But ordinary business confidentiality cannot be established solely by post-dispute descriptions; here preexisting policies. 3. Misappropriation etc. - Breach of confidentiality: Adrian copied 80GB including confidential info to unapproved external storage before resignation. Technical authorized? Copying from laptop to external drive may be prohibited by policy, and he had duty. If access technically authorized but policy prohibits external storage, copying may be improper? Misappropriation includes acquiring via improper means? If he had access authorized but used in breach of duty to maintain secrecy? He likely knew policy. Could establish misappropriation by use/disclosure without consent? Copying for personal retention likely not for work from home? He says routine. But 80GB two days before resignation to encrypted drive is suspicious. Need assess. Copying public statutes not issue. But if trade secrets copied, misappropriation? Acquisition: if authorized access but in breach of confidentiality? Many laws: misappropriation includes acquisition of trade secret by a person who owes duty to maintain secrecy and discovers trade secret under circumstances giving rise to duty. Or improper means includes breach of duty to maintain secrecy. The prompt: Misappropriation includes acquiring a trade secret through improper means or using or disclosing it without consent when person knew or should have known of a duty to maintain secrecy. Copying while technically authorized may still breach contract/confidentiality duties. Under computer-access statute, misuse of info obtained through valid access is not unauthorized access. Access after credentials revoked is unauthorized. So initial authorized copying: likely breach of confidentiality/policy if he took unapproved external drive and retained trade secrets. But for misappropriation, acquiring via improper means? If he had valid access but copied contrary to policy/duty, could be improper means? Need likely yes for misappropriation? Prompt says copying while technically authorized may still breach contract/confidentiality duties. It doesn't explicitly say it's misappropriation, but acquiring through improper means may include breach of duty. However computer-access says misuse info obtained through valid access not unauthorized access, but that's for unauthorized access claim, not trade secret misappropriation. Need distinguish. - Threatened misappropriation: Need concrete evidence of likely use/disclosure. Evidentia feature similar to roadmap, technical choices resemble eval data, Adrian product lead, became lead immediately, clean-room only two weeks later, but Evidentia had 9-month head start on general feature. Is that concrete? Could be threatened misappropriation if similarity plus access, but inevitable disclosure insufficient. Need show likely use of specific eval data, not just feature idea. Evidentia's records show independent development may defeat. But technical choices resembling experiments in LexCore eval data could be concrete. Need maybe partial threatened misappropriation for specific technical features, not entire feature or roadmap. Also Adrian retained 80GB, then wiped, making intent? Wiping after C&D could support inference of consciousness of guilt, but not necessarily use. Need concrete evidence of likely disclosure? No evidence he transmitted to Evidentia yet. But he is product lead, no clean room for first two weeks, product similar within six weeks. Could infer? Need standard likely success? Need weigh. - Breach of confidentiality: Adrian breach by copying unapproved external drive and possibly disclosing to Evidentia? Also erasing? He signed confidentiality agreement. Even if trade secret claim weak, contract. Need maybe for copied files. If he only used for work from home? But encrypted external drive and 80GB before resignation, no indication work from home. Policy prohibited. Breach likely. Need note if he had permission to remote work but not unapproved storage. If routine, maybe not. But volume and timing suspicious. - Customer solicitation: Non-solicit enforceable only customers material contact and reasonably necessary. Three customers contacted Adrian after move. He responded. Told one: "You should see what Evidentia is launching. It solves the workflow problem LexCore kept postponing." Customer moved part business. Does this violate? Need determine if he had material contact with those customers as product director? Probably yes if product director, customer usage/renewal data, contact spreadsheet. If material contact, non-solicit applies. Initial contact doesn't automatically defeat solicitation. Question actively encouraged or induced. His statement likely solicitation: suggesting Evidentia launch solves problem LexCore postponed, encouraging customer to see and move business. If he responded to customer-initiated contact with promotional pitch, likely solicitation. But if merely answering factual questions? The quote is proactive competitive pitch. Likely breach as to that customer, perhaps other two if similar. But restriction only as to customers with material contact and reasonable. Need tailor. - Unauthorized-access claims: initial authorized copying not unauthorized access under statute. 5:08 p.m. downloads after credentials revoked: access after revocation is unauthorized. But cached credential used, automatic sync. Adrian says didn't know revoked. Under statute maybe unauthorized if access after revoked, maybe strict? Need likely unauthorized access claim for 14 files concerning next product release, unless defense of technical/automated and lack knowledge? The prompt says access after credentials revoked is unauthorized. But maybe he can argue no culpable knowledge? Statute may require knowingly? Not specified. Need assess. Even if unauthorized, only 14 files. Misappropriation? Could be improper means for those files. Need also possible breach confidentiality? Access after termination, even accidental, maybe. But TRO? Limited. 4. Significance initial authorized copying and 5:08 downloads: - Initial: 80GB to encrypted drive two days before resignation. Strong evidence of intent to retain company info. Policy prohibits. Breaches confidentiality. But if he had work-from-home habit and remote unreliable, could be partial justification. However unapproved storage and volume/timing undermine. It does not by itself establish trade secret misappropriation if no use/disclosure, but supports breach and threatened? The wiping after C&D increases suspicion. It also destroys evidence, may allow adverse inference if intent to deprive. But because he says personal records, maybe not intent to deprive of company files? Secure erasure of entire drive after C&D likely duty to preserve relevant evidence. If intentional wipe, can support spoliation, but adverse inference requires intent to deprive. He may have believed LexCore already had every file, but that doesn't negate intent to destroy relevant evidence? Need maybe. Sanctions may include excluding defense on copying/wiping, adverse inference that copied trade secrets and/or used? Need caution. Since wiping occurred after C&D/preservation duty, may support sanctions. But to get adverse inference on use, need intent to deprive. Deliberate secure erase after demand likely infer intent to deprive. But he claims personal files; still destroyed potentially relevant. Could support inference he copied and retained, maybe used? Not automatically. - 5:08 downloads: After revocation, unauthorized access. Stronger evidence of intent to obtain confidential next-release info. But only 14 files and automated sync defense. Cached credential suggests process not manual. But if automated sync on laptop still connected after 5:08, could happen. Need maybe LexCore failed to ensure revocation immediately or disabled device. Adrian access scheduled end 5:00, cached credential used 8 min later. Could be technical glitch. Need not huge. Still under statute unauthorized access, may support improper means for those 14 files and breach. But TRO overbreadth? 5. Evidentia preexisting development and clean-room: - Evidentia produced development records: began general feature nine months earlier, i.e. before Adrian joined (Adrian joined? 6 weeks after, feature announced; 9 months before announcement = approx 7 months before Adrian joined? If announced 6 weeks after joining, 9 months earlier is 7 months before he joined). This is strong independent development defense for general feature. It defeats claim that entire feature came from LexCore. But several technical choices resemble experiments in LexCore evaluation data. This could indicate use of specific details, not just general feature. Need narrow relief for those technical choices if they are trade secrets and not independently developed. Clean-room protocol adopted two weeks after Adrian started; before that, Adrian product lead immediately. That gap is problematic. But Evidentia says Adrian has no access to LexCore-derived files. Clean-room late, but if he didn't have files and didn't disclose, maybe okay. However as product lead, he could influence based on memory. Need concrete evidence. Preexisting records may show independent, but technical choices resemblance can be explained by common industry choices, market demands, Adrian's general knowledge, or public knowledge. Need discovery to identify specific technical choices, compare development records, test whether in preexisting records. If they first appear after Adrian joined and match secret eval data, stronger. - Clean-room protocol: If adopted after he started, weak as to first two weeks, but can mitigate future. Need order requiring continued clean room, no access to Adrian's work product? But Adrian is product lead; maybe can't wall him? Need maybe restrict from specific product work if likely use. But broad bar on working competing products overbroad/noncompete void. Need tailor. 6. Consequences wiping external drive: - After C&D, preservation duty. Deliberate secure erase. Spoliation. Sanctions: monetary, inference, adverse inference? Need intent to deprive. He may argue personal files, believed LexCore already had files. But secure erasure is deliberate and after demand. Likely court can infer intent to deprive LexCore of evidence of copied files, maybe use. But adverse inference against Adrian/Evidentia? Evidentia maybe not liable for Adrian's spoliation unless agency/control? He was employee; acts within scope? Erasing drive personal? Could be attributed if he did after C&D while employee? Maybe as agent? Need careful. Evidentia could face if it directed or if Adrian acted in furtherance. But likely Adrian personally. Sanctions against Adrian: exclusion of evidence, adverse inference that drive contained trade secrets and he used/retained? Need not automatic. It undermines credibility of no use. But cannot use as sole basis for injunction? It supports threatened misappropriation? Maybe. - Since drive wiped, LexCore can't prove exact contents beyond forensic? Forensic report indicates wiped. Maybe can infer from system logs? Need expedited discovery of Adrian's devices, Evidentia. 7. Irreparable harm: - TRO requires likely irreparable harm. Trade secret misappropriation often presumed? But need show likely loss of customer, competitive edge, cannot be remedied by money. Facts: customer moved part business; Evidentia feature launch similar. Loss of customers and market share may be irreparable if ongoing. But if Evidentia independent, harm maybe compensable. Need show likely continued use/disclosure, loss of pricing advantage, roadmap. Adrian's solicitation likely caused customer switch; but one customer part business could be damages. However loss of trade secret secrecy once public/used may be irreparable because can't unring bell; but if feature not secret? Need likely. The 5:08 unauthorized downloads of next release and Adrian product lead could show imminent loss. But Evidentia independent development may reduce. Need argue: harm to customer relationships, pricing, competitive edge not fully quantifiable, ongoing; continued disclosure would cause loss of trade secret value. But need likely, not speculative. Could be mixed. For TRO, maybe strongest for customer non-solicit and forensic, not broad injunction. 8. Overbroad requested restraints: - Prevent Adrian from working on competing products: This is noncompetition. Noncompete void unless sale of business. Overbroad; likely void. Also overbroad as to all competing products, not limited to trade secrets. Should not get. - Barring release of Evidentia's feature: Overbroad if feature independently developed (9 months). Cannot enjoin entire feature. Maybe only specific infringing aspects if proven. Also chilling legitimate competition. Need narrow to particular technical choices derived from trade secrets, not general feature. - Imaging Evidentia's systems: Overbroad/invasive; emergency forensic relief must be proportionate and avoid exposing legitimate confidential info. Full imaging of new employer systems is likely overbroad. Instead targeted forensic protocol, neutral expert, privilege/confidentiality protocols, limited to Adrian's devices and relevant Evidentia repositories, maybe no full imaging. - Prohibiting contact with all LexCore customers: Overbroad; non-solicit enforceable only customers with material contact and reasonable. All customers too broad. Need list of customers Adrian had material contact with, maybe with usage/renewal data. Also maybe only solicitation, not all contact? Non-solicit usually prohibits solicitation, not passive contact. If customers contacted him, responding may be solicitation if inducing. Need tailor: no solicitation of enumerated customers for 12 months; maybe no use of confidential customer data; perhaps no direct contact without protocol? But all customers overbroad. 9. Strongest defenses: Adrian: - Information not trade secret: public statutes, public docs; roadmaps broadly accessible (400 employees), inconsistent labels, no expiration; readily ascertainable? Need show. - Authorized access and work-from-home routine: copying technically authorized, no improper means; policy? If routine, maybe not. But unapproved storage. - Clean development: Evidentia independent; no use/disclosure; clean room; no access to files. - 5:08 automated sync; no knowledge; technical glitch; no manual access; no culpability. - Wiping: personal data, legitimate; no intent to deprive; LexCore already had files; no spoliation; or proportionality. - No solicitation: customers initiated; he merely responded; quote maybe not enough? But it's proactive. Could argue no material contact? If product director maybe. Need identify. - No threatened misappropriation: inevitable disclosure insufficient; no concrete evidence of use; clean room; independent development. - Noncompete void; TRO overbroad. - Damages quantifiable, no irreparable harm. Evidentia: - Independent development records 9 months; feature general; no misappropriation; no access; clean-room (though late); no agency for Adrian? Maybe Adrian individual; company not liable if no use. - No unauthorized access to its systems? Not relevant. - Public info/market. - Remedies overbroad; no TRO standard met. - Trade secret protection unreasonable. - Customer contacts initiated; no inducement. 10. Risk unsuccessful emergency application damage LexCore strategically: - Losing TRO can create adverse factual findings? TRO on ex parte? If unsuccessful, court may find no likelihood success, harming future trial? Not binding but credibility. Opposing party may gain leverage; Adrian/Evidentia may continue, feature launch, customers. Could reveal claims, allow targeted defenses. Costs. Could be seen as overreaching, especially noncompete and full imaging, undermining credibility. May trigger protective orders limiting future discovery. Could encourage Adrian/Evidentia to argue inevitable disclosure, noncompete overreach. May cause customer relations? Need narrow to preserve. Also spoliation adverse inference if not? Need strategic. If TRO fails, may lose momentum, Evidentia may accelerate. But also can preserve via expedited discovery, preliminary injunction later. 11. Most defensible scope of temporary relief, forensic, expedited discovery, settlement: - TRO/PI: narrow. - Enjoin Adrian from using or disclosing identified LexCore trade secrets in connection with Evidentia work, particularly next product release and specific technical choices derived from eval data. - Enjoin Adrian from soliciting a defined list of LexCore customers with whom he had material contact for 12 months (or remaining term) and from using confidential customer data. Maybe no direct contact? But if customers contact, he can answer neutrally? Could require no solicitation; no use of customer-contact spreadsheet. - Require Adrian/Evidentia to maintain clean-room: Adrian not to work on specific Evidentia features that implicate LexCore trade secrets until forensic/discovery; or require Evidentia to implement/continue clean room, no access to Adrian's notes/devices? Need proportionate. Maybe no broad ban from competing products; only from using trade secrets. - Preserve and produce evidence; litigation hold; no destruction. - Forensic: limited imaging of Adrian's external drive? Already wiped; his laptop/devices; maybe Evidentia's systems only targeted: search terms, Adrian's file access, repositories, commit history, communications, feature development files. Use neutral forensic examiner, confidentiality protocols, two-step attorney review. No full Evidentia imaging. - Expedited discovery: identify exact trade secrets, access logs, file transfer logs, Adrian's devices, Evidentia development records for the specific feature and technical choices, customer interactions, preservation logs. Maybe expedited depositions. - Settlement: leverage spoliation/solicitation; limited license? Buyout? Clean room verification; Adrian restricted from specific features; customer non-solicit; damages for one customer? Maybe settlement with forensic audit, no admission. Could negotiate Adrian non-solicit, Evidentia no use of identified trade secrets, release feature? But if independent, can't bar feature. Could require Evidentia to certify clean-room and exclude Adrian from specific roadmap; perhaps damages. 12. Whether seek TRO immediately or narrower course: - If strong likelihood success for narrow claims (solicitation, unauthorized access, spoliation, threatened use of specific eval data), TRO may be justified for immediate preservation and prevention of further solicitation/unauthorized use. But broad TRO likely fail and harm. Need decide: immediate TRO? Probably seek narrow TRO or expedited injunction after limited evidence. Need maybe file immediate TRO for: preservation, no further solicitation of listed customers, no use/disclosure of specific trade secrets, forensic protocol. But if not enough evidence of threatened misappropriation of specific technical choices, maybe wait for expedited discovery to build record. However Adrian wiped drive after C&D; risk further destruction; customer solicitation ongoing; 5:08 unauthorized access; imminent risk. Need immediate narrow TRO to preserve and prevent further harm. But avoid overbroad. Could seek expedited hearing with ex parte? Need likely TRO requires likely success etc. Need maybe file TRO with specific exhibits: copied directories, policy, non-solicit, customer quote, development records. But Evidentia development records show independent; need not overclaim. Need perhaps structure final answer as memo with headings. Need be thorough. Let's think legal nuances. Trade secret identification: Need satisfy particularity. LexCore cannot just say 80GB categories. Need identify specific trade secrets: (a) next product release details and feature priorities/timing from 14 files; (b) internal model-evaluation datasets and feature-ranking experiments showing specific technical choices; (c) pricing models; (d) customer usage/renewal forecasts and compiled customer contact data with nonpublic metrics; (e) annotated public court docs? Maybe. Public statutes/court rules and unenhanced public docs not. Roadmaps: maybe if contain future unreleased features, but if known to 400 employees, still trade secret? Need note access may be too broad but not fatal; if 400 employees includes large portion, may undermine "not generally known" within company? Trade secret secrecy is from public, not all employees. But if widely known internally, economic value may be less. Need argue limited to product team. But facts say 400 LexCore employees could access; not know total. If company has 400 employees? If 400 could access, that's all? It says approximately 400 LexCore employees could access roadmap. Maybe company size? Could be all. That weakens. Need be realistic: roadmap likely weak if broad access; but next release details maybe more restricted? The 14 files concerning next product release maybe subset. The copied directories included product roadmaps broadly. Need differentiate: general product roadmap (400) less secret; next product release (14 files) maybe secret. Reasonable measures: need pre-existing. Confidentiality agreements, training, passwords. But inconsistent labels and links no expiration. For trade secrets, measures must be reasonable relative to value and access. Need maybe court will find reasonable for eval datasets (32) and customer data (70), but less for roadmap due 400 and no labels. But the prompt says perfect security unnecessary; ordinary business confidentiality cannot be established solely by after dispute. So likely some trade secrets survive. Need advise: focus on tightly restricted, high-value data, not public/broad. Misappropriation: - Acquisition: Adrian copied trade secrets to external drive. If he had duty, acquisition may be misappropriation. Need likely if improper means includes breach of confidentiality? The prompt: Misappropriation includes acquiring a trade secret through improper means or using or disclosing it without consent when person knew or should have known of a duty to maintain secrecy. "Copying information while technically authorized may still breach contract or confidentiality duties. Under computer-access statute, however, misuse of information obtained through valid access is not unauthorized access. Access after credentials are revoked is unauthorized." This suggests for trade secret, authorized copying can still be breach but not unauthorized access. It may be misappropriation if improper means? If "improper means" includes breach of contract/duty? Usually yes. But prompt may be distinguishing: copying while technically authorized may still breach contract/confidentiality duties, but not unauthorized access. So misappropriation can still occur if acquiring through improper means (breach of duty). Need say likely misappropriation as to trade secrets copied in violation of policy/confidentiality, but need identify trade secrets. If he had valid access and no policy? There was policy prohibiting unapproved storage. So yes. - Use/disclosure: No direct evidence he used/disclosed before feature announcement. But threat? Need concrete. Evidentia's product similar; technical choices resemble. Need maybe threat as to specific technical choices, not general feature. Also customer solicitation separate. - Breach confidentiality: stronger. He copied unapproved, maybe retained, wiped. Even if no trade secret, contract. - Customer solicitation: likely as to one customer. Need non-solicit enforceable only material contact. As product director, likely had material contact with three? Need verify. If he had material contact, his quote is inducement. If customers initiated, he responded with pitch. That is active encouragement. Likely breach. Maybe as to all three? He responded to each; quote only one. Need evidence for each. Restriction only material contact. If he had no material contact with some, not enforceable. Also if customer initiated and he only gave factual info, maybe not. But quote is promotional. - Unauthorized access: 5:08 after revocation: likely. Initial authorized: no. Need note cached credential automated: possible defense of no knowledge, but statute says access after revoked unauthorized; may still be accidental. For civil claim, unauthorized access maybe not require knowledge? Prompt doesn't specify. Need say likely but limited. It may support improper means for 14 files, not entire TRO. Threatened misappropriation: Need concrete evidence likely use/disclosure. We have: - Adrian had copied trade secrets, wiped after C&D (consciousness of guilt). - He is product lead at competitor, clean-room late. - Evidentia feature similar to confidential roadmap within 6 weeks; technical choices resemble eval data. - He made solicitation statement. But Evidentia has 9-month development records for general feature. This weakens. Need concrete as to specific technical choices: if they match eval data and not in preexisting records, likely. Need discovery. TRO may be granted for likely threatened use of specific secret technical choices if similarity and access. But not inevitable disclosure. Need not overstate. Irreparable harm: Need likely. For trade secrets, once disclosed/used, value lost; customer loss. But if Evidentia independent, harm may be damages. Need show Adrian's solicitation caused customer move and likely more; unauthorized access to next release could cause competitive harm before launch. The market for litigation software maybe niche; customer relationships. Need argue likely irreparable because continued use would erode pricing and product differentiation, not readily quantifiable. But courts skeptical. Need tie to concrete likely harm: customer moved, three customers engaged, feature launch. Need maybe not enough for entire feature but enough for targeted. Overbreadth: as above. Need note noncompete void; cannot prevent Adrian from working on competing products generally. Can only prevent use of trade secrets and solicitation. Evidentia feature release: can't enjoin independent feature. Imaging: not full; targeted. All customers: overbroad. Strongest defenses: list. Strategic risk: if TRO fails, adverse inferences? Actually if unsuccessful, court may not make findings, but could create record. Need discuss. Also if LexCore overreaches, may lose credibility, face sanctions, fees? Could reveal trade secrets in discovery? Need protective order. Evidentia may get injunction? No. But strategic: Adrian/Evidentia may use to argue no misuse, accelerate feature, customers reassured. Could also allow Evidentia to argue inevitable disclosure insufficient. Need mitigate. Most defensible scope: - Preliminary injunction or TRO? Need maybe immediate TRO narrow. Let's decide. The assignment asks whether LexCore should seek TRO immediately or narrower course. Need recommend. I'd say yes, but only a narrow TRO or expedited injunction after a limited emergency application focused on preservation, no further solicitation, no use of identified trade secrets, and targeted forensics. Avoid broad noncompete/product ban/full imaging/all customers. If evidence of specific threatened use not yet developed, use expedited discovery first to identify trade secrets and compare Evidentia technical choices, then seek PI. But there is urgent risk: Adrian already wiped drive, unauthorized downloads, customer moved. Need immediate TRO for preservation and no further solicitation/unauthorized use. Maybe TRO can issue if likely success on narrow claims: breach of non-solicit, unauthorized access, spoliation? TRO for threatened misappropriation may be harder but possible. Need recommend: file TRO seeking narrow relief, with fallback to expedited discovery if court declines product-related relief. Or consider not seeking product injunction now, only preservation/solicitation, then expedited discovery. Need be nuanced: "immediately" maybe yes for anti-spoliation/no solicitation; but for feature/product, pursue narrower course. Need perhaps recommend immediate narrow TRO or, if unable to establish concrete threatened use, expedited discovery. Since question asks whether should seek TRO immediately or narrower course, answer: Seek immediate but narrowed TRO; do not seek all four. If the court is not persuaded on threatened misappropriation, use expedited discovery. Need explain. Need maybe propose specific order: 1. Adrian and Evidentia preserve all evidence (devices, logs, development records, communications) and maintain litigation hold; no deletion. 2. Adrian shall not use or disclose identified LexCore trade secrets (list: next-release files, eval datasets/experiments, pricing models, customer usage/renewal data, customer contact list with confidential annotations) in developing, marketing, or selling competing products, or in soliciting LexCore customers. 3. Adrian shall not solicit any LexCore customer with whom he had material contact (list attached) for 12 months; may not use confidential customer data; if contacted, respond only factually and notify LexCore? Maybe require no use of customer-contact spreadsheet. But all customers overbroad. 4. Evidentia shall continue clean-room protocol: Adrian not to have access to, or influence, development of the specific feature(s) at issue until independent-development audit; or require separation of Adrian from those workstreams. But can't ban all competing products. Need maybe "no use of Adrian's work product that derives from LexCore trade secrets". If he is product lead, maybe require a forensic audit and if no use, release restrictions. Need balance. 5. Forensic protocol: neutral examiner; limited search terms; privilege log; confidentiality; no full imaging; expedited protocol. 6. Expedited discovery: file transfer logs, access logs, Adrian's devices, Evidentia development records for feature, customer communications, preservation/wipe logs. 7. Security bond? Maybe. 8. Contempt sanctions. Need discuss settlement: After narrow TRO, negotiate: - Evidentia independent development certification and exclusion of Adrian from specific feature for period; clean-room audit. - Adrian non-solicit for listed customers; confidentiality; damages. - Possibly buyout/license of roadmap? If Evidentia independent, not necessary. Could settle with Adrian's separation from product lead? But noncompete void. Could require Adrian not to work on feature similar to LexCore's next release for limited period? That may be de facto noncompete? Need careful. Could require no use of trade secrets, not no competing. Settlement can include agreed restrictions if not court-ordered noncompete? But if noncompete void, perhaps court won't enforce? Parties can contract for noncompete? Governing law says noncompetition unrelated to sale void. So can't enforce. Settlement maybe with damages, no admission, release, Adrian restricted from specific projects by contract? If void, likely unenforceable. Better: license/clean room, damages. Need maybe discuss damages: one customer moved part business; can quantify. But TRO not about damages. Settlement could include damages for customer switch and unauthorized access. Need include risk of spoliation sanctions: adverse inference. Need maybe in TRO request, ask court to deem copied files contained trade secrets? No, ask adverse inference later. Need maybe discuss computer-access statute: 5:08 downloads unauthorized, but initial authorized copying not. Need maybe claim for civil damages under CFAA? Not sure. But question asks unauthorized-access claims. Need say initial authorized not; 5:08 likely yes. If cached automatic, maybe defense, but access after revocation is unauthorized; knowledge may matter for damages/claims. Need maybe not central to TRO. Need maybe discuss "ordinary business confidentiality cannot be established solely by describing information as confidential after dispute arises." Need use: LexCore had pre-existing agreements/training/policies, not just post-dispute labels. But inconsistent labeling and no expiration weaken. Need show measures were reasonable. Need maybe argue that for evaluation data and customer data, limited access and high value justify reasonable. For roadmap, broad access and inconsistent labels may be challenged; focus on next-release subset. Need maybe discuss "threatened misappropriation requires concrete evidence of likely use or disclosure. Inevitable disclosure alone is insufficient." Need emphasize: can't just say Adrian knows too much. Need use facts: similar feature, technical choices, clean-room gap, wipe. But Evidentia independent records. Need need specific technical choices. Need maybe TRO only if can show specific choices not in Evidentia preexisting records. If not, wait. Need maybe discuss "emergency forensic relief must be proportionate. Avoid exposing new employer legitimate confidential info." Need propose targeted protocol: search terms tied to LexCore trade secrets, hash values, file names, author names, dates around Adrian's hire, development repo for feature, Adrian's devices, external drives, communications. Use privilege/confidentiality tiers, neutral examiner, redactions, quick-look? Need not expose all. Maybe no full imaging; logical collection of relevant repos; if necessary, image only specific devices (Adrian's) and Evidentia's repositories under protocol. Need maybe discuss public court docs enhanced with annotations: Are annotations trade secret? If internal annotations reflect analytical method, maybe. But public docs themselves not. Need maybe not central. Need maybe discuss customer-contact spreadsheet: If just names/email/phone, not trade secret if readily available. But if includes renewal forecasts, usage, notes, contact person, opportunity, then compiled customer list can be. Need separate. Need maybe discuss "feature-ranking experiments" and "internal model-evaluation datasets" likely most defensible. Because Evidentia technical choices resemble experiments. These are costly, nonpublic, limited access. Need focus TRO on these. Need maybe discuss "pricing models": likely trade secret, but may be used in customer solicitation? Could be. Need not overclaim. Need maybe discuss "customer usage statistics/renewal forecasts": limited 70; value; but if only aggregate? Need likely. Could support customer solicitation? Use of renewal forecasts to target customers maybe. Need maybe discuss "product roadmaps": If publicly known? No, but 400 employees. Need maybe trade secret if contains future features/timing not known to market. But if widely accessible, less. Need maybe identify "next product release" 14 files as more secret. The 5:08 files concerning next release likely high value. Evidentia feature similar to roadmap within 6 weeks. But Evidentia independent general feature. Need distinguish feature idea vs roadmap specifics. General feature idea maybe not secret if market problem obvious; roadmap details (timing, prioritization, technical approach) secret. Need maybe discuss "Adrian routinely copied files to work from home" and company permitted remote work. If true, may explain 80GB? But 80GB and encrypted drive prohibited. Need maybe if remote unreliable, copying may be understandable but not unapproved. Need evaluate credibility. The fact he copied two days before resignation undermines routine. Need maybe use to support bad faith. Need maybe discuss "Some internal links had no expiration date. Documents inconsistently labeled. Former employees’ access sometimes disabled several days after departure." These show security flaws. Need maybe court could find LexCore failed reasonable measures for some categories. Need argue context: 32 employees for eval data, 70 for customer data, confidentiality agreements. But the 400 roadmap access and no expiration may be problematic. Need not hide. Need advise to identify strongest secrets and not rely on weak. Need maybe discuss "Adrian says he believed LexCore already possessed every company file" after wipe. If LexCore's system logs show original files on laptop/server, he may be correct that company had copies. But that doesn't negate spoliation of external drive evidence of copying/use. Need maybe if LexCore had original files, but external drive could show he took them, maybe use? The original files exist, but the external drive itself is evidence of retention. So wiping still relevant. If company had every file, less harm? But still spoliation. Need note. Need maybe discuss "forensic report indicates drive was deliberately wiped using secure-erasure software." This is strong. Could support adverse inference. Need maybe ask court to draw inference that drive contained trade secrets and Adrian intended to deprive. But adverse inference on use? Need intent to deprive. Deliberate secure erase after C&D likely intent to deprive. But he claims personal records; still secure erase entire drive. Need maybe court could infer he destroyed evidence of company files, but not necessarily that he used them. Need sanctions: exclude his explanation, adverse inference that he copied and retained trade secrets, maybe that he disclosed/used? Need not too aggressive. Need maybe discuss "Evidentia clean-room protocol adopted two weeks after Adrian started." This is a defense but also weakness: first two weeks he was product lead with no protocol. Need ask discovery: what did he do in first two weeks? Did he participate in feature decisions? If technical choices in final product resemble LexCore eval data and were made in first two weeks or around feature announcement, stronger. If clean room after, still could have influenced before. Need maybe TRO requiring continued clean room and no involvement in specific feature until audit. Need maybe discuss "Adrian became Evidentia's product lead immediately upon joining." This increases risk of use by memory. But inevitable disclosure insufficient. Need concrete. Need maybe discuss "Three LexCore customers contacted Adrian after his move. Adrian responded to each." If customers initiated, non-solicit may still be breached if he induced. Need maybe quote: "You should see what Evidentia is launching. It solves the workflow problem LexCore kept postponing." This is affirmative solicitation. It disparages LexCore slightly. Customer moved part business. Likely breach. Need maybe as to other two, need similar evidence. Non-solicit only material contact. Need identify list. Need maybe discuss "Noncompetition restriction unrelated to sale of business is void." So LexCore's request to prevent Adrian from working on competing products is likely void as noncompete. Need not seek. But can seek injunction against misappropriation/use of trade secrets, which is not noncompete. Need phrase carefully: "Adrian shall not use LexCore trade secrets in connection with any product he develops or supports," not "shall not work on competing products." This distinction critical. Also cannot bar Evidentia from feature if independent. Need maybe discuss "public interest" TRO factor: favors preventing misuse of trade secrets but also freedom to compete and protect confidentiality of new employer. Need balance: narrow tailored relief favors. Need maybe discuss "likely success" for each claim. Need maybe table. Could produce a memo with conclusions. Need maybe consider if LexCore should seek TRO immediately. Need weigh urgency: Adrian wiped drive after C&D, possible further destruction; 5:08 unauthorized access; customer solicitation ongoing; Evidentia feature soon? If TRO delay, further harm. Need yes but narrow. If no concrete evidence of use, court may deny threatened misappropriation but can grant preservation/no solicitation. Need maybe request expedited discovery under TRO. Need maybe if ex parte TRO, need bond. Need maybe propose "narrow TRO + expedited discovery; if court not persuaded on product use, fallback to PI after discovery." Need maybe discuss "most defensible scope of temporary relief, forensic examination, expedited discovery, and settlement." Need perhaps separate sections. Let's outline final answer: Title: Memo to LexCore re Adrian/Evidentia. I. Executive summary: - Strongest claims: trade secret (eval datasets/experiments, next release, pricing, customer analytics), breach of confidentiality, customer non-solicit, unauthorized access for 5:08 downloads, spoliation. - Weaker: general roadmap, public materials, broad noncompete, feature ban, full imaging, all-customer ban. - Recommend immediate narrow TRO: preserve evidence, no further solicitation of listed customers, no use/disclosure of identified trade secrets, targeted forensics; not noncompete/feature ban/full imaging/all customers. Use expedited discovery to prove specific use. Settle if independent development confirmed. II. Trade secret categories: - Likely: next product release details; internal eval datasets/feature-ranking experiments; pricing models; customer usage/renewal forecasts; compiled customer contact list with confidential data; annotations to public court docs if nonpublic analytical value. - Unlikely: public statutes/court rules; public court docs without annotations; general feature ideas; roadmap if too broad? But roadmap as to unreleased features may qualify; focus on 14 files. - Access restrictions: 32/70 supports; 400 roadmap weakens but not fatal. III. Reasonableness: - Positive: NDAs, training, passwords, policies, limited access, prohibition external storage. - Negative: inconsistent labels, no expiration, delayed deprovisioning, 400 roadmap access. - Likely reasonable for high-value limited data; maybe less for broad roadmap. Need not perfect. Post-dispute labels not sole. Need identify pre-existing. IV. Claims: A. Misappropriation: - Acquisition: copying to unapproved encrypted drive likely improper/breach duty as to trade secrets. Need particularity. Public materials no. - Use/disclosure: no direct proof yet; threatened misappropriation concrete? Similar feature/technical choices + clean-room gap + wipe; but independent development weakens. Need specific technical choices. - 5:08 unauthorized downloads: unauthorized access after revocation; improper means for 14 files. Automated sync defense; limited. B. Breach confidentiality: likely for copying/retention/wiping; even if trade secret fails. C. Customer non-solicit: likely for customers with material contact; quote = inducement; not defeated by customer initiating; tailor list. D. Unauthorized access: initial authorized no; 5:08 yes. Need maybe statutory elements/knowledge. E. Spoliation: after C&D, deliberate secure wipe; preservation duty; sanctions/adverse inference if intent to deprive. Strong but not conclusive. V. Significance of copying and 5:08: - Initial: evidence intent to retain, breach, supports trade secret; but authorized access limits unauthorized access; work-from-home argument; volume/timing undermines. - 5:08: post-revocation unauthorized; next-release files; strong but small; automated defense; supports likelihood of continued access and threat. VI. Evidentia development/clean-room: - 9-month records strong independent development for general feature; defeats broad feature injunction. - Technical choices resemblance to eval data: possible specific misappropriation; need compare with preexisting records. If choices first appear after Adrian joined and match secret data, stronger. - Clean-room late: first two weeks gap; as product lead, risk. But if no access to files and no evidence use, defense. Need discovery/forensic. VII. Wiping drive: - Spoliation; secure erase after C&D; likely intent to deprive; sanctions/adverse inference. Undermines credibility. But not direct proof of use; Evidentia not automatically liable. Could infer copied trade secrets and maybe use if necessary. VIII. Irreparable harm: - Need likely. Strengths: loss of customer, trade secret value, competitive edge, ongoing solicitation, unauthorized next-release access. Weaknesses: independent development, damages for customer maybe quantifiable, no direct proof of use. Need show likely continued use/disclosure and inability to remedy. Maybe enough for targeted relief. IX. Overbroad restraints: - No competing products: noncompete void. - Ban Evidentia feature: overbroad; independent development. - Full imaging: overbroad; proportionality. - All customers: overbroad; non-solicit limited. - Need narrow to identified secrets, listed customers, targeted forensics. X. Defenses: - Adrian: no trade secret, authorized access, work-from-home, no use, independent development, clean room, automated sync, personal files, no solicitation, no irreparable harm. - Evidentia: independent development, no access, clean room, no agency, trade secret protection unreasonable, feature general, overbroad remedies. XI. Strategic risk of unsuccessful emergency application: - Credibility, overreach, accelerated competitor, customer reassurance, adverse record, costs, protective order constraints, spoliation? Need mitigate. XII. Most defensible scope: - Temporary relief: preserve, no use/disclosure of identified trade secrets, no solicitation of listed customers, clean-room/no involvement in specific feature until audit, forensic protocol. - Forensic: neutral, targeted, search terms, limited repositories, privilege/confidentiality, no full imaging, hash/chain of custody, expedited. - Expedited discovery: file logs, access logs, Adrian devices, Evidentia development records, customer communications, preservation logs, technical choices comparison. - Settlement: after narrow relief/discovery; possible independent development certification, Adrian excluded from specific feature, damages, non-solicit, release, no admission; avoid noncompete. XIII. TRO immediately? Recommend yes, narrow TRO or expedited hearing. If can't establish concrete threatened use, seek only preservation/no solicitation and expedited discovery; then PI. Avoid overbroad. Maybe propose order. Need maybe include "conclusion" with recommendations. Need ensure answer addresses every bullet. Need maybe use headings matching assignment. Need be detailed. Need maybe include caveats: facts not exhaustive, need discovery. Need maybe not legal advice? But as role, can advise. Let's deepen each point with legal reasoning. Trade secret particularity: - Under law, information must derive value from secrecy and reasonable measures. Need identify with reasonable particularity. We can propose categories: 1. Next-Release Product Data: the 14 files downloaded at 5:08 and roadmap entries concerning features not generally known, release timing, priorities. Economic value: competitive head start. Secrecy: limited? 400 access to roadmap but next release maybe more restricted? Need maybe if 14 files were next product release, likely. But if 400 could access roadmap, maybe not. Need say strongest if specific next-release documents were not generally known and access limited/controlled. 2. Model-evaluation datasets and feature-ranking experiments: highly technical, costly, limited 32, not readily ascertainable. Evidentia technical choices resemble. Strong. 3. Pricing models: value, not public. 4. Customer usage statistics and renewal forecasts: limited 70, predictive, not public. 5. Customer-contact spreadsheet: if contains compiled nonpublic info (owner, notes, renewal, usage, opportunities) then trade secret; if only public contact info, no. 6. Annotated public court docs: annotations may be if they reflect confidential analytical methodology/results; public docs not. 7. Public statutes/court rules: no. - Product roadmaps: possible but broad access. Need narrow to unreleased, non-obvious. If 400 employees can access, may still be secret if not public, but reasonableness and value may be challenged. Need maybe not central. Reasonable measures: - Reasonableness in context. Need compare value and access. 32 employees for eval data is strong; 70 for customer data strong; 400 for roadmap weak. Confidentiality agreements, annual training, passwords, policy prohibiting unapproved storage. Some links no expiration and inconsistent labeling are deficiencies but not fatal. Delayed deprovisioning: Adrian's access scheduled end 5pm but cached credential used 5:08; not necessarily unreasonable. Need maybe court will find LexCore took reasonable steps but not perfect. Need emphasize pre-existing, not after dispute. Misappropriation: - Acquiring through improper means: If "improper means" includes breach of duty, copying to unapproved drive likely. Need maybe if he had authorization to copy for work but policy prohibited, is it improper? The prompt says copying while technically authorized may still breach contract/confidentiality duties. So yes. Need maybe if he routinely copied, but unapproved storage. The fact encrypted external drive and 80GB two days before resignation supports improper. Need maybe misappropriation as to each copied trade secret. But need identify. If he merely copied public statutes, no. - Use/disclosure: Need consent? He has no right to retain/use after departure. If he used to help Evidentia, misappropriation. No direct evidence. Threatened: see below. - 5:08: Access after revocation unauthorized. If he used cached credential to download next-release files, likely improper means/misappropriation for those files. But if automated, maybe not knowing. Under trade secret, knowledge/duty? He knew he was leaving; but maybe didn't know revoked. Could be accidental. Need still unauthorized under statute, but for misappropriation maybe improper means requires knowingly? Prompt: "Misappropriation includes acquiring a trade secret through improper means or using or disclosing it without consent when the person knew or should have known of a duty to maintain secrecy." For acquiring through improper means, maybe knowledge not explicit? Could be. Need say likely but limited; automated sync may defeat intent, but access after revocation is unauthorized. Need maybe if statute requires knowledge, defense. But prompt says access after credentials revoked is unauthorized, not necessarily misappropriation. Need separate. Threatened misappropriation: - Need concrete evidence. Need list: - Adrian copied trade secrets, including eval data and next-release files. - He wiped drive after C&D (inference of consciousness of guilt). - He became product lead; clean-room only after two weeks. - Evidentia announced similar feature six weeks; technical choices resemble eval data. - He solicited customer about Evidentia launch solving workflow problem. - But independent development records for general feature 9 months earlier. Need not enough for general feature. Need concrete as to specific technical choices. If development records show those choices predate Adrian, no. If they postdate and match, yes. - Inevitable disclosure: can't rely solely on his knowledge. Need avoid overclaiming. Breach of confidentiality: - Signed agreement; copied prohibited; retained; wiped. Even if no trade secret, likely breach. Need maybe damages? Not central. Customer solicitation: - Non-solicit enforceable only customers with material contact. Need define material contact: as product director, likely had significant interactions, access to customer usage/renewal, contact spreadsheet. Need verify for three. If yes, enforceable. - Initial contact doesn't defeat. He responded with promotional pitch, actively encouraged. Quote: "You should see what Evidentia is launching. It solves the workflow problem LexCore kept postponing." This suggests he induced customer to consider/move. Customer moved part business. Likely breach as to that customer. For other two, need similar evidence; if just polite response, maybe not. Restriction should be limited to material-contact customers and reasonable (12 months). Need maybe no contact with all customers overbroad. Unauthorized access: - Initial authorized copying: not unauthorized under statute because valid access. Misuse of info obtained through valid access not unauthorized. So no computer-access claim for 80GB copy. But may be contract/trade secret. - 5:08 downloads: after revocation, unauthorized. Cached credential and automation may be defense of lack of knowledge/negligence, but statutory unauthorized access may be strict or require knowledge? Prompt says access after credentials revoked is unauthorized. Need likely claim. But only 14 files; maybe damages limited. Supports threat. Evidentia preexisting development/clean-room: - Development records: strong. If feature general began 9 months before announcement (7 months before Adrian), independent. This likely defeats enjoining feature. But technical choices resemblance: need identify whether in preexisting records. If some choices match LexCore eval data and not in preexisting records, possible specific misappropriation. Need forensic/expedited discovery. - Clean-room protocol adopted two weeks after start: not immediate. Adrian product lead immediately. This weakens defense as to first two weeks and any decisions made then. But if protocol now, future risk reduced. Need require continuation and possibly exclusion from specific workstream until audit. Need not bar all product work. - Evidentia states Adrian no access to LexCore-derived files: possible but unverified. Wiping prevents proof. Clean room doesn't prevent use from memory. Need concrete evidence. Wiping: - Preservation duty arose after C&D (or when litigation reasonably anticipated). Deliberate secure erase. Spoliation. Sanctions may include instruction that drive contained trade secrets, adverse inference on copying/retention/use, exclusion of his explanation. Adverse inference requires intent to deprive. Deliberate secure erase after demand likely supports intent; his personal-file explanation may not negate. But if he believed LexCore already had every file, maybe no intent to deprive of company data? Still relevant to whether he intended to destroy evidence. Need maybe court could infer he intended to deprive LexCore of proof of what he took and whether he disclosed. But not automatic on Evidentia's use. Evidentia liability? If Adrian was employee and acted in scope? Erasing personal drive maybe not Evidentia's. But if Evidentia directed or knew, maybe. Need focus on Adrian. - Strategic: spoliation can bolster TRO and settlement leverage. Irreparable harm: - Need likely. Trade secret law: harm to secrecy and competitive position may be irreparable. Need show not speculative. - Customer already moved part business; Adrian may continue soliciting; loss of customer relationships and pricing leverage. - Unauthorized next-release access could allow competitor to preempt. - Use of eval data could undermine product differentiation. - Once trade secret used/disclosed, cannot be restored; damages may be inadequate if ongoing. - But if Evidentia independent and customer damages quantifiable, court may say adequate remedy. Need tie to likely continued misuse. Need maybe for TRO, show immediate risk of further solicitation and destruction. Overbroad restraints: - Prevent Adrian from working on competing products: noncompete void. Also overbroad. Cannot enjoin general competition. - Barring release of Evidentia's feature: overbroad; independent development. Could only enjoin specific aspects if derived from trade secrets. Also may implicate Evidentia's confidential info. - Imaging Evidentia's systems: overbroad; proportionality. Need targeted. - Prohibiting contact with all LexCore customers: overbroad; non-solicit limited to material contact. Also "contact" broader than solicitation; customers can initiate. Need no solicitation, not no contact. If need no direct contact, maybe for listed customers and only during TRO, with protocol. Strongest defenses: Adrian: - No trade secret: public; roadmap broad; annotations not valuable; customer list public. - Reasonableness: LexCore security flaws. - Authorized access: copying technically authorized; work-from-home routine; no improper means for initial. - 5:08 automated; no knowledge; no manual unauthorized access. - No use/disclosure: no evidence; clean room; independent development; wiped drive because personal; no threat. - Customer: initiated; no inducement; no material contact; quote not solicitation? (but likely weak). - No irreparable harm; damages. - Noncompete void; TRO overbroad. Evidentia: - Independent development 9 months; general feature; no misappropriation. - No access to LexCore files; clean-room; no agency. - Trade secrets not reasonably protected or not secrets. - Remedies overbroad; no irreparable harm. - Customer initiated. Risk unsuccessful emergency application: - If court denies, may signal weakness; Evidentia may proceed; customers reassured; Adrian may use momentum. Could create adverse factual record? At TRO, no full findings but arguments. Could increase costs and delay. Could reveal trade secrets in filings/discovery. Could lead to protective order that hampers later. Could encourage Adrian to argue no misuse and clean room. Could damage relationship with customers. Need mitigate by narrow, evidence-based claims. Also if LexCore overreaches with noncompete/full imaging, court may view as coercive, possibly fees. Need preserve credibility. Most defensible scope: - Temporary relief: * Identify trade secrets in annex with particularity: next-release files, eval datasets/experiments, pricing models, customer usage/renewal forecasts, customer-contact list with confidential fields, annotated public docs. * Enjoin Adrian from using or disclosing those in any Evidentia product, marketing, pricing, or customer solicitation. * Enjoin Adrian from soliciting listed material-contact customers for 12 months; require no use of confidential customer data; maybe require neutral response protocol if contacted. * Require Evidentia to maintain/enhance clean-room: Adrian not to participate in development of the specific feature(s) at issue or any product feature incorporating the identified trade secrets until independent development audit; no access to LexCore-derived files (though he shouldn't have); require separation of work product. * Preservation/litigation hold: all devices, logs, development records, communications, external drives, cloud, backups; no deletion; forensic imaging of Adrian's devices under protocol. * No broad ban on competing products or entire feature; no all-customer ban; no full Evidentia imaging. - Forensic examination: * Neutral forensic expert agreed by parties or court-appointed. * Two-tier confidentiality: "Litigation Confidential - Forensic Only" then "Attorneys' Eyes Only" for highly sensitive. * Limited collection: Adrian's devices (laptop, external drive remnants? wiped, but maybe logs), Evidentia repositories for feature, file access logs, commit history, design docs, meeting notes, communications with customers, search terms tied to LexCore secrets. * Avoid broad Evidentia systems; use hash, targeted keywords, author/date filters, privilege review, sampling. * Expedited protocol: 7-14 days for forensic, 30 days for discovery. - Expedited discovery: * LexCore file transfer/access logs for Adrian before/after departure, cached credential logs. * Adrian's explanation of copying routine: prior transfers, work-from-home logs, external drive approvals. * Evidentia development records for feature: timeline, technical choices, design decisions, preexisting docs, clean-room protocol, Adrian's involvement, who made choices, source of data. * Customer communications: all contacts, who initiated, what said, business moved. * Wiping: metadata, forensic report, Adrian's statement, whether Evidentia knew/directed. * Trade secret identification: detailed charts, access controls, value. - Settlement: * Use narrow TRO and spoliation leverage. * Possible terms: Adrian and Evidentia no admission; Evidentia independent development certification for general feature; Adrian excluded from specific feature/workstream for defined period (not general noncompete) or no use of identified trade secrets; clean-room audit; damages for customer switch/unauthorized access; mutual releases; continued non-solicit for listed customers; confidentiality; no publicity. * If evidence shows specific technical choices misappropriated, negotiate license or delay/modify feature aspects. If independent, settle Adrian's individual claims (confidentiality/non-solicit/spoliation) and allow feature. Whether TRO immediately: - Need urgent? Yes if risk of further solicitation, destruction, use before feature launch. But broad TRO likely fail. Recommend immediate narrow TRO/ex parte? Need maybe if can show likely success on narrow. If not, file complaint and seek expedited injunction after discovery. But given wipe and unauthorized access, immediate TRO for preservation and no further solicitation is defensible. Product-related relief should be limited to identified trade secrets and maybe pending forensic audit. Need maybe request TRO with bond. Need maybe if court denies product use, still get preservation. - Could also consider "narrower course" if not enough concrete evidence: expedited discovery first. But urgency favors TRO. Need recommend: Seek immediate TRO, but only narrow. If unable to make concrete showing of threatened use of specific eval data, limit TRO to (1) preservation, (2) no solicitation of listed customers, (3) no further unauthorized access/use of identified trade secrets, (4) forensic protocol. Then pursue PI after expedited discovery. Need maybe include a "proposed order" language. Need maybe mention "public interest" favors preventing unjustified use of trade secrets and protecting competitive process, but also favors employees' ability to work and competitors' right to use independent information. Narrow relief balances. Need maybe mention "balance of hardships": LexCore's hardship from ongoing misuse/customer loss; Adrian/Evidentia hardship from broad restrictions; narrow restrictions less burdensome. Need maybe mention "likely success" for TRO: strong on breach/non-solicit/unauthorized access/spoliation; moderate on threatened misappropriation if specific technical choices; weak on broad feature/noncompete. Need maybe include risk matrix? Could be helpful. Need ensure no legal inaccuracies. Let's think about non-solicitation and customer initiated contact. Law says customer's initial contact does not automatically defeat solicitation. Question whether former employee actively encouraged or induced. Adrian's statement likely. But if customer contacted him first, and he responded "you should see what Evidentia is launching..." that's more than passive. Likely breach. Need maybe if he only told factual info, maybe not. Need tailor. Noncompete: request preventing Adrian from working on competing products is void. But can we enjoin him from working on the specific Evidentia feature? If it's a product, that might be a noncompete if unrelated? If tied to trade secret, maybe allowed. Need phrase as use of trade secrets, not work ban. If feature is independent, can't. If specific technical choices secret, can enjoin use. Need maybe not "working on competing products" but "using trade secrets in competing products." Evidentia feature: If Evidentia began general feature 9 months earlier, enjoining release likely fail. But if some technical choices from LexCore, maybe enjoin those specific choices or require modification/delay. Need not entire release. Imaging Evidentia systems: Full imaging likely overbroad. But maybe emergency forensic relief could include imaging Adrian's devices and targeted Evidentia systems. Need propose "logical collection" rather than full image. If need Evidentia's systems, use search terms and repositories. Need maybe court could order imaging of Adrian's laptop/devices and external drive (wiped) and Evidentia's product repository under protocol. Full Evidentia systems no. Spoliation: adverse inference requires intent to deprive. Deliberate secure erase after C&D likely. But he says personal tax/medical and believed LexCore had files. Need maybe court may not infer use, but can infer drive contained relevant evidence and he destroyed. Need maybe sanctions: monetary, exclusion, adverse inference that he copied trade secrets and/or failed to disclose. Need maybe not automatic against Evidentia. Need maybe if Adrian was under Evidentia's control? He was employee; but erasing personal drive maybe not within scope. Need not. Irreparable harm: Need maybe discuss "likelihood" not certainty. Need maybe use one customer as proof of causation. Need maybe if customer moved part business, that harm already occurred; TRO prevents future. But TRO requires future irreparable harm. Need show likely more customers, ongoing use. Need maybe "likely" from solicitation and threat. Strategic risk: Need maybe if unsuccessful, court may set schedule, adverse inferences? At TRO, findings not usually binding, but could be. Need maybe if LexCore files overbroad, court may order protective order, limit discovery, award fees. Need maybe Evidentia can use to argue no misappropriation, file declaratory judgment? Need maybe customers see LexCore as aggressive. Need mitigate. Need maybe final answer with "Bottom line". Let's consider potential alternative: Maybe LexCore should not seek TRO immediately because broad application likely fail and better to preserve via expedited discovery. But facts include immediate risk: Adrian wiped drive, unauthorized downloads, customer moved, feature similar. Need likely court would grant narrow TRO. Need recommend immediate narrow TRO. But assignment asks "Whether LexCore should seek a temporary restraining order immediately or pursue a narrower course." We can say: Seek immediate TRO only if it can be narrowed; otherwise narrower course. Need maybe "I would file immediately for a narrow TRO, but not the four broad restraints." Need maybe discuss "most defensible scope of temporary relief, forensic examination, expedited discovery, and settlement" maybe as recommendations. Let's maybe produce final as a legal memorandum. Use headings and bullet points. Need be thorough but not overly verbose? Desired oververbosity 9, so detailed. Potential final structure: **MEMORANDUM** To: LexCore Litigation Team From: Counsel Re: Adrian/Evidentia – Emergency relief and merits **1. Executive conclusions** - Strongest trade secrets: eval datasets/experiments, next-release details, pricing, customer analytics, annotated customer list. - Protections likely reasonable for those; roadmap weaker. - Misappropriation: initial copying likely breach/misappropriation as to trade secrets; 5:08 unauthorized; no direct use yet; threatened use possible only if specific technical choices. - Non-solicit likely breach as to material-contact customer. - Spoliation strong. - Overbroad requests likely fail. - Seek immediate narrow TRO: preservation, no solicitation, no use of identified secrets, targeted forensics; not noncompete/feature ban/full imaging/all customers. Use expedited discovery and settlement. **2. Trade secret analysis** Table with categories, likely? why. Need include public/nontrade secret. **3. Reasonableness** - Positive/negative, conclusion. **4. Claims analysis** Maybe subheadings. **5. Initial copying and 5:08 downloads** - significance. **6. Evidentia development and clean room** - evidence effect. **7. Wiping drive** - spoliation. **8. Irreparable harm** - likely. **9. Overbreadth of requested relief** - table. **10. Defenses** - Adrian/Evidentia. **11. Strategic risk** - unsuccessful TRO. **12. Defensible scope** - TRO/PI, forensics, discovery, settlement. **13. Recommendation: TRO immediately?** - yes, narrow; fallback. Need maybe include "proposed narrow order" bullet. Let's think about any hidden issue: "Adrian says he routinely copied files to work from home because LexCore’s remote connection was unreliable. The company permitted remote work but prohibited use of unapproved external storage." If he routinely copied, maybe LexCore tolerated? But prohibited unapproved external. If remote unreliable, maybe copying to personal drive was work-around. But 80GB to encrypted drive two days before resignation is not routine? Need maybe if encrypted external drive is unapproved. Need maybe court will find bad faith. Need maybe his defense weak. "Some internal links had no expiration date." This could mean access to links persisted after departure? 5:08 cached credential. Reasonableness? Maybe not. Need maybe if links no expiration, could be accessed after departure without credentials? But cached credential used. Need maybe show LexCore's offboarding not perfect. But access scheduled end 5pm; 8 minutes later. Maybe due technical. Need not fatal. "Former employees’ access was sometimes disabled several days after departure." This could undermine reasonableness and unauthorized access? But Adrian's access scheduled end final day. Cached credential 8 min after. Need maybe if former employees sometimes had access days after, but here 8 min. Need maybe court may view as ordinary. "Approximately 400 LexCore employees could access the product roadmap." If company has 400 employees? It says approximately 400 LexCore employees could access. Maybe total employees? If so, roadmap widely known internally. Trade secret? If all employees, maybe not "not generally known" within company? But trade secret can be known to many inside if not public. However if every employee, economic value may be diminished. Need maybe roadmap less strong. "The evaluation datasets were limited to 32 employees. Customer usage and renewal data were limited to approximately 70 employees." Strong. "Documents were inconsistently labeled." Could undermine reasonable measures. Need maybe court may still find reasonable if other measures. "Adrian signed confidentiality and twelve-month customer non-solicitation agreements. He did not sign a noncompetition agreement." Good. "Three LexCore customers contacted Adrian after his move. Adrian responded to each." Need maybe if non-solicit only customers with material contact. Did he have material contact? As product director likely. Need maybe need to prove. Need maybe customer usage data limited to 70; if he had access, maybe material contact? Need identify. "Told one customer: ... That customer later moved part of its business to Evidentia." Strong. "Six weeks after Adrian joined, Evidentia announced a feature similar to one on LexCore’s confidential roadmap. Evidentia has produced development records showing it began work on the general feature nine months earlier." If announced six weeks after join, nine months earlier means about 7.5 months before join. Strong independent. "Several technical choices in its final product resemble experiments reflected in LexCore’s evaluation data." This is key. Need maybe if "resemble" not "identical". Need discovery. Need maybe trade secret of experiments. Need maybe if technical choices are common in field, no. Need compare. "Evidentia states that Adrian has no access to LexCore-derived files and that it established a clean-room protocol. The protocol was adopted two weeks after Adrian started. Adrian became Evidentia’s product lead immediately upon joining." Gap. Need maybe if clean room late, but he could have influenced. Need maybe order to keep clean room and no access to Adrian's work product? Actually clean room usually prevents exposure to trade secrets by having clean team. If Adrian is product lead, he may give requirements. Clean room after two weeks doesn't erase. Need maybe require forensic audit of first two weeks and feature development. "LexCore wants an order preventing Adrian from working on competing products, barring release of Evidentia’s feature, imaging Evidentia’s systems, and prohibiting contact with all LexCore customers." All overbroad. Need maybe discuss "emergency forensic relief must be proportionate. A court should avoid unnecessarily exposing the new employer’s legitimate confidential information." So full imaging of Evidentia systems likely fails. Need targeted. Need maybe discuss "Destruction of relevant evidence after a preservation duty arises may support sanctions. An adverse inference requires intent to deprive." Need maybe wiping after C&D. Need maybe if he erased because personal records, but secure erase entire drive. Need maybe intent to deprive? Could argue he intended to destroy personal records, not company evidence, but also knew C&D and company files. Need maybe court may infer. Need maybe not if he reasonably believed LexCore had every file? But still relevant to whether he used/disclosed. Need maybe adverse inference that he copied and retained trade secrets, not necessarily that he used. Need maybe if he believed LexCore had every file, maybe less intent to deprive of company files, but still deprive of proof of external drive. Need maybe sanctions can be less than adverse inference on use. Need maybe think about "misuse of information obtained through valid access is not unauthorized access." This means initial 80GB copy not CFAA. But can still be trade secret misappropriation if improper means? The prompt says copying while technically authorized may still breach contract or confidentiality duties. It doesn't explicitly say trade secret misappropriation. Need be careful: Under the provided law, misappropriation includes acquiring through improper means or using/disclosing without consent when knew duty. If he acquired through valid access but in breach of confidentiality, is that "improper means"? It may be. The prompt likely intends: authorized copy = not unauthorized access but may be breach; misuse of info obtained through valid access is not unauthorized access. So for trade secret, if he had valid access, acquisition might not be improper if no breach? But copying to unapproved storage is breach. Need say likely misappropriation if the copied items are trade secrets and the copying violated policy/duty; otherwise if copying was within authorized work-from-home, maybe only breach, not misappropriation? Need nuance. Maybe we should say: The initial copying is not a clean trade secret misappropriation if the only access was valid and the policy prohibition is unenforced? But policy prohibited unapproved external storage. So improper. Need maybe "likely, but fact-dependent." Need not overstate. Need maybe discuss "use or disclose without consent when person knew or should have known of a duty to maintain secrecy." If he copied for personal retention, is that use? Retention may be use? After departure, retaining trade secrets without consent may be use? Some laws treat retaining as use? Not sure. Could say retention for competitive benefit may be use. But no direct use. Need maybe threat. Need maybe discuss "customer-contact spreadsheet" and non-solicit: If he used spreadsheet to contact customers? The customers contacted him, not he contacted? "Three LexCore customers contacted Adrian after his move. Adrian responded to each." So not using spreadsheet to initiate. But he may know who to target. Still. Need maybe discuss "publicly available court documents enhanced with LexCore’s internal annotations." Are annotations trade secret? If annotations are just legal analysis publicly available? Maybe not. If internal methodology, maybe. Need maybe low priority. Need maybe discuss "public statutes and court rules" no trade secret. Need maybe if copied 80GB, much may be nonsecret. Need TRO should not focus on volume. Need maybe discuss "pricing models" could be used in solicitation? He told customer Evidentia solves workflow, not price. But pricing secret. Need maybe discuss "customer usage statistics and renewal forecasts" could be used to target customers. If he had material contact, likely. Need maybe discuss "feature-ranking experiments" and "internal model-evaluation datasets" likely core. Need maybe Evidentia technical choices resemble. Need focus. Need maybe discuss "product roadmaps" and Evidentia feature similar. But independent development. Need maybe roadmap as to general feature not secret if general feature obvious. But roadmap details maybe. Need maybe discuss "threatened misappropriation" and "inevitable disclosure alone insufficient." Need explicitly say cannot rely on Adrian's role alone. Need concrete evidence: technical choices resemblance, clean-room gap, wipe. But independent records counter. Need maybe need expedited discovery before broad PI. Need maybe discuss "likely success" for TRO: If seeking TRO for no use of eval data, need likely success. We have access, similarity, but independent. Maybe moderate. Need maybe court may require expedited discovery. But TRO can be for preservation and no solicitation where success stronger. Need maybe discuss "irreparable harm" and "likely" for TRO: Customer moved part business, but already occurred; future likely if no order. Need maybe ongoing solicitation and feature. Need maybe if no order, Evidentia may continue using specific technical choices. Need maybe not enough if independent. Need maybe discuss "balance of hardships": Broad order harms Evidentia/Adrian; narrow order less. LexCore's hardship of loss of secret value. Need maybe public interest. Need maybe discuss "settlement" strategically: After spoliation, Adrian may prefer settlement. Evidentia may want to avoid litigation and feature delay. Need maybe use targeted threat: if specific technical choices found, delay/modify. Need maybe offer independent development certification. Need maybe include "what evidence to gather before TRO": - Identify trade secrets with documents, access logs, value. - File transfer logs showing 80GB copy, 5:08 download. - Policy prohibiting external storage, NDA, non-solicit. - Customer quote and business move. - Forensic wipe report. - Evidentia development records (already produced) and technical choices comparison. - Clean-room protocol dates. Need maybe in final. Need maybe discuss "immediate TRO vs narrower course" with decision tree: - If can show concrete threatened use of specific eval data and likely irreparable harm: immediate narrow TRO. - If not: file complaint, seek expedited discovery, preliminary injunction after discovery; still seek emergency preservation/no solicitation. Given facts, recommend immediate narrow TRO with fallback. Need maybe be mindful: We represent LexCore, so advice can be advocate but objective. Need maybe phrase "We should not overclaim." Good. Let's think about possible court outcomes: - TRO: court likely denies broad noncompete and feature ban; may grant preservation and no solicitation; may grant limited no use of identified trade secrets; may allow targeted forensics. Full imaging denied. All customers denied. - PI after discovery: if technical choices match and not independent, enjoin those aspects; if not, no. - Spoliation: adverse inference maybe. Need maybe include "risk that unsuccessful emergency application could damage LexCore strategically" in detail: - Overreaching can lead to court finding no likelihood success on core misappropriation, making future PI harder. - Evidentia can argue clean room and independent development; Adrian can use court's skepticism. - Customers may fear LexCore is overaggressive; may not sign non-solicit? Not relevant. - Cost and delay; feature may launch before full discovery. - If LexCore's trade secrets disclosed in filings, less secrecy? Need protective order. - If court orders no broad relief, Evidentia may publicize win. - Could trigger fee shifting? Maybe if overreaching. Need mention potential. Mitigation: narrow claims, particularize secrets, avoid noncompete, proportionate forensics, settle early. Need maybe discuss "most defensible scope of settlement" perhaps: - Adrian: individual settlement: damages for breach/non-solicit, confidentiality, no admission, release, no further contact with listed customers, maybe buyout of his work? Not noncompete. - Evidentia: no admission, independent development declaration, clean-room audit, no use of identified trade secrets, maybe exclusion of Adrian from specific feature for 6-12 months (contractual, not court noncompete? But if void, maybe settlement consideration okay? Courts may still not enforce as noncompete? But settlement can include agreed restriction supported by consideration? Governing law says noncompetition unrelated to sale void. A settlement restriction might be deemed noncompete and void. Better not rely; use no-use trade secret and clean room. If parties agree Adrian won't work on feature, is that noncompete? It might be void if unrelated. But if consideration for release, maybe enforceable? Safer: no use of trade secrets, not broad work restriction. Could include "Adrian will not participate in the specific feature until audit" as protective order, not settlement? Could be court order. Settlement can include "Evidentia will not use identified trade secrets" and "Adrian will not solicit listed customers." That's allowed. - Maybe damages for customer switch and unauthorized access. - Confidentiality, no publicity, mutual releases. Need maybe discuss "expedited discovery" specifics: - LexCore: file transfer logs, access logs, external drive policy exceptions, work-from-home logs, previous copies. - Adrian: identity of drive, encryption, contents, prior use, why wiped, statements. - Evidentia: development timeline for feature, technical choices, source documents, clean-room protocol, Adrian's tasks, who accessed what, customer communications, whether Adrian influenced, preservation. - Customers: initiation, communications, reason for moving. - Forensic: chain of custody, hash, search terms. Need maybe include deadlines. Need maybe discuss "temporary relief" details: - Duration: TRO 14 days, PI until trial; preserve until case resolution. - Bond: reasonable. - Notice: ex parte? Maybe if TRO ex parte, need affidavit; otherwise noticed. - Contempt: specify. - Reporting: neutral forensic expert report. Need maybe include "what not to seek": - No order that Adrian cannot work at Evidentia or on any competing product. - No order barring Evidentia's entire feature. - No order prohibiting all customer contact. - No order for full imaging of Evidentia. Need maybe discuss "publicly available court documents enhanced with internal annotations" maybe could be trade secret if annotations are nonpublic and valuable. But if public court docs, the underlying is public; only annotations. Need maybe not central. Need maybe discuss "customer usage statistics" if aggregated? If per-customer, valuable. If public? No. Need maybe discuss "pricing models" if based on public data? Maybe still not readily ascertainable. Need maybe discuss "product roadmaps" if known to 400 employees: if 400 is all employees, maybe not secret? Need maybe if all employees, still not public but maybe no reasonable measures? Need maybe say "likely weak; avoid making it centerpiece." Need maybe discuss "evaluation datasets limited to 32" strong. Need maybe "feature-ranking experiments" could be considered know-how. Need maybe if Evidentia technical choices resemble, strong. Need maybe discuss "reasonableness" with "ordinary business confidentiality cannot be established solely by describing information as confidential after a dispute arises." Need maybe LexCore's labels inconsistent, but had agreements/training. Need maybe not rely on post-dispute "confidential" stamps. Need maybe show pre-existing access controls. Need maybe discuss "misappropriation" if Adrian copied public statutes: no. Need maybe volume 80GB includes nonsecrets; don't use volume as sole proof. Need maybe discuss "5:08 p.m. cached credential" maybe LexCore's failure to revoke immediately? Access scheduled end 5pm; 8 min later. Could be technical. Need maybe if cached credential used, maybe not knowing. But under statute unauthorized. Need maybe if no damages, limited. Need maybe supports "access after credentials revoked is unauthorized" and could be used for improper means. Need maybe if automated sync, Adrian may argue no intent; but even negligent retention of device after revocation? Need maybe. Need maybe discuss "Adrian says automated synchronization process caused downloads and that he did not know his credentials had been revoked." Need evaluate: If automatic, why still connected 8 min after? Could be. But 14 files concerning next release; if automatic, likely synced entire laptop? It says fourteen files concerning next product release, not all. Could indicate targeted? But cached credential used to download fourteen files. Need maybe if automated sync, would download files changed? Could be. Need maybe forensic logs can show whether manual/automatic, time, user action. Need discovery. For TRO, maybe not decisive. Need maybe discuss "Evidentia's clean-room protocol adopted two weeks after Adrian started" and "Adrian became product lead immediately". If he had no files, but as product lead could direct based on memory. Clean room after two weeks may not prevent prior influence. Need maybe require audit of first two weeks and feature decisions. Need maybe discuss "Several technical choices in its final product resemble experiments reflected in LexCore’s evaluation data." Need maybe if resemblance is due to Adrian's general skill or public literature, defense. Need need compare. Need maybe if choices are not in Evidentia preexisting records, stronger. Need maybe if they are in preexisting records, no. Need maybe discuss "Evidentia has produced development records showing it began work on the general feature nine months earlier." This is strong but maybe not all technical choices. Need maybe "general feature" vs specific technical implementation. Need maybe independent development of general idea doesn't preclude use of secret details. Need maybe court will require specific. Need maybe discuss "threatened misappropriation" if Evidentia feature already announced. Is there likely use? Already announced, but maybe not released. Need TRO to prevent release? If independent, no. If specific choices, maybe prevent release of those aspects. Need maybe if feature already announced, harm maybe imminent. Need maybe expedited. Need maybe discuss "barring release of Evidentia's feature" maybe if feature already announced, enjoin release could be overbroad and maybe moot? Need maybe if not yet released. Need maybe if independent, no. Need maybe discuss "imaging Evidentia's systems" maybe if Evidentia has legitimate confidential info; need proportionate. Need maybe target Adrian's devices and relevant repos. Need maybe if Evidentia systems necessary, use neutral protocol. Need maybe discuss "prohibiting contact with all LexCore customers" maybe overbroad and also may violate customers' free choice. Need no solicitation, not no contact. Need maybe discuss "strongest defenses" maybe include "clean room" but late; "independent development"; "no unauthorized access for initial"; "automated sync"; "personal files"; "customer initiated"; "no trade secret". Need maybe for Evidentia, "no agency" for Adrian's wiping? Need maybe. Need maybe discuss "risk that unsuccessful emergency application could damage LexCore strategically" maybe also "if LexCore fails to prove trade secrets, Evidentia can use ruling to argue no secrecy, undermining future claims." Need maybe. Need maybe discuss "most defensible scope of temporary relief" maybe include "particularity annex" and "narrowly tailored to protect trade secrets, not prevent competition." Need maybe discuss "whether LexCore should seek TRO immediately" maybe "Yes, but only with a carefully scoped application; if not, expedited discovery." Need maybe "do not wait because of spoliation and ongoing solicitation." Need maybe "do not file broad application." Let's maybe draft final in a professional tone. Potential final: ``` MEMORANDUM ... I. Bottom line ... II. Trade secret categories Table... III. Reasonableness ... IV. Claims A. Misappropriation B. Breach confidentiality C. Customer non-solicit D. Unauthorized access E. Threatened misappropriation V. Copying and 5:08 VI. Evidentia development/clean room VII. Wiping VIII. Irreparable harm IX. Overbroad relief X. Defenses XI. Strategic risk XII. Defensible scope XIII. Recommendation ``` Need maybe include "Conclusion" at end. Let's ensure we answer "Which categories of information likely qualify as trade secrets." We'll table: - Public statutes/court rules: no. - Product roadmaps: possible but weak; next-release subset likely. - Customer usage stats: likely. - Pricing models: likely. - Internal model-evaluation datasets: likely strong. - Feature-ranking experiments: likely strong. - Customer renewal forecasts: likely. - Customer-contact spreadsheet: likely if compiled with nonpublic data; otherwise no. - Public court docs enhanced with annotations: annotations maybe, underlying no. Need maybe say "approximately 80GB volume not itself proof; must identify specific secrets." Need maybe "reasonableness" with conclusion: likely reasonable for eval/customer/pricing/next release; roadmap weaker due 400 access and labeling. Need maybe "not perfect but sufficient." Need maybe "misappropriation, threatened misappropriation, breach, customer solicitation, unauthorized-access claims" all. Need maybe for each: likely/unlikely. Let's think about legal standard for TRO: likely success, irreparable harm, balance, public interest. Need maybe evaluate each requested relief against standard. Could make table: - No competing products: noncompete void, likely fail. - Bar feature: overbroad, likely fail unless specific. - Imaging Evidentia: likely fail if full; targeted maybe. - No all customers: fail; listed solicitation maybe. Need maybe "most defensible scope" maybe propose order language: ``` 1. Adrian and Evidentia shall not use or disclose Annex A trade secrets in connection with any product, marketing, pricing, or customer solicitation. 2. Adrian shall not solicit any customer listed in Annex B for 12 months; shall not use Annex C customer data. 3. Evidentia shall maintain clean room; Adrian shall not participate in the development of Feature X or any feature incorporating Annex A until independent-development audit. 4. Preserve and produce evidence; no deletion. 5. Forensic protocol as described. ``` Need maybe not "Feature X" if independent? Could say "the specific feature(s) at issue to the extent they incorporate alleged trade secrets." Need maybe if broad, no. Need maybe "settlement" propose: - If Evidentia independent: settle Adrian's claims, damages, non-solicit, no use; release Evidentia feature. - If specific choices: negotiate license/delay/modify; Adrian excluded from specific feature; damages. - Use spoliation and non-solicit as leverage. Need maybe "immediate TRO" recommendation: "File now for narrow TRO, with ex parte if necessary for preservation, but be prepared to accept targeted forensics and expedited discovery. If the court requires more proof of threatened misappropriation, limit TRO to preservation and no solicitation, then move for PI after discovery." Need maybe "Do not seek the broad four-part order." Need maybe mention "bond" and "notice". Not necessary but good. Need maybe mention "protective order" for trade secrets and Evidentia confidential info. Let's consider if there is any issue with "customer non-solicitation restriction is enforceable only as to customers with whom employee had material contact and only to extent reasonably necessary to protect legitimate relationships." Need maybe 12 months is given enforceable? It says a twelve-month customer non-solicitation restriction is enforceable only as to ... So 12 months okay if limited. Need maybe "all LexCore customers" overbroad. Need maybe "prohibiting contact" overbroad; should be no solicitation. Need maybe if customers initiated, he can respond but not induce. Could order require him to cease solicitation, not all contact. Maybe if risk of further inducement, no direct contact with listed customers except through LexCore? But that might be overbroad. Better: no solicitation; if contacted, may answer factual questions but not promote Evidentia or induce move. Court could monitor. Need maybe propose. Need maybe "material contact" definition: substantial responsibility for account, regular communications, knowledge of customer usage/renewal, participated in demos/proposals. Need maybe need discovery. Need maybe "initial contact does not automatically defeat solicitation." Need explicitly address: Even though customers contacted Adrian, his statement likely induced. Need maybe for other customers, need evidence. Need maybe "noncompetition restriction unrelated to sale of business is void." Need explicitly say request to prevent Adrian from working on competing products is noncompete and void. Need maybe even if tied to trade secret? The law says noncompetition restriction unrelated to sale void. So cannot. But injunction against trade secret use is not noncompete. Need phrase. Need maybe "copying information while technically authorized may still breach contract or confidentiality duties." Need explicitly use for initial copy. Need maybe "Under applicable computer-access statute, however, misuse of information obtained through valid access is not unauthorized access. Access after credentials are revoked is unauthorized." Need use. Need maybe "Threatened misappropriation requires concrete evidence ... inevitable disclosure alone insufficient." Need use. Need maybe "Emergency forensic relief must be proportionate..." Need use. Need maybe "Destruction ... adverse inference requires intent to deprive." Need use. Need maybe "Reasonable measures ... perfect security unnecessary, but ordinary business confidentiality cannot be established solely by describing information as confidential after dispute arises." Need use. Need maybe "Information is trade secret when ..." Need use. Need maybe "Misappropriation includes acquiring ... or using/disclosing ..." Need use. Need maybe "TRO requires likely success, irreparable harm, balance, public interest." Need use. Now let's think about potential counterarguments and how to address. Adrian's defense: He routinely copied files to work from home. If LexCore permitted remote work and remote connection unreliable, copying to personal drive may be within scope? But policy prohibited unapproved external storage. Need maybe if he had no alternative and company knew? Not stated. Need maybe if he encrypted drive, suggests awareness of confidentiality. Need maybe 80GB two days before resignation. Need maybe court may view as pretext. Need maybe if he only copied files he had access to for work, no improper access. But retention after departure is issue. Need maybe if he wiped, no use. Need maybe. Evidentia defense: clean room. But adopted two weeks after. Need maybe if Adrian product lead, clean room not enough if he influenced before. Need maybe require audit. Spoliation: He says personal tax/medical. But secure erasure entire drive. Need maybe if he believed LexCore had every file, maybe no intent to deprive of company files. But he may have intended to deprive of proof of copy. Need maybe adverse inference not automatic. Need maybe if no proof of intent, court may only preclude him from testifying? Need maybe. Irreparable harm: Customer moved part business; damages maybe. Need maybe if one customer, quantifiable. Need maybe ongoing. Need maybe if Evidentia independent, no irreparable. Need maybe. Overbroad: Need maybe if court denies broad, LexCore may still get narrow. Strategic risk: Need maybe if TRO fails, Evidentia may file declaratory judgment? Not mentioned. Could use to pressure. Need maybe. Let's maybe include "evidentiary gaps" for LexCore: - Need particularized trade secret list. - Need prove material contact with customers. - Need prove specific technical choices not in Evidentia preexisting records. - Need prove Adrian's use or likely use, not just access. - Need prove intent to deprive for adverse inference. - Need prove irreparable harm. Need maybe in recommendations. Need maybe "strongest claims" ranking: 1. Customer non-solicit (quote) - likely. 2. Breach confidentiality/unauthorized use of unapproved storage - likely. 3. Unauthorized access 5:08 - likely but limited. 4. Spoliation - strong. 5. Trade secret misappropriation/threat as to eval data/next release - possible, needs discovery. 6. General roadmap/feature - weak due independent. Need maybe "most defensible scope" ranking: - TRO: preserve, no solicitation of listed customers, no use of identified secrets, targeted forensics. - PI: after discovery, enjoin specific aspects. - Settlement: as above. Need maybe final answer long. Let's start drafting mentally. Begin: **MEMORANDUM** **To:** LexCore Litigation Team **From:** Counsel **Re:** Adrian/Evidentia – trade secret, non-solicitation, and emergency relief **I. Executive summary** ... (bullet points) Then detailed. Need maybe use "likely" not absolute. Let's draft sections in detail. ### I. Executive summary - LexCore has credible claims, but must narrow. Strongest: breach of confidentiality, customer non-solicit, unauthorized access at 5:08, spoliation, and threatened misappropriation of specific eval data/next-release details. Weaker: broad roadmap, public materials, entire feature, noncompete, all-customer ban, full imaging. - Protections: reasonable for tightly restricted data; roadmap weaker. - Initial copying: not unauthorized access but likely breach/misappropriation if trade secrets and policy violated. 5:08: unauthorized access, strong but limited. - Evidentia's 9-month development record strong independent defense to general feature; technical choices resemblance creates possible specific claim. Clean-room late weak. - Wiping: spoliation; adverse inference possible. - Irreparable harm: possible if targeted; broad feature ban hard. - Recommendation: immediate narrow TRO or expedited hearing; not broad. Seek preservation, no solicitation of listed customers, no use/disclosure of identified secrets, targeted forensics. Use expedited discovery. Settle if independent development confirmed. ### II. Trade secret categories Table. Need maybe include "particularity". Let's write table: | Category | Likely trade secret? | Reasoning | ... Need maybe not too wide? But okay. Public statutes/court rules: No. Public court docs: No underlying; annotations maybe if nonpublic analytical value. Product roadmaps: Possible; general roadmap weak due 400 access; next-release details likely if not generally known. Customer usage stats: likely. Pricing models: likely. Internal model-evaluation datasets: likely strong. Feature-ranking experiments: likely strong. Customer renewal forecasts: likely. Customer-contact spreadsheet: likely if compiled with nonpublic data; if simple public list, no. Need maybe "80GB volume not per se." Good. ### III. Reasonableness - Pre-existing NDA, training, passwords, policy, limited access. Good. - Deficiencies: inconsistent labels, no expiration, delayed deprovisioning, 400 roadmap. But perfect not required. For eval/customer/pricing/next-release, likely reasonable. For broad roadmap, may be challenged. Need not rely solely on after-dispute labels. Need maybe show access controls and value. ### IV. Claims analysis #### A. Misappropriation and threatened misappropriation - Acquisition: copying to encrypted external drive in violation of policy; if trade secrets, misappropriation. But if routine and authorized, maybe less. Need identify. - Use/disclosure: no direct evidence yet. Threat: specific technical choices, clean-room gap, wipe, solicitation. But independent development weakens. Inevitable disclosure insufficient. Need concrete: similarity of technical choices to eval data, next-release unauthorized downloads, product lead role. Need discovery. #### B. Breach confidentiality - Signed agreement; copying/retention/wiping. Likely. Even if trade secret fails. #### C. Customer non-solicitation - Enforceable as to material-contact customers. As product director likely. Customer initiated not defense. Quote = active inducement. Likely breach as to that customer; need evidence for others. Tailor. #### D. Unauthorized access - Initial authorized: no CFAA claim. 5:08: unauthorized. Automated defense; but access after revocation unauthorized. Limited to 14 files. Supports improper means. #### E. Spoliation (maybe separate) - Wiping after C&D; deliberate secure erase; preservation duty; sanctions/adverse inference if intent to deprive. Strong. Undermines credibility. Not direct proof of use. Evidentia not automatically liable. ### V. Significance of initial copying and 5:08 downloads - Initial: suspicious volume/timing, encrypted, prohibited; supports breach/threat; work-from-home defense weak; not unauthorized access. - 5:08: post-revocation, next-release, unauthorized; automated defense; small but targeted; supports urgency and threat. ### VI. Evidentia's preexisting work and clean-room - 9-month records: strong independent for general feature; defeats broad feature injunction. - Technical choices: if match secret eval data and not in preexisting records, possible specific misappropriation. Need compare. - Clean-room: late, first two weeks gap, product lead; weak as to early influence. Need audit. ### VII. Wiping drive - Spoliation; secure erase after C&D; intent to deprive likely; adverse inference possible; personal-file defense; if believed LexCore had files, still relevant. Sanctions. Strategic leverage. ### VIII. Irreparable harm - Need likely. Strengths: loss of customer, trade secret value, ongoing solicitation, unauthorized next-release, feature launch. Weakness: independent development, quantifiable damages. Need show likely continued use and not fully compensable. Targeted relief more defensible. ### IX. Overbroad requested restraints Table: - Prevent Adrian working on competing products: noncompete void, overbroad. - Bar release of feature: overbroad; independent; only specific aspects. - Image Evidentia systems: overbroad; proportionate targeted only. - Prohibit contact with all customers: overbroad; only material-contact solicitation. Need maybe "all fail or require narrowing." ### X. Strongest defenses Adrian and Evidentia. Bullet. ### XI. Strategic risk of unsuccessful emergency application - Credibility, overreach, adverse record, competitor momentum, customer perceptions, cost, protective order, fee risk. Mitigate by narrow. ### XII. Most defensible scope #### A. Temporary relief - Particularized annex. - No use/disclosure of identified trade secrets. - No solicitation of listed material-contact customers for 12 months; no use of confidential customer data; if contacted, no inducement. - Clean-room/audit: Adrian not to influence specific feature(s) incorporating alleged secrets until audit; Evidentia maintain clean room. - Preservation/litigation hold. - Targeted forensics protocol. - No broad noncompete/feature ban/all customers/full imaging. #### B. Forensic examination - Neutral expert, two-tier confidentiality, limited search, hash, chain, no full Evidentia imaging, targeted repos/Adrian devices. #### C. Expedited discovery - Lists. #### D. Settlement - Options. ### XIII. Should LexCore seek TRO immediately? - Yes, narrow immediate TRO due urgency (spoliation, solicitation, unauthorized access, feature). But if cannot show concrete threatened use, limit to preservation/no solicitation and expedited discovery. Do not file broad. Need maybe "file now". Need maybe include "proposed narrow TRO" maybe in XII or XIII. Let's think if any issue with "Adrian became Evidentia’s product lead immediately upon joining." Could support threatened misappropriation because he can shape product. But inevitable disclosure insufficient. Need concrete. Need maybe discuss "Evidentia states Adrian has no access to LexCore-derived files." If true, but he wiped drive, can't prove. Need forensic of Evidentia devices to verify. Need maybe if no access, clean room. Need maybe TRO to preserve. Need maybe discuss "Several technical choices in its final product resemble experiments reflected in LexCore’s evaluation data." Need maybe if technical choices are not publicly known and in Evidentia preexisting records? Need compare. Need maybe "resemblance" can be explained by common algorithms, public papers, Adrian's general skill. Need not overstate. Need maybe discuss "feature similar to one on LexCore's confidential roadmap." General feature idea may be independent; not secret. Need maybe roadmap details like timing, priority, specific technical approach secret. Need focus. Need maybe discuss "customer usage statistics" and "renewal forecasts" if used in customer solicitation: He told customer Evidentia solves workflow problem; not necessarily using data. But he likely knows which customers likely to churn. Need maybe. Need maybe discuss "pricing models" not directly in facts of customer move. But copied. Need preserve. Need maybe discuss "public court documents enhanced with internal annotations" maybe if annotations are trade secret, but not central. Need maybe discuss "Adrian says he believed LexCore already possessed every company file." If true, LexCore's original files still exist; but external drive evidence destroyed. Need maybe if LexCore can prove original files, less harm. But still spoliation. Need maybe if he believed company had every file, maybe no intent to deprive of company data, but still relevant to whether he intended to hide evidence. Need maybe. Need maybe discuss "forensic report indicates deliberately wiped using secure-erasure software." Need maybe ask court to preclude his personal-file explanation? Maybe adverse inference. Need maybe if secure erase, metadata may show. Need maybe. Need maybe discuss "12-month customer non-solicitation" enforceable only material contact. Need maybe if he had no material contact with three customers? As product director, maybe. Need verify. Need maybe if customer contact spreadsheet includes them, maybe. Need maybe not assume. Need maybe discuss "customer’s initial contact does not automatically defeat solicitation." Need explicitly: The fact customers contacted him first does not save him if he induced. His quote likely. Need maybe discuss "noncompetition restriction unrelated to sale of business is void." Need explicitly: request to prevent Adrian from working on competing products is likely void; even if he signed no noncompete, court won't impose de facto. Need maybe if tied to trade secret, phrase as no use. Need maybe discuss "temporary restraining order requires likely success, likely irreparable harm, favorable balance, public interest." Need maybe evaluate: likely success for narrow no solicitation/preservation strong; for threatened use moderate; irreparable harm moderate; balance favors narrow; public interest favors both competition and trade secret protection. Broad fails. Need maybe discuss "emergency forensic relief must be proportionate." Need maybe full imaging fails; targeted passes. Need maybe discuss "destruction ... adverse inference requires intent to deprive." Need maybe deliberate secure erase after C&D likely intent; but need evidence. Now let's think about how to phrase "most defensible scope of temporary relief" with legal precision: **Temporary relief order**: 1. **No use or disclosure**: Adrian shall not, directly or indirectly, use or disclose any information in Annex A (identified trade secrets) in the development, design, marketing, pricing, sale, or customer solicitation for any product or service of Evidentia or any competitor. This is not a noncompete. 2. **Customer non-solicitation**: Adrian shall not solicit any customer listed in Annex B (customers with whom he had material contact) for 12 months. He may not use Annex C confidential customer data. If a customer contacts him, he may respond factually but shall not encourage movement of business; he shall notify LexCore within 24 hours? Maybe too intrusive. Could require no solicitation only. Maybe "shall not make statements promoting Evidentia's competitive advantage over LexCore to listed customers." Need maybe. 3. **Clean-room and audit**: Evidentia shall continue clean-room protocol. Adrian shall not participate in the development or decision-making for the specific feature(s) at issue or any feature that incorporates Annex A until a forensic/independent-development audit determines no misappropriation. This is tailored, not general noncompete. But if feature independent, maybe after audit release. 4. **Preservation**: Preserve all devices, external drives, logs, emails, chats, development records, meeting notes, design docs, customer communications. No deletion. Evidentia and Adrian to certify litigation hold. 5. **Forensic protocol**: As below. 6. **Security/bond**: Reasonable bond. 7. **Contempt**: Sanctions. Need maybe not "bar release of feature" but "no use of specific trade secret aspects." If audit shows use, maybe enjoin those aspects. **Forensic protocol**: - Parties designate neutral forensic expert. - Scope: Adrian's laptop, any remaining external drive remnants, mobile devices, cloud accounts; Evidentia's relevant product repositories, design docs, Jira/Confluence, code commits, design review materials, communications between Adrian and feature team, customer communications. Search terms: LexCore product names, feature names, file names, hashes, technical terms from eval data, customer names from Annex B, dates from hire to feature announcement. - Confidentiality: Forensic examiner and counsel only; two-tier; no general distribution. - Method: targeted logical collection, hash verification, privilege review, sampling, no full imaging of Evidentia systems. If necessary, image only specific devices under protocol. - Timeline: 14-21 days for forensic report. **Expedited discovery**: - Document production: LexCore access logs, file transfer logs, offboarding logs, policy, NDA, non-solicit; Adrian's statements; Evidentia development records; clean-room protocol; customer communications; preservation logs. - Depositions: Adrian (copying, drive, wipe, 5:08, customer contacts, Evidentia role), Evidentia product lead/CTO (feature development, technical choices, clean room), maybe customer. - Interrogatories? Maybe. - Comparison: technical choices vs eval data and preexisting records. **Settlement**: - If evidence independent: settle Adrian claims: damages, non-solicit, confidentiality, release, no admission; Evidentia continues feature with clean-room certification. - If specific use: negotiate license or modification/delay of specific aspects; Adrian excluded from specific feature; damages; mutual releases; confidentiality. - Use spoliation and customer harm as leverage. Avoid noncompete. **TRO immediately?**: - Yes, narrow. Because: wipe after C&D, unauthorized access, ongoing solicitation, feature launch, risk of further harm. But if court not persuaded on threatened use, seek preservation/no solicitation and expedited discovery. Do not seek broad. Need maybe "file immediately with particularized trade secret annex and evidence of quote, logs, wipe, development records." Need maybe include "fallback" if TRO denied: move for PI after expedited discovery; seek damages; continue customer relationships. Need maybe include "what to avoid in filing": - Don't call it noncompete. - Don't seek all customers. - Don't seek full imaging. - Don't rely on inevitable disclosure. - Don't overstate roadmap. - Don't request feature ban without specific trade secret nexus. Need maybe include "evidentiary gaps to fix before TRO": - Particularize trade secrets. - Identify material-contact customers. - Show technical choices not in Evidentia preexisting records. - Show intent to deprive for adverse inference. - Show irreparable harm. Need maybe include "risk matrix" maybe not necessary but could be helpful. Let's think about potential legal nuance: "Misappropriation includes acquiring a trade secret through improper means or using or disclosing it without consent when the person knew or should have known of a duty to maintain secrecy." If Adrian copied files while employed, he knew duty. Copying to personal drive may be "acquiring" outside scope? He already had access; acquiring copy maybe. If policy prohibited, improper. Need maybe if he had a right to work from home, copying to external drive for work could be consented? But policy prohibited unapproved storage. Need maybe no consent. Need likely. Need maybe "copying information while technically authorized may still breach contract or confidentiality duties." This supports breach, but for misappropriation maybe if he used without consent after departure. Need maybe retention is use? Could say "retention for possible competitive use after departure is at least threatened use." Need careful. Need maybe "access after credentials are revoked is unauthorized." 5:08 download. Need maybe if cached credential, was access by Adrian or automatic? Under statute, if automatic process used credential, maybe user responsible? Need maybe if he left device connected, negligent. Need maybe. Need maybe "Threatened misappropriation requires concrete evidence of likely use or disclosure." Need maybe if he wiped drive, no disclosure. But Evidentia feature similar. Need maybe concrete? Maybe not enough without discovery. Need maybe TRO for threatened misappropriation should be limited to specific technical choices where similarity is concrete. Need maybe if not, wait. Need maybe "inevitable disclosure alone insufficient." Need explicitly say don't argue Adrian "knows too much." Need argue specific evidence. Need maybe "A customer’s initial contact does not automatically defeat solicitation." Need explicitly. Need maybe "A noncompetition restriction unrelated to sale of business is void." Need explicitly. Need maybe "Emergency forensic relief must be proportionate." Need explicitly. Need maybe "Destruction ... adverse inference requires intent to deprive." Need explicitly. Let's maybe write final with enough detail. Need maybe not too repetitive but thorough. Potential final text (draft): ``` MEMORANDUM ... 1. Bottom line LexCore has a credible case on narrow grounds ... The four requested restraints are overbroad ... Seek immediate narrow TRO ... ``` Need maybe use "we" as LexCore counsel. Let's ensure final answer includes all assignment bullets. It will. Let's think about any possible hidden expectation: The question is from a legal reasoning exam maybe wants analysis, not just advice. Need maybe answer as if analyzing each issue. Could be in exam style. Need maybe include "conclusion" for each. Need maybe not just recommendations. But assignment asks analyze many points. We can combine. Need maybe maybe they expect "LexCore should not seek TRO immediately because broad application overbroad and may fail; instead pursue expedited discovery and narrower preliminary injunction." Need decide. Let's weigh. If we recommend immediate narrow TRO, is it defensible? TRO requires likely success. Do we have likely success on narrow no use of trade secrets? We have copied trade secrets, unauthorized 5:08, feature similar, technical choices resemble, clean-room late, wipe. But Evidentia independent development 9 months. For TRO, need likely success on threatened misappropriation. The independent development may make likely success hard for feature. But no use claim maybe: Adrian copied eval data and wiped; no proof he used. Threatened use maybe speculative. Court may deny trade secret TRO. But no solicitation likely success. Preservation likely. So immediate TRO for no solicitation/preservation is defensible. For product-related, maybe need expedited discovery first. The question asks "Whether LexCore should seek a temporary restraining order immediately or pursue a narrower course." Maybe answer: Seek immediate TRO only for narrow preservation/no solicitation; for product/feature, pursue expedited discovery and PI. Or if strong concrete evidence of specific technical choices, immediate TRO for no use. Need nuanced. Given Evidentia produced development records 9 months earlier, likely success on misappropriation of general feature is weak. Need not seek TRO to bar feature. But if several technical choices resemble eval data, maybe need expedited discovery to compare. TRO may be premature. However urgency: Adrian wiped drive; need preserve. Need immediate TRO for preservation and forensic protocol. That is narrower course. So maybe recommendation: immediate narrow TRO (preservation/no solicitation) but not broad product/feature; if need product use, maybe wait for expedited discovery. Need phrase. Need maybe "most defensible scope of temporary relief" includes "no use of identified trade secrets" but if likely success weak, maybe court may grant after PI. But TRO can include no use if threatened. Need maybe propose. Need maybe "risk that unsuccessful emergency application could damage LexCore strategically" suggests maybe if broad TRO fails, bad. So maybe better to pursue narrower course initially. But if no immediate action, Adrian may continue soliciting, destroy more evidence. Need balance. I think best: "File immediately for a narrow TRO, but do not file the broad application. If the concrete showing of threatened use of the evaluation data is not yet sufficient, limit the TRO to preservation, no further solicitation, and a targeted forensic protocol; use expedited discovery to support a later PI on product-related relief." This answers both. Need maybe maybe "temporary restraining order immediately or narrower course" could mean "Should LexCore seek TRO immediately or pursue narrower course?" We can say "Seek immediate TRO if and only if narrowed; otherwise narrower course." Good. Need maybe include "If the court is likely to deny due to independent development, a narrower expedited discovery path may be less risky. But given spoliation and solicitation, some emergency relief is justified." Good. Let's think about "irreparable harm" for TRO. For preservation/no solicitation, likely irreparable? Solicitation can cause loss of customers, maybe. Preservation prevents loss of evidence, maybe. Product use? Need. Need maybe court may find damages adequate for one customer. But ongoing. Need maybe. Need maybe "likely success" for non-solicit: strong if material contact. Need maybe prove. For preservation: high. For forensic: high if spoliation risk. Need maybe "balance of hardships" for no solicitation: Adrian can still work, just not solicit listed customers. Favorable. For no use of trade secrets: can still work independently. Favorable. For clean-room: manageable. For full imaging: not favorable. Need maybe "public interest" favors preventing misappropriation but also competition. Narrow. Need maybe include "security bond" maybe not central. Need maybe final answer with "caveat: facts as given; need verify access, material contact, technical comparison." Good. Let's maybe start writing final in a polished way. Potential final: ``` **Memorandum** **Re: Adrian / Evidentia** **I. Conclusion** LexCore should pursue immediate but narrow emergency relief. The strongest grounds are ... The four requested restraints are overbroad ... ``` Need maybe include "trade secret categories likely qualify" as table. Let's draft table in text. Table maybe: - Public statutes/court rules: no. - Product roadmaps: possible; next-release subset likely; general roadmap weak. - Customer usage stats: likely. - Pricing models: likely. - Internal model-evaluation datasets: likely and strongest. - Feature-ranking experiments: likely and strongest. - Customer renewal forecasts: likely. - Customer-contact spreadsheet: likely if compiled with nonpublic data. - Public court docs enhanced with annotations: annotations maybe. Need maybe "approx 400 employees access roadmap" in reasonableness. Let's draft each section in final. Need ensure not too long? Desired oververbosity 9, can be long. But final should be manageable. Maybe 4000-6000 words? We have token budget. Need be detailed but not insane. Let's aim ~5000-7000 words? We can produce ~4500-5500. Need fit. Let's write final now in my head, then final. Detailed content: **I. Executive summary** (5 bullets) **II. Trade secret identification** - Need particularity. Table. - Focus on eval data/experiments, next-release, pricing, customer analytics. Roadmap weak. Public no. **III. Reasonableness** - Positive/negative. Conclusion. **IV. Claims** A. Misappropriation/threat B. Breach confidentiality C. Non-solicit D. Unauthorized access E. Spoliation **V. Significance of copying and 5:08** **VI. Evidentia development/clean-room** **VII. Wiping drive** **VIII. Irreparable harm** **IX. Overbreadth** **X. Defenses** **XI. Strategic risk** **XII. Defensible scope** (relief, forensics, discovery, settlement) **XIII. Recommendation on TRO** Let's ensure each assignment bullet is explicitly addressed. Maybe use headings matching assignment: 1. Trade secret categories 2. Reasonableness 3. Claims 4. Significance copying/5:08 5. Evidentia development/clean-room 6. Wiping 7. Irreparable harm 8. Overbroad restraints 9. Defenses 10. Strategic risk 11. Defensible scope 12. TRO immediately? Good. Let's draft with legal reasoning. Need maybe mention "we should not rely on post-dispute labels." In reasonableness. Need maybe mention "ordinary business confidentiality cannot be established solely by describing information as confidential after dispute arises." Use. Need maybe mention "perfect security unnecessary." Use. Need maybe mention "threatened misappropriation requires concrete evidence; inevitable disclosure insufficient." Use. Need maybe mention "customer initial contact does not automatically defeat solicitation." Use. Need maybe mention "noncompete void." Use. Need maybe mention "emergency forensic relief proportionate." Use. Need maybe mention "adverse inference requires intent to deprive." Use. Let's think about possible wording for "misappropriation" initial copy: "The 80GB copy is not an unauthorized-access violation under the computer-access statute because Adrian had valid access. But it is not automatically innocuous. He copied it to an encrypted external drive that company policy prohibited, two days before resigning, in substantial volume, and it included at least some information that was not public. If the copied items qualify as trade secrets, the copying may be acquisition through improper means or at least a breach of the duty of confidence. The work-from-home explanation is credible only if there is a pattern of similar transfers for work; the timing and volume make it weak." Good. For 5:08: "The 5:08 downloads are different: access after revocation is unauthorized. The fact that a cached credential was used and Adrian claims an automated sync is a factual defense, but the statute draws the line at revocation. Even if the claim succeeds on knowledge or causation, the episode supports urgency and a possible misappropriation claim as to the 14 next-release files." Good. For Evidentia: "The nine-month development records are LexCore's biggest obstacle to a product injunction. They likely show independent development of the general feature. But they do not automatically answer whether the specific technical choices that resemble LexCore's evaluation experiments were independently derived. If those choices appear only after Adrian joined and match the secret data, LexCore has a concrete threat claim as to those choices. If they appear in the nine-month records, the claim is weak." Good. For wiping: "After C&D, preservation duty. Deliberate secure erase. This may support sanctions and adverse inference, but the inference must be tied to intent to deprive. The personal-file explanation and belief LexCore had files may limit the inference. Still, it undermines Adrian's credibility and supports that he took and attempted to destroy evidence." Good. Irreparable harm: "Likely if targeted: continued solicitation, loss of customer relationships, use of next-release info, erosion of trade secret value. Weaker if broad: independent feature, one customer damages quantifiable. Need show likely future harm not just past." Overbroad: table. Defenses: list. Strategic risk: list. Defensible scope: detailed. TRO recommendation: yes narrow. Need maybe include "most defensible scope of temporary relief, forensic examination, expedited discovery, and settlement" in one section. Good. Let's maybe include a "proposed order" bullet. Good. Need maybe ensure final answer not too adversarial? We represent LexCore but objective. Good. Let's now compose final. Use clear headings. Ensure no missing. One nuance: "Customer non-solicitation restriction is enforceable only as to customers with whom employee had material contact and only to the extent reasonably necessary to protect legitimate relationships." Need maybe "material contact" not just access to data. Need maybe as product director, likely but need prove. Need maybe if he only had data but no direct contact, maybe not. Need maybe "customer-contact spreadsheet" indicates he had contact info. Need maybe. Another nuance: "A customer’s initial contact does not automatically defeat solicitation. The question is whether the former employee actively encouraged or induced the customer to move business." Need maybe his statement "You should see what Evidentia is launching..." likely encouragement. Good. Another nuance: "Noncompetition restriction unrelated to sale of business is void." Need maybe "preventing Adrian from working on competing products" is a noncompete even if not labeled. Good. Another nuance: "Emergency forensic relief must be proportionate. A court should avoid unnecessarily exposing the new employer’s legitimate confidential information." Need maybe target. Another nuance: "Destruction of relevant evidence after a preservation duty arises may support sanctions. An adverse inference requires intent to deprive." Need maybe. Need maybe mention "LexCore's requested imaging of Evidentia's systems" could expose Evidentia's legitimate confidential info. Need targeted. Need maybe mention "Adrian's no access to LexCore-derived files" claim: if true, but wiped drive prevents proof. Need forensic. Need maybe mention "clean-room protocol adopted two weeks after Adrian started" - not a perfect defense; first two weeks. Need maybe. Need maybe mention "Adrian became product lead immediately" - high risk but not enough. Need maybe. Need maybe mention "Evidentia announced feature similar to confidential roadmap" - if roadmap general, independent; if specific, threat. Need maybe mention "publicly available court documents enhanced with internal annotations" - only annotations. Good. Let's write final now. Ensure final is in English. Use markdown. Need maybe not cite cases because governing law provided. Good. Let's produce final.