wave5-local-to-world-read-only-contract

Incorrect LocalToWorld values in Unity DOTS usually happen when reading the value before TransformSystemGroup executes or when gameplay writes corrupt the composed parent-chain transform. Treat LocalToWorld as strictly read-only after the transform system updates to ensure spatial queries use correct world-space positions.

To safely read LocalToWorld in an ECS physics query job, declare it with read-only access like `in LocalToWorld` in IJobEntity, and schedule the job to run after TransformSystemGroup so the world transform is freshly computed and uncorrupted by concurrent gameplay writes.

You should write entity movement to LocalTransform, not LocalToWorld. TransformSystemGroup then computes and propagates the composed world-space transform safely, ensuring rendering and spatial calculations rely on an uncorrupted LocalToWorld value across parent-child hierarchies.

You need to enforce a read-only LocalToWorld contract whenever systems require composed parent-chain transforms for root and child entities, such as Unity DOTS rendering, physics queries, and culling, to prevent unstable spatial logic from gameplay write conflicts.

You can use stale last-frame LocalToWorld data only if you accept explicit latency in your spatial calculations. For fresh, accurate world transforms, you must schedule your read-only systems to run after TransformSystemGroup executes.