Compliance verification

Compliance verification is where you configure the checks that measure whether a project actually meets its frameworks — the coverage rules and active checks behind the verification described in Verification & quality analysis.

Coverage rules

You define coverage rules that express what your frameworks require to be linked and covered — every requirement verified, every risk controlled, every relationship the standard expects. These rules are what the platform checks records against continuously, so compliance coverage is computed from the real thread rather than asserted. Where a rule isn’t met, it surfaces as an issue to resolve.

Active checks

The set of active checks determines what’s evaluated for a project. Enabling the right checks means verification reflects your actual obligations — neither missing a requirement that matters nor flagging things that don’t apply. Because the checks are configurable, verification is tuned to your regulatory context rather than a one-size-fits-all pass.

Verified continuously

Configured here, these rules and checks run as people work, so a project’s compliance state is always current. That’s the mechanism behind the platform’s core promise: that readiness is verified continuously and the evidence is ready when an audit asks. Closely related quality checks are configured in Quality analysis.