# ``ParcelEngine`` Connect the pure reducer to real windows without blocking the main actor on AX. The reactor accepts events, updates Core state, and sends effects to injected services. The app supplies the native services; tests can supply controlled ones. Keep layout decisions in Core and platform calls behind those services. ## Window work Each application has its own AX thread. Discovery and reconciliation turn native observations into model events. Frame writes use size → position → size, skip unchanged values, and distinguish our writes from external changes. Slow or failed applications must not hold up healthy ones. Motion samples use latest-wins delivery. A newer target replaces stale pending work rather than building an animation backlog. Native readback is the evidence that an operation took effect; a successful private-call return alone is not. ## Configuration and input A validated configuration becomes a typed engine update. Rules decide how windows are classified and placed. Keyboard, mouse, and IPC input all reach the command path rather than maintaining separate layout logic. Binding modes live in replayable Core state. Mode entries are checked against the active configuration; removing the active mode returns to default bindings. The `config` IPC query includes `active_mode`, with `null` for the default mode. Drag previews are provisional. Releasing commits an eligible target; cancellation or stale ownership clears the preview without applying a drop. Restore, display changes, and permission loss must invalidate work that no longer belongs to the current window world. ## Testing and failures Use injected services to test ordering, cancellation, and failure handling. Use FixtureApp e2e scenarios for native focus, frame writes, Spaces, and recovery. Diagnostics should explain missing permission, unavailable private APIs, and slow or failed AX work. Do not turn those failures into silent success.