Developers are separating business definitions, authorization and data connectors from a single model or analytics product. The mechanism is making parts of a functioning workflow movable rather than offering only interchangeable model names.
Scope: Semantic metadata, authorization and content connectors; provisional direction/window.
Potential direction of power
Converters, development tools and licensed connections provide parts of a portable workflow. Compatibility does not guarantee that definitions, permissions, context and controls survive a move. A technically compatible subscription can also remain commercially gated.
Apache Ossie aims to make enterprise semantic definitions portable. Code, incubation and reported commercial backing do not establish complete round-trip metric/permission migration.
October 6 announcements describe broader MCP connectors across Atlassian products and an expanded OpenAI relationship. MCP is an interface through which assistants can use external tools. Atlassian lists support across clients such as Claude, ChatGPT and Cursor, with broader Jira, Confluence and related workflows; some service-management features remain forthcoming. Reported usage and efficiency figures are company metrics, not independent comparisons. The OpenAI partnership page was indexed but direct retrieval failed; it supports a qualified partnership lead rather than every implementation detail.
Model choice within a workflow is useful, but it does not establish freedom to move the underlying project history, permissions and organizational knowledge out of Atlassian.
The CMA reports some launched connections and switching-fee changes, alongside limited uptake and important unfinished interoperability work. Voluntary engagement does not guarantee that users can move complete workflows.
Developers can preserve common session code across local and hosted providers, reducing a bounded part of switching cost without universal workflow equivalence.
Inbound delegation separates the chosen assistant from the SAP business agent doing the work. SAP retains permissions and business context, while outbound operation and complete migration are not established.
A shared interface lets participating customers use a compatible outside assistant for a limited set of workforce workflows. Assistant substitution is possible at the interface, while records, enablement and permissions remain with Beeline.
Opens provisionally for institutional customers at the semantic/authorization layer; intact end-to-end migration is not yet demonstrated.
What would change this assessment
Real migrations that preserve working context, permissions and controls without rebuilding the system—and with manageable exit costs—would demonstrate a practical right to leave.