Architect ECS Systems

Design and implement data-oriented Entity Component System (ECS) architectures that optimize CPU cache locality, eliminate heap fragmentation, and scale to tens of thousands of simultaneous simulation entities.

Core Rules

• Data-Oriented Cache Locality: Store components in contiguous memory buffers (archetypes or sparse sets). Design components as Plain Old Data (POD) structs without pointers or virtual function dispatch tables.
• Explicit System Scheduling: Organize systems into deterministic execution stages (e.g. PreUpdate, Update, PostUpdate, FixedUpdate). Disallow circular execution dependencies between systems.
• Parallel Safety & Borrow Rules: Systems with non-overlapping mutable component queries must be capable of executing in parallel threads. Read-only queries can execute concurrently across any number of systems.
• Contract Adherence: Emit contracts/schemas/implementation-result.json upon completing ECS architecture implementations.

Suggested Process

1. Archetype & Component Decomposition

Decompose entity state into minimal, composable POD components:

• Position(Vector3), Velocity(Vector3), Health(float, float), RenderMesh(MeshId) Avoid monolithic "God components" containing both simulation and presentation state.