Architecture Decision Records
The why behind Leoflow design decisions — one record per decision, immutable once accepted.
Version v0.5.9 of the documentation is no longer actively maintained. The site that you are currently viewing is an archived snapshot. For up-to-date documentation, see the latest version.
The record of how Dexaflow got here and where it is going.
The why behind Leoflow design decisions — one record per decision, immutable once accepted.
Design specs for large changes, written before the code; what will be built, how it upgrades, and how it is tested.
Where Dexaflow is heading next, and the historical road to the first release.
What a Dexaflow release may change, how long a minor line is supported, how features are deprecated, and what stays compatible across upgrades.
Working planning notes on connector compatibility and the two-tier connector model.
Background analyses that shaped the MVP — the reverse analysis and the UI/frontend assessments.
Where the names Leoflow and Dexaflow come from, and what the rename keeps working.