We've flashed out our ideas bit by bit, and finally made Kamix 2.x! Now, you don't have to be forced to use a certain VFS (which was a long-deprecated Volumes extension version in Kamix 1.x), or even be forced to use a certain shell. Kamix 2.x leaves it up to you to build your new distro.
Now, Kamix 2.x isn't service-based like Kamix 1.x is. The main changes in 2.x are that the kernel has shifted to binaries, as opposed to a full service/daemon structure (that's for you to decide). In fact, the init process (the thing that 2.x starts after it's done initializing) is a broadcast and not a service.
Since an init process is now required to boot Kamix 2.x, the kernel is pretty much a black box apart from the new kernel panic panel, which you'll be met with when you boot Kamix raw (with no added or set init process). So, you'll need to BYOIP (Bring Your Own Init Process). However, we're working on a fallback shell for Kamix... keep in tune!
Kamix 1.x will be going into KTLO mode soon, as we're shifting our goals to 2.x. A major update for Kamix 1.x will be released, which adds a KTLO notice, improvements to the checking service, and more.
Note that Kamix 2.x will break most 1.x applications. A new terminal emulator will be used, service architectures are improving, et cetera.
Small patches will still be released for Kamix 1.x, but no new features will be planned for it unless the situation is dire. Updates to Kamix 1.x's extensions will happen, most of the extensions that Kamix 1.x uses (example: TurboDev, Volumes, etc.) have either been deprecated or have since released a major update that broke Kamix 1.x functionality to the point that a fix would require a remake of Kamix.