It is artisanal so it varies dramatically in style and quality. I’ve had both great and diarrhea-inducing chicha.

Did you have chicha prepared the 'artisanal' / traditional way described in the article...

This part—the chewing—plays a key role in the fermentation process, since enzymes from saliva convert the starch to sugar, which, when combined with wild yeast or bacteria, eventually becomes alcohol. The preparers then spit the resulting juice into a clay pot, where it ferments for several hours. After that, voila: Chicha is born

Chicha is spit?!?

Few concepts have been found to be independently discovered and adopted across the history of disparate human civilizations. Don't kill members of your own tribe. Incest is bad. Find a way, any way, to make booze. :-)

What's the benefit of this approach vs doing scoped queries? i.e. current_user.pages.find(params[:id])

(1) It makes so you can't forget.

(2) Some customers require it.

(3) At scale, database sharding becomes necessary. Multi-tenancy is a natural way to shard.

My experience is that it's easy for a developer (new or not) to forget to scope some query. So, by using a gem like this or tenancy, your infrastructure prevents the tragic mistake of missing it.

A middle ground solution might extend active record to warn you whenever a query doesn't have current_user / current_customer.

The issue is that you would be missing the tenant_id (or user_id) if you were to do `other_object.pages.find(params[:id])` (i.e. on something thats not directly below the user)

That is a problem in systems that expect the tenant_id to always be in the query, so you can locate which node the query needs to go to.