Governance Coverage and Compliance
Automated compliance scoring and coverage analysis across all enabled governance rules, with per-rule breakdowns, non-compliant block identification, uncovered node lists, and direct navigation to fix issues.
Enabling governance rules is only useful if you can measure how well your workspace meets them. Two complementary reports that analyse compliance from opposite directions: the Governance Compliance report checks whether your governance blocks actually govern the right things, and the Governance Coverage report checks whether your architectural nodes have the governance documentation they need.
Governance Compliance
The compliance report examines every enabled governance rule and evaluates each applicable content block against it. For a given rule like "Risk blocks must govern model entities", the engine finds every risk block in your workspace and checks whether it has at least one governs edge to a model entity node.
Governance Coverage
The coverage report takes the inverse perspective. Instead of asking "do my blocks govern something?", it asks "are all my architectural nodes governed?" For each enabled rule, the engine finds all target nodes of the required type and checks whether at least one content block of the source type governs each one.
| Metric | Description |
|---|---|
| Overall Coverage | Weighted average across all enabled rules, showing the percentage of architectural nodes with required governance documentation |
| Fully Covered | Nodes with at least one governance block of the correct type linked to them |
| Partially Covered | Nodes with some governance documentation but not all required types |
| Uncovered | Nodes with no governance documentation of the required type - these are the gaps |
Unlinked Entity Blocks
A third related report identifies entity content blocks that exist in your workspace but have zero outgoing governs edges. These blocks represent governance documentation that is not connected to any architectural node, reducing their value as evidence of governance.
The report groups unlinked blocks by type (risk, security control, compliance requirement, etc.) and shows the page path for each one. This helps you identify blocks that were written but never linked to the architecture, perhaps because the linking step was forgotten during authoring.
Continuous Measurement
All three reports run against live workspace data using NeoArc's signal-based analysis engine. When you save a file, whether it is a content page, schema, or diagram, the reports regenerate automatically after a 500ms debounce. This means you can: