Policy Configuration

One of the first places you might encounter the term policy in the app is in the policies tab of the app itself. This tab performs two main functions:

1. Configure which rules in the policies are enabled / disabled for a particular diagram

2. Debug, modify or diagnose behaviours stemming from the policy files

Policies page tabs

Rules

Use this tab to view the active rule set and control what is enabled for the current diagram and environment.

• Confirm which policy rules are currently active.
• Validate that category-level toggles match what you intend to assess.
• Quickly check if behaviour changes are caused by enable/disable state rather than policy logic.

Rule Summary Tree

Use this tab for a readable, rule-by-rule breakdown of conditions and actions.

• Understand what each rule reads and writes.
• Review how a rule contributes to scoring and expected controls.
• Spot duplicated or conflicting rule intent.

Specification

Use this tab to inspect policy contribution to generated specification text.

• Verify that policy-driven specification lines are present and correctly grouped.
• Check whether configuration-key-based specification mappings are being applied.
• Confirm contribution ordering and source attribution.

Entity Summary

Use this tab to review key coverage by entity type.

• See default scope keys, default config keys, and potential dynamic keys.
• Validate that keys shown for each entity type are relevant.
• Spot keys that appear unexpectedly due to broad rule conditions.

Policy Editor

Use this tab to edit policy YAML and iterate quickly.

• Make controlled changes to rule definitions and actions.
• Test policy updates without leaving the diagnostics context.
• Use with lint output to catch schema/logic issues early.

Rule Dependency Graph

Use this tab to understand how rules depend on one another through produced/consumed keys.

• Identify chains where one rule sets values another rule depends on.
• Find circular or brittle dependency patterns.
• Diagnose why expected downstream rules are not triggering.

Config Key Map

Use this tab to see where keys are consumed and produced across policy.

• Trace a key from input configuration through rule actions.
• Confirm whether scope keys and control keys are wired as expected.
• Detect orphan keys not referenced by any useful rule path.

Coverage Gaps

Use this tab to identify missing policy coverage.

• Find areas where entities or controls are not addressed by current rules.
• Compare expected scope/control model with actual rule coverage.
• Prioritize where to add or refactor policy logic.

Policy Linter

Use this tab to catch authoring issues before runtime.

• Detect malformed rules, missing fields, and inconsistent action shapes.
• Surface potential logic problems (for example, dead conditions or unreachable outcomes).
• Run lint after each edit cycle in Policy Editor.

AI-Explain

Use this tab for plain-language interpretation of complex policy logic.

• Translate rule behaviour into human-readable reasoning.
• Accelerate onboarding for new policy authors/reviewers.
• Cross-check AI explanation against Rule Summary Tree and Dependency Graph.