The Timeshare You Didn't Know You Bought

Of everything your AI vendor ships this year, the warmest feature is the one to fear. Tag the assistant inside a Slack thread and it reads along, holds the context, reaches into your tools, splits the work into pieces, chases the open items, and behaves like a colleague who never clocks out. No one at the vendor must act in bad faith for this to curdle. The incentives handle that on their own.

The instant that assistant becomes a shared coworker, something quietly reclassifies. It stops being a model you rent by the token and turns into the surface where work gets interpreted, remembered, routed, and eventually carried out. People reach for "model lock-in" and worry about the wrong thing. Models are the cheap part of the relationship. The expensive part is that your company's operating memory now lives inside someone else's product, which means you have started renting your own company back from the people who sold you the assistant.

It is the oldest sales structure dressed in new clothes: a timeshare you didn't know you bought. You pay forever for something you never own. The costs creep, climbing quietly with each task you route through and each season the meter resets higher. And getting out is notoriously hard, because the unit you signed for was never the model or the agent. It was the deeded right to your own operating memory, and the only party holding the title is the vendor who sold it back to you.

If you have the right infrastructure in place, switching vendors costs little where it counts for little. Models swap in an afternoon and agents get copied overnight. The thing that survives no migration is the knowledge of how your company truly runs: the Slack scar tissue, the exception paths no one wrote down, the promises made to specific customers, the threads abandoned half-finished, the implicit owners, the strange workflow born of one bad night in 2019, the buried verdict that "we tried that in Q2 and it died." Once that knowledge settles inside a single vendor's agent layer, you are no longer renting intelligence. You are renting your operating memory and the lease renews itself.

Where this turns dangerous is the tokenomics behind the warm fuzzies of the friendliest feature. A human colleague costs a salary you can forecast a year out. This one runs on an unbounded token meter that climbs with every task you route through it. As more work flows into this system, the vendor captures your software budget and also begins capturing your labor budget. Every task you hand over lifts the vendor's revenue as well as your exit cost, so their interests and yours drift apart where the value is created and the work concentrates. Follow the meter far enough and the arrangement comes into focus quickly. In effect, you are paying a vendor to run your operating model, billed by the token, at a price you neither set nor cap. The convenience shows up immediately. The dependence takes a few months to set. Faust at least got years; this is his bargain on a quarterly clock.

And the uncapped price is not even the worst of it. The worst part is that you cannot leave. Once the full context of how your company runs lives in one vendor's system, no competitor, no successor tool, and no team of your own can rebuild that context well enough to take over. A seller who knows you have nowhere to go stops competing on price and starts naming it. What began as a teammate is now a landlord who owns the only building in town and the rent is whatever they decide.

What should the architecture look like instead? It refuses to let one vendor hold both halves of the deal. Rent the best intelligence this month from whoever is ahead, whether that is Anthropic, OpenAI, Google, or something open you run yourself. Then own the layer beneath it. In a System of Intelligence (SOI), that layer is the Evidence Plane, and it serves as the System of Record for how your company operates. It stays inspectable, permissioned, portable, and model-neutral by design. It records what happened, why it happened, who set it in motion, which policies were evaluated, what it cost, and what came of it, and it stays independent of any single model router so you can change vendors without forfeiting your routing memory, your economics, or your quality history.

In the Baser SOI model, the control plane enforces policy and emits the evidence, which the Evidence Plane records as your System of Record, yours by default because the whole stack is yours. The Model Router sits behind the control plane as the swappable layer and never doubles as the System of Record. Cost gets attributed by workflow and verified outcome rather than by whatever figure lands on the vendor invoice. That attribution is your exit strategy: a cost you can read by workflow is one you can carry to another provider next quarter. A teammate that writes into a memory you own earns its keep all day long. The trouble starts only when you let that teammate become the place where work is interpreted, remembered, and ratified.

None of this argues against the warm feature; its usefulness is exactly what should keep you alert. Put it to work at the edge, where it answers questions, drafts the first pass, and quickens the people around it. Hold it back from the seat of record, where your company's memory either belongs to you or belongs to your vendor, with no third option waiting in reserve.

Eventually the convenience burns off and an old decision is left standing. Choose who holds the memory before the friendliest feature on the roster chooses for you.