How movacx/bc250-control-center works
BC250 Control Center is a Linux desktop control and monitoring application for AMD BC-250 hardware, with a CLI and optional SteamOS Decky panel. The main workflow is to start the desktop app, inspect system status, prepare supported dependencies when needed, then review and apply bounded hardware changes. Its domain branches cover GPU governance, CPU tuning, Compute Unit and fan control, plus diagnostics and recovery. The graph uses documented capabilities and the composition-root source; several subsystem paths are represented by their enclosing directories because their wiring was not sampled.
Main entry points: app.py Desktop interface · main.py Desktop entry · bc250_contract.py Privileged helpers · system System service
Components 21
User interfaces
- Desktop entry
frontends/desktop/main.py - Desktop interface
frontends/desktop/app.py - CLI
frontends/cli.py - Decky Quick Access
integrations/decky/bc250-quick-access/src/index.tsx
Application services
- Service composition
src/bc250cc/application/container.py - System service
src/bc250cc/application/system - Dependency preparation
src/bc250cc/application/preparation/service.py - Monitoring and health
src/bc250cc/application/health/aggregator.py
Hardware controls
- GPU governance
src/bc250cc/application/gpu - CPU tuning
src/bc250cc/application/cpu/use_cases.py - Compute Units
src/bc250cc/application/compute_units/operations.py - Fan control
src/bc250cc/application/fan/policy.py
Platform integrations
- GPU runtime adapter
src/bc250cc/infrastructure/gpu/cyan_gpu_engine.py - GPU repository
src/bc250cc/infrastructure/gpu_repository.py - Dependency repository
src/bc250cc/infrastructure/dependencias_repository.py - Privileged helpers
privileged/lib/bc250_contract.py - Decky backend
integrations/decky/bc250-quick-access/main.py
State and safety
- Recovery snapshots
src/bc250cc/application/recovery/service.py - Recovery snapshot store
src/bc250cc/infrastructure/persistence/recovery_engine.py
Other components
- Desktop user
- Linux hardware and services
Connections 25
- Desktop user → Desktop entry: starts
- Desktop entry → Service composition: constructs services
- Desktop entry → Desktop interface: opens
- Service composition → System service: provides
- Desktop interface → System service: uses
- CLI → System service: accesses
- Desktop interface → Dependency preparation: requests preparation
- Dependency preparation → Dependency repository: executes preparation
- Desktop interface → Monitoring and health: presents status
- Desktop interface → GPU governance: requests GPU changes
- Desktop interface → CPU tuning: requests CPU tuning
- Desktop interface → Compute Units: requests CU changes
- Desktop interface → Fan control: requests fan changes
- Desktop interface → Recovery snapshots: requests snapshots
- Recovery snapshots → Recovery snapshot store: captures and reads
- GPU governance → GPU repository: reads and writes
- GPU repository → GPU runtime adapter: delegates runtime control
- GPU runtime adapter → Linux hardware and services: reads evidence and controls
- Dependency repository → Linux hardware and services: checks and prepares
- Compute Units → Privileged helpers: dispatches operations
- Fan control → Linux hardware and services: controls fan
- CPU tuning → Linux hardware and services: tunes CPU
- Decky Quick Access → Decky backend: dispatches requests
- Decky backend → Privileged helpers: runs named operations
- Privileged helpers → Linux hardware and services: applies privileged changes