Storage-Based Lock-In

This form of lock-in is distinctive because it is reversible by a decision rather than by a project. Integration lock-in requires re-engineering; data-gravity lock-in requires moving volume; genuine platform lock-in requires rebuilding capability. Storage-based lock-in requires only that the customer put the material somewhere else, and the entire cost disappears on the day they do. The reason it persists is not difficulty but default: the convenient place to author a prompt is the console in front of you, and nobody notices the cumulative position being established until a renewal.

Centralpoint's default is the opposite one. Prompts, skills, generation patterns and the governance dictionary are authored as records in the organization's environment, so the accumulation builds on the customer's side from the first day rather than being repatriated later. Adaptations for new providers ship every two weeks, which keeps the option live rather than theoretical.