Architectural constraints imposed by BPMN model owner

FlowDrop Modeller API integration (current architecture used in POC) is tightly coupled to the BPMN model specification, as used by the Model Owner (e.g. BPMN.io). While this brings compatibility with ECA and plugin reusability, it also limits innovation in how workflows are defined and executed.

Considerations:

• Can we extend the model schema without breaking BPMN interoperability?
• Do we need an abstract FlowDrop-native model layer that maps to BPMN only for export?
• Should we define a custom Model Owner?