Repository Architecture

This is a Turborepo monorepo with three main packages:

1editor-v2/
2├── apps/
3│   └── editor/          # Next.js application
4├── packages/
5│   ├── core/            # Schema definitions, state management, systems
6│   └── viewer/          # 3D rendering components

Separation of Concerns

Package	Responsibility
@pascal-app/core	Node schemas, scene state (Zustand), systems (geometry generation), spatial queries, event bus
@pascal-app/viewer	3D rendering via React Three Fiber, default camera/controls, post-processing
apps/editor	UI components, tools, custom behaviors, editor-specific systems

The viewer renders the scene with sensible defaults. The editor extends it with interactive tools, selection management, and editing capabilities.

Stores

Each package has its own Zustand store for managing state:

Store	Package	Responsibility
`useScene`	`@pascal-app/core`	Scene data: nodes, root IDs, dirty nodes, CRUD operations. Persisted to IndexedDB with undo/redo via Zundo.
`useViewer`	`@pascal-app/viewer`	Viewer state: current selection (building/level/zone IDs), level display mode (stacked/exploded/solo), camera mode.
`useEditor`	`apps/editor`	Editor state: active tool, structure layer visibility, panel states, editor-specific preferences.

Access patterns:

1// Subscribe to state changes (React component)
2const nodes = useScene((state) => state.nodes)
3const levelId = useViewer((state) => state.selection.levelId)
4const activeTool = useEditor((state) => state.tool)
5 
6// Access state outside React (callbacks, systems)
7const node = useScene.getState().nodes[id]
8useViewer.getState().setSelection({ levelId: 'level_123' })

Source captured: 2026-10-11