epic_perlman [It's] kinda to hard to know, just by [looking] at the page and some of the top-level docs, how far beyond package management and into config management it pushes.
I suspect this question is more complicated than it might seem. In Android much of what might be considered "configuration" is genuinely immutable (in a different sense from what some desktop Linux distributions use "immutable" to mean). When Google ships Android 17 to a Google Pixel, many things just cannot be changed. System services can't be replaced, apps that ship with the system can't be deleted, device drivers can't be added or deleted, etc. -- or else the system partition will fail a signature check and the device won't boot. When Samsung ships Android 17 on Samsung devices, parts of the system come from Google and are mostly unchangeable, but there is a mechanism for Samsung to overlay or replace things, but from the user's point of view once that "negotiation" between Google and Samsung is over the results genuinely can't be changed (or else the system partition will fail a signature check and the device won't boot).
Depending on the device, other people can produce immutable configurations -- for example, on Pixel devices it is currently possible to unlock the bootloader, flash GrapheneOS and the GrapheneOS signing key, and then re-lock the bootloader. At that point it's not possible to change the kernel, system services, preinstalled apps, etc., without (you guesed it!) the system partition failing its signature check and the device refusing to boot. Or an individual user can flash a personally-built OS and personal signing key.
After that, there are limited ways to change a device's configuration. Some components can be upgraded via overlays, but only by the same party who signed the in-use system partition (the system for this is called "APEX"). Users can install apps, but what those apps can do is limited, and users can reduce what an app can do. A Mobile Device Manager (MDM) can do a wide variety of things, but -- by design -- can't do everything. An app store can do many things, but -- by design -- can't do everything.
If some desired configuration feature changes can't be done by installing sets of apps, or by the powers an MDM has, then the next step is probably building and signing system partitions. There isn't really a way to port a desktop-Linux configuration management app to Android. It would be sort of like "porting" a whale into a submarine: whales and submarines do have similarities, but neither one can really fit into the framework provided by the other one. I guess in theory it might be possible to replace parts of the Android build system with a different way to specify the contents of a system partition (perhaps inspired by configuration files similar to Puppet, Chef, etc.), but that would be a monumental undertaking.