Audience question about the difficulty of keeping tuples consistent with domain models. Answer: it is a real challenge because you are duplicating many-to-many/foreign-key relationships out of your schema into a single normalized tuple table. Must be managed explicitly (e.g. after_commit). In a monolith it can be kept in one transaction; with authorization-as-a-service it must be synced between the Rails app and the external service. Track only relationships relevant to authorization.