AWS's own agent fleet guidance puts the lock-in in state, auth and telemetry, not the framework

The provider interface is the pattern that gets a code sample, and it is the pattern that was never the hard part. Wrapping `bedrock_client.invoke_model` and `openai.ChatCompletion.create` behind a single `complete()` method turns a provider swap into a configuration change rather than a rewrite ^[7]. Nothing else in the post reduces that cleanly.

Read the diagnosis again. LangChain keeps conversation history in memory or Redis, CrewAI uses task queues, custom agents write to DynamoDB or Postgres ^[5], and AWS's stated conclusion is that convergence cannot be forced without rewriting production systems ^[6]. Then the concrete patterns arrive: the model interface, an agent registry with a router and framework adapters, telemetry normalisation, federated identity, and config-as-code with immutable versions ^{[7][8][10][11][13]}. State management is the divergence the post opens with and the one boundary it never draws ^[1]. Session history stays wherever each framework put it, which makes the store, not the framework, the thing nobody moves later.

The substrate also carries the operational verbs. Canary routing at ten percent of traffic is described as a capability of the request router ^[13], and the router only dispatches to agents that have registered metadata and have an adapter ^[8], so an agent outside the registry has no progressive rollout at all ^[2]. Cross-agent tracing works the same way: a request can be followed across frameworks only once callbacks, task events and CloudWatch writes are mapped into a common schema and landed in a central store ^[10]. Credential revocation without redeploying agents works because tokens are short-lived and issued by a central identity service against tool-declared scopes ^[11][12]. Each of those is a fleet property purchased from shared plumbing, not a property of anyone's chosen library.

The post is candid about the bill for that, at least in one place. The failure surface it names is registry unavailability, where the router cannot dispatch and the mitigation is caching registry data locally with TTL-based refresh ^[14]. That failure sits in the shared layer every team now depends on rather than in any framework a team picked ^[3], and a TTL cache relocates the outage into stale dispatch decisions rather than removing it.

Which is why the LangChain-versus-CrewAI argument is the cheap one. A team can replace CrewAI with a custom orchestrator inside its own repository so long as the adapter contract holds, and the agents already in production are untouched ^[9]. The registry, the event schema and the identity service do not move on those terms: the normalisation mappings and everything reading from the central store are downstream of the schema choice ^[10]. Pick the framework by taste. The substrate is picked once.