Architecture decisions
Why tarang 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.
ADR 0001 · Accepted
Record architecture decisions
Decisions about how tarang is built (its dependencies, its boundaries, the trade-offs it accepts) were made in conversations and commit messages, where nobody finds them later. A c…
ADR 0002 · Accepted
Ship as its own repository, as a Vyom tool
tarang started as a script inside Vayu that piped rows into wofi. Living inside the desktop's dotfiles meant it couldn't be installed, versioned or tested on its own, and wofi's pl…
ADR 0003 · Accepted
Talk to NetworkManager through nmcli
Wi‑Fi on Linux desktops is almost always NetworkManager. Its D-Bus API is large; nmcli is stable, scriptable and always installed with it.