Architecture Decision Records
The why behind Leoflow design decisions — one record per decision, immutable once accepted.
Version v0.5.0 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.
Project
The project itself — architecture decision records, the historical roadmap, planning notes, and background analyses.
The record of how Dexaflow got here and where it is going.
Architecture Decision Records
The why behind Dexaflow's design, ADR by ADR — immutable once accepted.
Read the ADRs →
Roadmap
The historical road to release.
See the roadmap →
Planning
Working notes on connector compatibility and the two-tier model.
Browse planning →
Background
The reverse-analysis and UI/frontend assessments that shaped the MVP.
Read the analyses →
Roadmap
The historical road to release — where Dexaflow has been heading.
Planning
Working planning notes on connector compatibility and the two-tier connector model.
Background
Background analyses that shaped the MVP — the reverse analysis and the UI/frontend assessments.
The name
Where the names Leoflow and Dexaflow come from, and what the rename keeps working.