No Naked Reads, No Naked Writes

No naked access requires all data queries and writes to pass through predefined schemas. This eliminates direct operations on the underlying database, enforcing governance and maintaining consistency across distributed systems.

This principle enables auditing and traceability. Every operation is logged, making it easier to track data lineage.

No naked access promotes coordination between services or applications interacting with the database. By requiring developers to define schemas, the system reduces ambiguity about data structure and interpretation.

Schemas function as community-driven assets. Users benefit from collective vetting and maintenance of open-source schema repositories. Groups adopt data philosophies matching their privacy requirements without setting permissions on each data element. This provides granular control while users offload maintenance to contributors who refine and optimize schemas.