The product
The governance engine
Owner, approval, and retention travel with the run, from connection through the issued report.
The governance engine runs across the toolbox. It requires an owner, a source, and a classification before ingestion. Issuing a report needs a named reviewer. Changing a method needs approval before results refill. Arming a destructive step needs a named interlock.
What it enforces
| Moment | The engine requires |
|---|---|
| Ingestion | Owner, source, and classification. |
| Issue | A named reviewer. |
| Method change | Approval before results refill. |
| Destructive step | A named interlock. |
| Retention | Raw data stays immutable for the retention period. |
| Contract end | The owner’s data is purged, and a deletion record is kept. |
Customer data stays isolated per customer. Pooling it requires written consent. A number from a published document stays a reference and never enters a measured result.