Architecture: ¶

This is a living document, so update it when reality changes.

1. Key parts¶

Name the important types, scenes, services, modules, or assets and where they live.

Describe the organizational structure: which namespaces define this system, what assembly definitions (.asmdef) are used, and how they relate.

Explain how data moves through the system.

How this gets verified today: unit tests, play-mode tests, integration checks, or manual QA steps.

What is still risky, unclear, or likely to change.

Optional implementation notes, diagrams, links, or follow-ups.