Multi-Consumer Enrichment

Most enrichment is built for a single purpose and duplicated when a second purpose appears, so an organization ends up extracting dates once for retention and again for contract alerts, classifying once for permissions and again for search. Each duplication drifts, and the divergence surfaces as two systems disagreeing about the same document. Single-derivation architecture treats enrichment as a shared layer: the properties are derived once, held on the record, and read by whatever needs them.

In Centralpoint a record's derived properties are read by retention scheduling, workflow routing, audience evaluation, full-text and natural-language search, accessibility remediation and the vector index alike. There is no synchronization step because there is no second copy — which is the same principle that keeps governance state consistent across the platform rather than requiring integration between components.