Architecture Decision Records
The why behind Leoflow design decisions — one record per decision, immutable once accepted.
The record of how Leoflow got here and where it is going.
The why behind Leoflow design decisions — one record per decision, immutable once accepted.
The historical road to release — where Leoflow has been heading.
Working planning notes on connector compatibility and the two-tier connector model.
Background analyses that shaped the MVP — the reverse analysis and the UI/frontend assessments.