Audience 01
Chief data officers
Uses the product where the cost of an unscoped action is higher than the cost of setup.
Knowledge & context · Concept
Where the work actually changes.
EnterpriseCDI is aimed at Chief data officers, AI infrastructure teams, enterprise architects.
01
Who it is for
Three audiences, one boundary model.
Audience 02
AI infrastructure teams
Adopts it to replace a patchwork of tools with one reviewable surface.
Audience 03
enterprise architects
Uses the product where the cost of an unscoped action is higher than the cost of setup.
02
Use cases
Each row maps a capability to the operational change it is meant to produce.
| Capability | Operational change | Status |
|---|---|---|
| Data acquisition and integration | Removes an ad hoc step from the workflow. | Specified |
| Context catalog and provenance | Turns a manual control into an explicit contract. | Specified |
| Entity resolution and knowledge graphs | Turns a manual control into an explicit contract. | Specified |
| Quality and lineage governance | Makes an existing action reviewable. | Specified |
| Context APIs and MCP delivery | Removes an ad hoc step from the workflow. | Specified |
03
Migration
How a team would move from the status quo without a big-bang cutover.
Step 01
Map the current path
Name the tools, owners and handoffs that the product replaces. Nothing is removed yet.
Step 02
Run one capability
Pick a single scoped capability and run it alongside the old path, with evidence compared side by side.
Step 03
Retire the old path
Remove the previous tool only when the new record is complete enough to audit.