Pylerium

Open-source on GitHub: Pylerium
Guides & Previews
The loadout framework operates as an Extensible Execution Pipeline Schema, where every visual slot in the Call of Duty menu styled interface acts as a modular container for any arbitrary script, setting, or hook you define.

Instead of hardcoding specific rules, each slot represents a broad Execution Abstraction Category:

Primary Weapon Slot (Primary Engine Target)
Role: Defines the core entry point of your project.

The "Gunsmith" (Attachments): Maps to an extensible CLI Parameter & Argument Registry. Each "attachment slot" (Muzzle, Barrel, Optic, Stock, etc.) is simply a user-configurable key-value field or flag array passed to the primary execution process.

Secondary Weapon Slot (Auxiliary Process Pipeline)
Role: Defines optional pre-execution or companion processes.

Capabilities: A modular array of companion scripts, background daemons, sidecars, or environment pre-checks that fire before or alongside the main script.

Tactical & Lethal Slots (Runtime Utilities & Output Handlers)
Tactical (Pre-Run & Runtime Utility Hooks): A container for any active profiling, logging, telemetry, or dynamic interceptor module attached during execution.

Lethal (Post-Run & Artifact Handlers): A container for post-execution operations, handling build outputs, deployment triggers, cleanup scripts, or export targets.

Field Upgrade Slot (Context Injector)
Role: An environment variable and secrets provider.

Capabilities: A swappable configuration profile slot (e.g., loading specific .env files, API key stashes, or platform-specific runtime contexts into the execution process).

Perk Slots 1, 2, 3 & Specialty (Modular Policy Grid)
Role: A dynamic matrix of boolean toggles, flags, and rules.

Capabilities: These slots load from a central Policy Registry. Any feature, system flag, privilege setting, or code formatting rule registered in your application can be assigned to any Perk slot as a simple toggleable policy.

Wildcard Slot (Pipeline & System Overrides)
Role: A high-priority modifier container.

Capabilities: Defines macro-level overrides that alter the overall build/run pipeline, allowing you to bypass standard execution flows, inject global decorators, or chain multiple execution passes together.