Compliance Reports
Operational reporting that stays tied to the workflow evidence behind it.
Veridominus does not invent a universal compliance score. It exports the current evidence, classification, and coverage each supported workflow actually has, so the report can be reviewed outside the app without losing trust boundaries.
CSV, JSON, and HTML where supportedEvidence retainedCoverage retained
Typical report sources
- Patch Compliance summaries and drill-down evidence
- Ghost Hunter findings with classification, evidence, and coverage notes
- EA Dependency Scanner evidence, coverage rows, and operator status
- Workflow-specific exports such as Blast Radius or Fleet Commander where the feature exposes them
Export formats
Depending on the workflow, Veridominus supports CSV, JSON, and HTML export. The export format is chosen per workflow, not forced into one global report abstraction.
Exported data preserves the evidence model the workflow uses. Unsupported boundaries and partial coverage should still be visible outside the app, not collapsed into a cleaner-looking but weaker summary.
What exported reports are for
- Sharing operational review results with another administrator
- Keeping a point-in-time copy of a cleanup or dependency review
- Feeding a ticket or change-review workflow with the same evidence seen in the app
- Preserving the distinction between confirmed, partial, unsupported, and unknown states
Related workflow docs
Read Patch Compliance, Ghost Hunter, EA Dependency Scanner, and Blast Radius Analyzer for the workflow-specific truth model behind their exports.