governance-mandate-cycle

To automate pending Mogul governance mandate execution, this Skill spawns a Mogul agent to consume mandate cycles, handling validation, execution, and status checking. It requires a pending mandate file at audit-logs/mogul/mandates/current.json to function properly.

AI-driven governance mandate processing uses a Mogul agent to analyze patterns, audit the system, and check for runtime drift. This approach ensures continuous compliance by automatically validating and acting upon issued governance mandates within a specific team topology.

Yes, you can explicitly skip a Mogul mandate cycle through deferral. The Skill provides an option to defer a pending mandate with a given reason, ensuring the automated governance process remains auditable and controlled.

Yes, mandate automation requires a pending mandate file located at audit-logs/mogul/mandates/current.json. Without this specific JSON file in place, the Mogul agent cannot validate or execute the governance cycle.

You can check the status of ongoing or pending Mogul governance mandates using this Skill. It monitors mandate execution progress, allowing you to verify that AI-driven operational adjustments and compliance checks are completed.