Backbone.Model attribute mutation and event bypass

Backbone.js models maintain a public attributes hash to store data, while providing get() and set() methods for managed access. According to documented behavior in Backbone 1.x, the framework does not encapsulate this hash, leaving it accessible to external scripts.

A design concern arises when external code modifies model.attributes directly rather than using the set()` method. Because the attributes object is public, direct writes bypass the internal logic that triggers change events and executes validate() routines.

Given that Backbone relies on convention rather than language-level private fields for encapsulation, how can a developer ensure that attribute mutations consistently trigger the necessary event lifecycle? Is there a documented pattern to prevent direct access to the attributes hash without overriding the base Model prototype?