Know where truth lives—and who owns the result.

Documentation hierarchy

This model makes the current authority chain visible. Individual repositories may use an equivalent locked convention.

Project/
├── Idea/
│   └── Idea-Brief.md
├── Design/
│   └── Game-Design-Brief.md
├── Bible/
│   ├── Game-Identity/
│   ├── Player-Experience/
│   ├── Game-Structure/
│   ├── Core-Logic/
│   ├── Content/
│   ├── Design-Data/
│   ├── Progression-Economy/
│   ├── Presentation/
│   └── Reference/
├── Architecture/
│   ├── Architecture.md
│   └── Module-Map.md
└── Modules/
    └── Module-01/
        ├── Module-01.md
        └── Slices/
            ├── Slice-Map.md
            ├── Slice-01.md
            ├── Slice-02.md
            └── Slice-03.md

Authority lookup

Permanent ownership and temporary work

Modules describe permanent ownership. Slices describe temporary development work.

Every implementation asset is placed by asking: Which system owns it? Then: What role does it perform within that system?

Project → Module → Role → Optional Detail

Locked Unity project structure

Assets/
├── _Project/
│   ├── Application/
│   ├── Modules/
│   ├── Shared/
│   ├── Scenes/
│   ├── Settings/
│   └── Tests/
└── ThirdParty/

Standard internal Module structure

Modules/
└── ModuleName/
    ├── Runtime/
    │   ├── Components/
    │   ├── Logic/
    │   ├── State/
    │   ├── Contracts/
    │   ├── Events/
    │   └── Types/
    ├── Configuration/
    │   ├── Definitions/
    │   └── Assets/
    ├── Presentation/
    │   ├── Prefabs/
    │   ├── UI/
    │   ├── Animation/
    │   ├── Audio/
    │   └── VFX/
    ├── Editor/
    └── Tests/

Folders are optional vocabulary, not an empty-folder quota. Runtime owns executable behaviour; Configuration owns tunable data; Presentation owns visible and audible expression; Editor contains authoring support; Tests verify the module contract.

Asset Placement Explorer

Placement follows ownership, not where an asset happens to appear.

Conventions still under validation

Scene roots: scene composition belongs under Scenes while domain behaviour stays in modules. The precise root/prefab convention is not locked.

UI safe area: safe-area adaptation should be reusable presentation behaviour with scene-level composition. Its final ownership boundary remains intentionally unsettled.