Yea, it's dead obvious for humans, but it's very hard to formalize for computers

Our apps show all places which are tagged as currency:XBT = yes, so every place with this tag is considered valid, and we recommend those places to local users and communities, and we encourage them to shop there and to maintain those places (by bumping check_date or survey_date from time to time)

We can alter the query and ask OSM for something like:

Give us all places with currency:XBT = yes AND disused:amenity not present

It will work for this particular place, but there are other disused places with other tags, so we'll need to list all the tags which can be disused, explicitly, so it would look like this:

currency:XBT = true and disused:amenity not present AND disused:shop not present AND disused:craft not present AND disused:tourism not present AND disused:leisure not present AND disused:office not present AND so on...

Relying on other tags to figure out if currency:XBT is really true gets a bit tricky, so adding lifecycle prefix to this tag alone simplifies things quite a bit =)

Regarding local areas, OSM discourages remote edits, and some local communities have their own conventions, so the locals are the ones who supposed to make final judgements on how to tag places located nearby them