# ``ParcelCore`` The window model, geometry, and reducer, with no AppKit or IO. Feed state and an event into the reducer to get new state and effects. The engine executes those effects; Core never reads a clock, queries a window, or starts an animation. This keeps layout decisions easy to test. ## Tiling layouts A workspace owns a tile tree. Splits divide available space; stacks share a tile and choose an active window. Layouts include `grid`, `columns`, `rows`, `side`, `tree`, `bsp`, and `accordion`. Manual splits use the requested orientation; BSP splits the focused tile along its longer side. Accordion gives the focused child most of the space while keeping its siblings visible. Balance, rotate, and mirror transform the tree without losing stacks or focus. Gaps and reserved edges reduce the usable display area before placement. A window cap limits tiles rather than discarding windows: extra windows stack. Geometry uses display coordinates, not assumptions about a screen's origin. Minimum window sizes constrain placement. When a layout cannot fit, report that constraint instead of inventing an offscreen frame. ## Commands and state Commands describe intent: focus a neighbor, change a layout, move a window, or adjust a split. Events describe observations and accepted input. Effects ask the platform to act. Window, display, and workspace identities belong in the model; native objects do not. `Command.enterMode` updates `State.activeMode` and emits a semantic announcement. A `nil` mode selects the default bindings. Config resolves names and shortcuts; Core only records the transition so it can be replayed. Keep deterministic behavior here and cover it with Swift Testing. Real AX behavior belongs in the platform and FixtureApp e2e suites.