Decoupling the Harness

Coupled systems make substitution expensive by construction. When prompts are authored in a provider's console, retrieval runs on a provider's vector store and conversation state is held in a provider's session, the harness is inseparable from the weights and switching means rebuilding the harness — which is the real barrier, since the harness is where the accumulated work sits. Decoupling relocates each of those components to the organization's side, at which point the weights become an endpoint. The test of whether decoupling is genuine is not how many providers are listed as supported but what would need rewriting if one disappeared.

In Centralpoint the answer to that test is nothing. Prompts and skills are records in the organization's SQL environment; the vector index is built and held locally; interaction logs and dialogue history are the organization's records under its own retention. Model selection is a runtime setting, and adaptations for new providers ship every two weeks across on-premises, private cloud and public cloud alike.