Import and export formats #14
Description
Problem Statement
Problem
The General Controls Engine relies on Simulink models to define control logic, but Simulink’s native text-based formats (specifically .mdl) are opaque, tool-specific, and poorly suited for modern source control workflows. These files cannot be easily read or understood without Simulink, produce noisy and non-deterministic diffs, and are difficult or impossible to review, merge, or audit in Git.
As a result, small logical changes often appear as large binary diffs, reviewers cannot reliably verify intent, and long-term traceability and maintainability suffer. This creates friction between model-based design and standard software engineering practices, especially in collaborative or safety-critical environments.
Proposed Solution
The General Controls Engine needs to support importing, exporting, and loading Simulink models in a clean, deterministic, and human-readable format that is tool-agnostic and source-control friendly. Such a format must clearly express model structure, behavior, and connectivity while excluding editor-specific noise, enabling meaningful diffs, reviews, and collaboration by anyone—not just Simulink users.