From 4200b4ea042412cf66c7e70b3b55492c6916137f Mon Sep 17 00:00:00 2001
From: Victor Giers <mail@victorgiers.com>
Date: Sat, 11 Apr 2026 03:53:43 +0200
Subject: [PATCH] Update architecture.md with persisted project structure
 details

---
 architecture.md | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/architecture.md b/architecture.md
index 2deeff1b..53c744a3 100644
--- a/architecture.md
+++ b/architecture.md
@@ -372,15 +372,22 @@ Rules:
 - no three.js object references
 - should be testable in isolation
 
-Example structure:
+Example persisted project structure:
 
 ```ts
-interface SceneDocument {
+interface ProjectDocument {
   version: number;
-  world: WorldSettings;
+  activeSceneId: string;
+  scenes: Record<string, ProjectScene>;
   materials: Record<string, MaterialDef>;
   textures: Record<string, TextureDef>;
   assets: Record<string, AssetRecord>;
+}
+
+interface ProjectScene {
+  id: string;
+  name: string;
+  world: WorldSettings;
   brushes: Record<string, Brush>;
   modelInstances: Record<string, ModelInstance>;
   entities: Record<string, EntityInstance>;
@@ -838,6 +845,8 @@ At that point, the user-facing save/load format should be a **project package**
 - `scene.json`
 - referenced asset payloads
 
+`scene.json` may still contain multiple authored scenes inside one project document; the file name does not imply a single loaded runtime scene.
+
 Recommended logical shape:
 
 ```txt