What changed

The CourtListener docket for X.AI Corp. v. Li reflects an active trade-secret dispute in the Northern District of California, including an opposition to a request for a preliminary injunction and related sealing activity. The filing excerpt identifies the case as involving the Defend Trade Secrets Act of 2016 and shows multiple declarations and exhibits attached to the opposition.

This is not a merits ruling. It is a litigation-posture signal: when an AI-company trade-secret dispute moves into emergency-relief territory, the company’s internal records become part of the practical case.

The hinge: can the company prove the control story quickly?

For counsel, the useful question is not whether one party will win. It is whether the company could assemble a credible record within days if a departing researcher or engineer were suspected of taking, retaining, deleting, or using disputed materials.

A preliminary-injunction fight tends to put pressure on evidence that is often fragmented across legal, HR, security, IT, and engineering systems. The docket’s sealing activity also underscores a recurring practical tension: the company may need to describe sensitive materials to the court while limiting public exposure of the same materials.

Controls to pressure-test now

Counsel should use this type of docket event as a tabletop exercise for departure controls involving confidential AI assets. The controls below are general departure-control considerations, not allegations about what did or did not occur in X.AI Corp. v. Li.

1. Confidential asset designation

Ask:

  • What materials are actually designated confidential?
  • Are those designations visible to employees and managers at the point of access or handoff?
  • Do research notes, source-code repositories, internal datasets, model-related files, and invention records have consistent ownership and classification records, where applicable?
  • Can the company explain why a particular item is protected without relying only on broad labels?

The goal is not more labels for their own sake. It is a defensible record showing what the company considered confidential before the dispute.

2. Access and export evidence

Ask:

  • Who had permission to access the relevant repositories, systems, files, or collaboration spaces?
  • Who could export, clone, download, sync, print, or transfer those materials?
  • What logs would show access, download, deletion, permission changes, or unusual activity?
  • Are logs retained in a form that legal, security, and outside counsel can understand quickly?

If the evidence lives only in specialized engineering systems, identify the internal owner who can authenticate and explain it before an emergency motion is being drafted.

3. Account cutoff and device return

Ask:

  • When are accounts disabled for departing employees?
  • Who confirms return or disabling of laptops, storage devices, credentials, tokens, and collaboration accounts?
  • Is the confirmation recorded in a durable exit file?
  • Are exceptions documented rather than handled informally?

A departure checklist is more useful when it records completion, timing, responsible owners, and unresolved gaps.

4. Confidentiality reminders and exit interview records

Ask:

  • Does the employee receive a clear reminder of confidentiality obligations at departure?
  • Who owns the exit interview record: HR, legal, security, or the business team?
  • Are invention, research, code, and project handoffs documented before access ends?
  • Are acknowledgments preserved with the employee’s agreements and role history?

The evidence value is in consistency and retrievability. A reminder that cannot be found later is operationally weak.

5. Preservation and escalation

Ask:

  • What facts trigger legal hold or preservation review after a departure?
  • Who decides whether to preserve logs, devices, chat records, repository activity, and access-control history?
  • What would be available within 48 hours of suspected misuse?
  • Who can prepare a concise factual chronology for counsel without overclaiming what the logs show?

The first version of the record often shapes the emergency posture. It should distinguish known facts, assumptions, and items still under investigation.

Contract and policy review questions

This docket signal also supports a targeted review of the documents employees actually see and sign:

  • Do confidentiality agreements match the types of technical materials employees handle?
  • Do internal policies explain permitted and prohibited handling of confidential technical materials?
  • Do onboarding records show that employees received the relevant policies?
  • Do vendor, contractor, or collaborator arrangements create gaps in repository access or return obligations?
  • Are invention and research handoff procedures aligned with the company’s confidentiality program?

This is a document-control exercise, not a broad rewrite mandate. The question is whether the company’s contracts, policies, and system records tell the same story.

How to use the signal

Treat the xAI docket as a prompt for a short cross-functional drill:

  1. Pick one high-sensitivity technical project.
  2. Identify the employees and contractors with access.
  3. Confirm what is designated confidential and where that designation appears.
  4. Pull a sample access-log package.
  5. Review one recent departure file for account cutoff, device return, confidentiality reminder, and handoff records.
  6. Write down what would be missing if counsel had to seek or oppose emergency relief next week.

The result should be a gap list with owners, not a theoretical policy memo.