Axiom will not attach to a protected process.
This is the first design constraint, not a disclaimer added later. It shapes the hook strategy, the signing model and which games ever appear in the registry.
Every backend checks the target process for a known kernel anticheat driver before attaching. If one is loaded, the attach is refused and the title is marked blocked in the profile registry. There is no flag, no build and no configuration that changes this.
What Axiom is for
Single-player games. Private servers. Dedicated servers where the operator decides what runs. Emulated and console titles. Tooling that reads a process you own, on a machine you own, to build something on top of it.
That is a large space, and it is almost entirely abandoned by modern anticheat. A framework serving it well does not need to fight anybody.
What it is not for
Competitive online titles. Anything where other players did not consent to what your client is doing. We do not take the position that this is impossible, only that it is not what this project builds.
Asking for an exception is not useful. The refusal is in every backend, and the people who would have to agree to remove it are the people who put it there.
Why it is worth the cost
Nothing has to hide. The core installs ordinary detours in plain sight, which is why two mods can share a function at all.
A registry that refuses one category of mod can hold publishers to a standard. One that serves everything cannot.
No kernel module, no service, no elevation. Axiom runs as your user and attaches only to what you launch through it.
Reporting a mod
A published version is immutable, but it can be yanked so the manager stops installing it. Yanks happen for malware, for a mod that targets a blocked title, and for a package whose declared capabilities do not match what it does.