ecm-governance-auditor

To audit governance and traceability in ECM capability models, run the governance-audit workflow against your workspace repository to surface findings and recommended corrective actions.

You can identify governance gaps in ECM Studio model repositories including missing ownership metadata, incomplete release history, absent publish evidence, and broken downstream traceability for retired capabilities.

Yes, the ECM governance audit performs downstream traceability checks for retired capabilities and verifies replacement links within the repository during governance reviews and releases.

Yes, you can use this governance audit on capability models stored as JSONL format, as it specifically captures retirement rationale, ownership metadata, and release history across revisions.

The best way to surface compliance findings before an ECM model release is to run the governance-audit workflow, which authenticates release records and generates a findings report with recommended corrective actions.

Your ECM governance audit shows missing publish evidence when structural events lack authentic release records across revisions, indicating incomplete governance documentation that requires corrective action before review.