Monitorian is a mature Windows desktop utility for adjusting brightness, contrast, and related display settings across multiple monitors, including external DDC/CI-capable displays. In production it enumerates physical and internal displays through several Windows APIs (Dxva2 DDC/CI, WMI, WinRT DisplayInformation, CCD DisplayConfig), wraps each display in a MonitorItem abstraction, and presents a tray-icon-anchored WPF UI with sliders for brightness, contrast, and adjustable range. It also supports unison changes, SDR white-level adjustment on HDR-capable displays, ambient-light-based adaptive brightness, startup registration, CLI-based control, and extensive probe/operation logging for diagnostics. Architecturally, this is a multi-project .NET Framework 4.8 solution: Monitorian (thin WPF executable), Monitorian.Core (domain and UI core), ScreenFrame (reusable WPF/Win32 window and tray helper library), StartupAgency (startup registration abstraction), IconImage (icon generation tool), Monitorian.Test (unit tests), and a WiX installer. The main entry path is App.xaml.cs -> AppKeeper -> AppController, which coordinates session/power/display watchers, monitor discovery, view models, and tray popup windows. The code is organized MVVM-style with custom WPF controls, converters, behaviors, and a clean separation between monitor hardware access and UI state. Key data flows are hardware-driven: MonitorManager aggregates monitor sources into DdcMonitorItem, WmiMonitorItem, HdrMonitorItem, and UnreachableMonitorItem objects; view models read and write brightness through DDC/CI calls or WMI methods; BrightnessWatcher reacts to external brightness changes; and session/power events trigger monitor rescans. External dependencies are Windows system APIs and contracts (Dxva2, SetupAPI, WMI, PowrProf, WinRT), Windows Forms NotifyIcon, Microsoft.Xaml.Behaviors, and MSTest. The codebase is actively maintained but carries medium technical drift: it targets legacy .NET Framework 4.8, uses preview C# language features, calls undocumented or version-gated Windows APIs, and contains some duplicated helper utilities and localization inconsistencies. Despite those issues, the core abstractions are well-structured and several subprojects are designed as genuinely reusable libraries.