Audience 01
Enterprise AI teams
Needs the same permission model for people and agents.
Knowledge & context · Concept
Where the work actually changes.
ContextInfrastructure is aimed at Enterprise AI teams, data architects, developers.
01
Who it is for
Three audiences, one boundary model.
Audience 02
data architects
Uses the product where the cost of an unscoped action is higher than the cost of setup.
Audience 03
developers
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 |
|---|---|---|
| Context ingestion and normalization | Removes an ad hoc step from the workflow. | Specified |
| Provenance and quality scoring | Removes an ad hoc step from the workflow. | Specified |
| Policy-based retrieval and delivery | Removes an ad hoc step from the workflow. | Specified |
| Context versioning and caching | Removes an ad hoc step from the workflow. | Specified |
| MCP, API and SDK interfaces | Turns a manual control into an explicit contract. | 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.