Skip to content

Under the hood

Ditana makes a lot of decisions automatically during installation — from resolving package conflicts to applying CPU-specific mitigations.

This section explains the architecture behind those decisions. You do not need to read this to use Ditana daily. However, if you want to understand our “Configuration as data” philosophy, learn how the system probes hardware, or intend to contribute to the installer, this is the place to start.

  • Configuration as data — why Ditana separates the installer engine from its knowledge base, and how updates ship without re-spinning an ISO.
  • Hardware detection — how the installer dynamically probes your hardware at boot time using KDL rules.
  • CPU mitigations — detailed documentation on per-CPU vulnerability detection, default kernel parameters, and how to override them.