Well if we can not ensure that a given version of the Transifex JSON file is downloaded, then it can always happen that suddenly a string in the app is not translated anymore, or incorrectly translated. (This is similar to depend on SNAPSHOTs of OMOD rather than release artifacts, things can be suddenly broken).
For instance if someone is accidentally removing a key from the locale_en.json file, then the change gets propagated in Transifex, in every locale: pulling the files will result in missing a translation on screen.
Or if someone is incorrectly changing a ‘fr’ translation value in Transifex: pulling the files will bring the faulty value.
In the case of an implementer who wants to start a new demo server, confident that everything will be fine (since he did it the day before already), will pull the translations and suddenly have a string not translated/incorrectly translated in there.
And that is for demo servers but could happen for a production server that would have to urgently be rebuilt, in a disastrous scenario, and the Transifex files pulled again.
So that’s why I suggest that we suggest to save the localization files for each implementation in the ad-hoc Bahmni Config repo.