Plugins and Security

Kinemium's data model checks plugin execution context when a script asks for a service. Services may declare an intent, and a plugin can be denied access when it has not requested that intent.

Examples found in current source include graphics-related intent on Workspace and threading intent on RunService.

Guidance

• Request only the capabilities your plugin actually needs.
• Prefer stable high-level services instead of renderer, FFI, or internal storage bindings.
• Treat filesystem, process, networking, FFI, rendering, and threading surfaces as privileged.
• Do not depend on engine-internal helper modules from src/environment/class or service helper subdirectories as if they were public classes/services.

Plugin service

local Plugin = game:GetService("Plugin")

The plugin runtime binding also resolves that same service.