A conventional operating system fixes its scheduling policies at build time, so one policy has to serve interactive work, builds, local inference and background sync alike, and can only compromise between them. ACOS proposed making agents part of the operating system: agents understand the task and its environment, then make decisions for the system. Kleinia applies this first to resource scheduling.
In Kleinia, scheduling is no longer a fixed default: the resource agent understands what you are doing and picks the best policy for the task at hand, and the policies themselves can be extended, evolve on their own and be shared across the community.