Architecture Decision Records
The why behind Leoflow design decisions — one record per decision, immutable once accepted.
Version v0.5.6 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 →
Specs
What a large change will build, written before the code, with the template to start one.
Read the specs →
Roadmap
What is planned next, and the road to the first 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 →
Specs
Design specs for large changes, written before the code; what will be built, how it upgrades, and how it is tested.
Roadmap
Where Dexaflow is heading next, and the historical road to the first release.
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.