# Nexus Device Manager 1.0 — Evidence Checklist

Capture screenshots from a Release build after opening **Nexus Device Manager** via launcher **Enheder** or `nexus:devices`.

| File | What to show |
|------|----------------|
| `device-overview.png` | **Oversigt** section: KPI cards (CPU, RAM, Disk, Network), left nav, right info panel |
| `device-cpu.png` | **CPU** section: model, cores/threads, load %, 60-second sparkline history |
| `device-storage.png` | **Lager** section: drives with friendly names and usage bars |
| `device-network.png` | **Netværk** section: active connection, IP, gateway, download/upload speeds |
| `device-health.png` | **Systemstatus** section: health ring/KPI and CPU/RAM/Disk/Network status |

## Notes

- Window title should read **Nexus Device Manager**, not Windows Device Manager.
- Left navigation must list all Phase 1 sections (Oversigt through Systemstatus).
- Read-only: no driver install, kill process, or admin actions.
- Data sources: WMI (`System.Management`), Performance Counters, `NetworkInterface`, winspool (printers), EnumDisplayDevices (monitors).

## APIs used

| Area | API |
|------|-----|
| CPU | WMI `Win32_Processor`, `GetSystemTimes`, optional `MSAcpi_ThermalZoneTemperature` |
| RAM | `GlobalMemoryStatusEx` |
| Disk | `DriveInfo` |
| GPU | WMI `Win32_VideoController`, registry fallback |
| Network | `NetworkInterface`, IPv4 statistics delta |
| Displays | `EnumDisplayDevices` via `DisplaySettingsService` |
| Printers | `EnumPrinters` via `NexusPrinterInfoService` |
| USB | WMI `Win32_PnPEntity` (PNPClass=USB) |
| Bluetooth | Registry via `NexusBluetoothInfoService` |
| Processes | `Process.GetProcesses`, `TotalProcessorTime` delta |

## Known limitations (POC)

- GPU load % not available without vendor-specific APIs
- CPU temperature often unavailable (depends on WMI thermal zone)
- Bluetooth paired devices from registry only (no live pairing state)
- Wi‑Fi signal strength not exposed in standard .NET APIs
