The Nebulo approach to data management provides an opportunity to move away from the legacy approach of files and databases with their fixed and limited formats for locating and referencing information. Moving data between systems is often possible. However, this is typically with varying degrees of compromise. This happens because there is generally no easy way to take both data and code behaviors that exist in one system to another. Nebulo changes that by enabling both data and code behaviors to become like Lego Bricks.
Data storage and access are separate from the data structure of the ‘Thing’ (uniquely named entities/objects) itself for a variety of reasons. We have 8 types of ‘possibility boxes’ (described below) based on how we can scale data (lossy-signal, exact-record, rolling-queue history, belief-certainty thoughts, etc.).
Granular security/access issues are handled by each ‘Essence Possibility Box’ so whether you can edit or read-only or just name-only or ‘nothing/no-awareness’ is determined from within each Box…not a central (potentially hackable) system.