These maps explain how creative direction becomes build contracts, how implementation reaches evidence gates, and how automation remains subordinate to approval.
The system separates emotional law from canon, gameplay contracts, reusable components, assembly, and validation. A world can remain expressive without making implementation arbitrary.
The production plan grows through foundation, spatial proof, abilities, world expansion, completion, and release. Each group must establish evidence before scope expands.
Animation timing triggers a named notify, resolves to a gameplay tag, enters authored MetaSound variation, and lands in the runtime submix.
Intent, routing, generation, review, provenance, and publication are separate states. The system can move quickly without quietly turning unfinished work into public work.
Each map exists to answer four practical questions: who owns the decision, what it depends on, what evidence proves it, and what must remain blocked until approval.
Canon, gameplay, assets, audio, and release status are not allowed to quietly contradict each other.
Build captures, comparison boards, test results, and manifests replace unsupported completion claims.
The architecture can be inspected without exposing private repositories, unreleased narrative, or production credentials.