Feat: composed governance policy for feature flags

Author: rian-be

Examples/Core/FeatureFlags/Policies/FeatureFlagGovernancePolicies.cs

@@ -0,0 +1,24 @@
+using FeatureFlags.State;
+using ModularityKit.Mutator.Abstractions.Policies;
+
+namespace FeatureFlags.Policies;
+
+/// <summary>
+/// Reusable policy compositions for sensitive feature flag changes.
+/// </summary>
+internal static class FeatureFlagGovernancePolicies
+{
+    /// <summary>
+    /// Composed governance policy set for critical feature flag changes.
+    /// </summary>
+    public static IMutationPolicy<FeatureFlagsState> CriticalChanges() =>
+        PolicyComposition.AllOf(
+            name: "CriticalFeatureFlagGovernance",
+            policies:
+            [
+                new BusinessHoursPolicy(),
+                new RequireTwoManApprovalPolicy()
+            ],
+            priority: 200,
+            description: "Requires business-hours execution and two-man approval for critical feature flag changes.");
+}

Examples/Core/FeatureFlags/Program.cs

@@ -17,8 +17,7 @@ private static async Task Main()
         var provider = services.BuildServiceProvider();
         var engine = provider.GetRequiredService<IMutationEngine>();
 
-        //engine.RegisterPolicy(new BusinessHoursPolicy());
-        engine.RegisterPolicy(new RequireTwoManApprovalPolicy());
+        engine.RegisterPolicy(FeatureFlagGovernancePolicies.CriticalChanges());
 
         Console.WriteLine("=== ModularityKit.Mutators - Complete Example ===\n");
 
@@ -41,4 +40,4 @@ private static async Task Main()
         Console.WriteLine($"  Median execution time: {stats.MedianExecutionTime.TotalMilliseconds:F2} ms");
         Console.WriteLine($"  P95 execution time: {stats.P95ExecutionTime.TotalMilliseconds:F2} ms");
     }
-}
+}

Examples/Core/FeatureFlags/README.md

@@ -31,6 +31,7 @@ The example covers three workflows:
 - [`Mutations/DisableFeatureMutation.cs`](Mutations/DisableFeatureMutation.cs)
 - [`Policies/BusinessHoursPolicy.cs`](Policies/BusinessHoursPolicy.cs)
 - [`Policies/RequireTwoManApprovalPolicy.cs`](Policies/RequireTwoManApprovalPolicy.cs)
+- [`Policies/FeatureFlagGovernancePolicies.cs`](Policies/FeatureFlagGovernancePolicies.cs)
 - [`Scenarios/EnableNewCheckoutScenario.cs`](Scenarios/EnableNewCheckoutScenario.cs)
 - [`Scenarios/DisableLegacyCheckoutScenario.cs`](Scenarios/DisableLegacyCheckoutScenario.cs)
 - [`Scenarios/BatchFeatureToggleScenario.cs`](Scenarios/BatchFeatureToggleScenario.cs)
@@ -41,7 +42,7 @@ The example covers three workflows:
 
 1. registers the engine with strict options
 2. resolves `IMutationEngine`
-3. registers `RequireTwoManApprovalPolicy`
+3. registers the composed `CriticalFeatureFlagGovernance` policy set
 4. runs the example scenarios
 5. prints history for the main state
 6. prints engine statistics
@@ -84,6 +85,16 @@ It demonstrates:
 
 Use it as reference if you want to restrict rollout windows.
 
+### Composed governance set
+
+[`FeatureFlagGovernancePolicies.CriticalChanges`](Policies/FeatureFlagGovernancePolicies.cs) combines business-hours restrictions and two-man approval into one reusable policy set.
+
+It demonstrates:
+
+- `PolicyComposition.AllOf(...)`
+- explicit policy merge behavior
+- registering one composed policy instead of multiple hand-wired policy classes
+
 ## Scenarios
 
 ### Enable new checkout