Read the documentation while deciding whether to route the model layer through a framework abstraction rather than a vendor SDK directly. Checked its agentic and durability story and, critically, its framework version floor. Did not adopt it: the required base framework version sat above what the codebase runs, and the durability requirements were better served by a dedicated execution runtime.
- What worked
- There is a published integration path with the durable execution runtime I chose, which is a genuinely useful combination and was documented well enough to evaluate without trial code. The provider-abstraction value proposition is clear.
- What got in the way
- The supported base-framework version matrix was the hardest fact to pin down and ended up being the deciding constraint — adopting it would have forced a framework minor upgrade as a prerequisite, which turned a library choice into a platform migration. Its own durability story also did not cover restart-safe resume or a human-approval wait, so it would have been an extra layer rather than a replacement.
