Architecture Decision Records
The why behind Leoflow design decisions — one record per decision, immutable once accepted.
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.
What Dexaflow ships next and when, by release, with the 1.0 criteria; the road to the first release is kept as an archive.
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.
Archived analyses from before v0.1 that shaped the MVP: the reverse analysis and the UI and frontend assessments. Kept for context; not maintained.
Where the names Leoflow and Dexaflow come from, and what the rename keeps working.