Robotics Trade Secrets and Departing Employees

Identify the claimed secret

Potential information includes source code, calibration, manufacturing methods, test results, unreleased designs, datasets, pricing, and supplier arrangements. The legal inquiry requires the statutory elements, including independent economic value from secrecy and reasonable measures to maintain it. A broad label such as autonomy stack does not identify the actual secret with sufficient precision for every dispute. [1, § 134A.002]

The inventory should distinguish public patents and documentation from genuinely confidential information. A company cannot assume that disclosing an invention in a patent leaves the disclosed material secret. Different undisclosed implementation details may still require their own analysis.

Reasonable protective measures

Recommended measures include access tied to roles, confidentiality agreements, controlled repositories, device and cloud controls, vendor restrictions, and clear procedures for sharing. The statutory standard is reasonable measures in the circumstances, not perfect security. The record should show what the business actually did rather than only what a policy says. [1]

Joint projects and field testing can expose information outside the company. Agreements should define permitted use, recipients, return or deletion, publication, residual information, and access after the project. A confidentiality clause is useful only if the team understands which disclosures it covers and follows the agreed process.

Misappropriation and lawful competition

TUTSA defines improper means and misappropriation and recognizes proper means within its text. The source, acquisition, disclosure, use, knowledge, and duty conditions matter. Independent development or lawful reverse engineering should not be described as automatically unlawful merely because a competitor reaches a similar result. [1, § 134A.002]

The investigation should distinguish copied files, retained access, customer solicitations, technical similarities, and ordinary employee skill. Timing can support an inquiry but does not alone establish every element. A litigation position should identify the information and evidence rather than assert ownership of a person's entire professional experience.

Federal remedies and protected disclosures

The DTSA provides a federal civil remedy for qualifying misappropriation involving the required commerce nexus. Its injunction and damages provisions have their own conditions. It does not replace every Texas claim or automatically validate a restraint on accepting employment. [2, § 1836]

Section 1833(b) protects specified confidential disclosures for reporting or investigating suspected legal violations and certain sealed court filings. It also contains employer notice requirements in covered agreements with employees, including the statutory treatment of contractors and consultants, and consequences for specified remedies if notice is omitted. Confidentiality documents should account for those provisions rather than purport to prohibit every protected report. [4]

Restrictive covenants

Texas §§ 15.50 through 15.52 address covenants not to compete, including the ancillary-agreement and reasonableness requirements and the statutory enforcement framework. Scope, duration, geography, activity, and the interest asserted require actual analysis. A noncompete and a confidentiality obligation are not interchangeable. [3]

A robotics employer should identify whether a proposed restriction protects an actual interest and whether narrower confidentiality or access measures address the concern. This guide does not assume a universal federal ban or universal enforceability of Texas covenants; the current controlling law and agreement govern the particular decision.

Departures and new hires

A recommended departure process revokes access, identifies devices and repositories, preserves relevant records where required, obtains return or deletion under the agreement, and documents unresolved issues. It should avoid indiscriminate collection of another person's private information. A new employer should instruct recruits not to bring or use prior confidential material and should document independent development where relevant.

Remote accounts and vendor systems deserve particular attention. A former engineer may retain a cloud token even after a physical badge is disabled. Conversely, an old account appearing in a log does not prove who used it. Technical evidence should be evaluated carefully and preserved with its limitations.

Hypothetical engineering move

An engineer joins a competitor developing a similar mobile robot. The former employer should identify specific protected code or test information and evidence of acquisition or use. The new employer should confirm clean sourcing and permitted work. Similar product goals alone do not answer the trade-secret claim, while copying a protected repository cannot be excused merely by calling the project independent development.