Architecture overview

NXD follows this boundary:

Nix modules -> canonical JSON -> validation -> plan -> persisted apply -> verify

Consumer repositories own topology, inventory, policy, and reviewed state. NXD owns schemas, planning, provider execution, reports, and reusable contracts.

See docs/nxd-integration-design.md for the full accepted design.