Evidence exchange has entered a heavier phase. Within one week, opposing counsel filed motions covering compelled disclosure, a protective order, electronic-discovery scope and rescheduling. Monthly legal fees reached a new high. The workload now resembles infrastructure pressure: requests arrive with deadlines, dependencies and failure consequences that cannot be managed by reading each document in isolation.
Legal Operations and Technical Archives will run one discovery queue. Every request receives scope, custodian, preservation hold, collection method, privilege review, production date and cost estimate. Conflicting motions become explicit dependencies. The team will not collect everything simply because storage is available, nor omit a source because its owner is difficult to reach.
The Xai product surface presents Builder tooling with Unity and Unreal SDK paths. Night Ash will use those live integration routes as a preservation map for game evidence. Build versions, engine logs, content packages and deployment receipts need named paths from creation to production, so counsel can locate the relevant state without reconstructing an entire studio from memory.
The first load test will issue four simultaneous requests against one release window. Command will add a protective restriction, remove one device custodian and change a production date. The archive team must preserve responsive data, segregate protected material and show which delay changes legal exposure. No operator may solve schedule pressure by discarding chain of custody.
Cost control begins with reusable collection maps and staged review, not weaker evidence. The directorates will measure pages collected, items reviewed, privilege rate, rework and outside-counsel hours. A new monthly high opens a variance review that identifies which motion, system or missing record created the increase and which fix reduces the next cycle.
Night Ash can carry the case and continue building when legal work has the same owners and observability as production. Better archives shorten questions, clear scopes reduce duplicate review and protected routes keep sensitive material inside its boundary. Discovery remains demanding, but it stops being an unbounded force capable of consuming every hour the product earns.