architecture

The safeguard-ps module uses Connect-Safeguard and Invoke-SafeguardMethod to build URLs, manage global session state, and dispatch REST requests with retries and long-running task polling. The root module coordinates these flows while nested modules implement specific features.

SignalR and SSE streaming in safeguard-ps follows a negotiate, handshake, and event dispatch sequence. You can trace this execution flow through the module's listener utilities to understand how streaming events are received and processed during active sessions.

To modify safeguard-ps module wiring safely, review how the module manifest composes nested modules and exports public cmdlets. Validate the correct module or utility boundary before editing to ensure changes remain visible without breaking the public cmdlet surface.

Dynamic group rule parsing in safeguard-ps has specific serialization gotchas and constraints. Review the dynamic group rule handling logic to ensure your rule definitions match the expected serialization format and parsing constraints within the module internals.

safeguard-ps supports custom platform script parameters with PowerShell 5.1-compatible architectural reasoning. The module internals handle these parameters through specific dispatch guardrails that maintain compatibility with the PowerShell 5.1 runtime environment.

Changing global session state coupling in safeguard-ps requires adherence to low-level REST dispatch guardrails. You must maintain PS 5.1 compatibility and ensure correct YAML frontmatter discovery metadata, as improper modifications to global state can break authentication flows and request dispatch.