Architecture Decision Records
The why behind Leoflow design decisions — one record per decision, immutable once accepted.
Version v0.4.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 Leoflow got here and where it is going.
- Architecture Decision Records — the why behind Leoflow’s design, ADR by ADR (immutable once accepted).
- Roadmap — the historical road to release.
- Planning — working notes on connector compatibility and the two-tier model.
- Background — the reverse-analysis and UI/frontend assessments that shaped the MVP.
Roadmap
The historical road to release — where Leoflow 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.