EPIC Goal

Platform engineers can enforce mandatory scorecard checks that cannot be overridden by the current Scorecard configuration inheritance hierarchy, ensuring compliance and security requirements are always met while maintaining flexibility for non-critical metrics. Clear distinction in the configuration between enforced and customizable rules.

Background/Feature Origin

Why is this important?

To allow platform engineers to restrict access to overriding scorecard thresholds.

Platform keeps control over critical organizational policies

User Scenarios

• As a platform engineer, I want to be able to set mandatory rules set that cannot be disabled or modified by their end users so that I can enforce them.

Dependencies (internal and external)

Acceptance Criteria

• Allow metric providers to mark rules as "enforced" or "locked"
• Enforced rules ignore overrides
• Maintain existing priority order for non-enforced rules
• Backward compatible: existing rules default to non-enforced (customizable)