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 Leoflow design decisions — one record per decision, immutable once accepted.

Specs

Design specs for large changes, written before the code; what will be built, how it upgrades, and how it is tested.

Roadmap

What Dexaflow ships next and when, by release, with the 1.0 criteria; the road to the first release is kept as an archive.

Versioning and support

What a Dexaflow release may change, how long a minor line is supported, how features are deprecated, and what stays compatible across upgrades.

Planning

Working planning notes on connector compatibility and the two-tier connector model.

Archive: background

Archived analyses from before v0.1 that shaped the MVP: the reverse analysis and the UI and frontend assessments. Kept for context; not maintained.

The name

Where the names Leoflow and Dexaflow come from, and what the rename keeps working.