Architecture decisions
Why vinyasa is built the way it is: each significant decision as a short record (context, the decision, its consequences), in the ADR format. A decision is never edited away: a later one supersedes it. Sources: docs/adr.
Record architecture decisions
Decisions about how vinyasa is built (its dependencies, its boundaries, the trade-offs it accepts) were made in conversations and commit messages, where nobody finds them later. A …
vinyasa holds no settings of its own
A settings app can keep its own database of preferences and push them to tools, or read and write each tool's own setting. Its own database drifts from reality the moment anything …
Plain GTK 4, styled by the theme, not libadwaita
A settings window needs real controls: colour and font pickers, sliders, image thumbnails, live previews. A terminal UI can't show them; a web view is heavy. GTK 4 is already on th…
Keyboard first, with vim keys
Vayu is driven from the keyboard. A settings app usually isn't: sidebars and grids expect the mouse.