"Per-Process Controls" (Quantized Executions)

Terms like "per-process controls" are understated in the programming world, and "quantized execution" is the key that makes these terms make sense. I made a threading architecture that embodies "quantized execution" and "per-process controls" and learned that the key to a productive codebase is having a "surface of execution" that speaks for itself. Each operation is quantized to a unit of arguments (token) and each unit represents a flowing surface of metadata and heuristics. The architecture I made TokenGate is described best as "an async threading hybrid model with per-process controls". In TokenGate there's two layers of task authority, the first layer is the CPU and IO process tags to control affinity, the second is a direct admin control panel operated on the localhost of the rig running TokenGate. Example of the control mechanisms in the GUI Having (per-task or) per-operation commands to change the runtime is helpful, undoubtedly. What I want to discuss is if people would get on