Design Principles#

1. The user should be able to opt-out of all our tooling easily, and be left with a fully functional configuration. The way we will do this is by having our tooling be a single import away.
2. Try to use existing tooling first Instead of trying to re-invent the wheel, try using existing tooling as much as possible.
3. The nixOS configuration is the state. Instead of maintaining the database to figure out the state of the OS, we will read the existing nixOS configuration, i.e parse and evalutate the flake. For this, we will need to build a program that can evaluate nix, and then we will cache it all in easily readable JSON. Kind of like what the nixos-cli does for NixOS options caching.
4. Be as quick to set up as possible. Similar to other projects, we want everything to be as quick and easy as physically possible. As such, we wanna eventually have an ISO that can be flashed for either aarch64 UEFI or amd64 UEFI (later BIOS+GPT, too) that asks minimal questions and installs the OS.

more TBD...