Layer 1: Owned Data
The first layer of data is the owned data, which is data that is created and owned by the developer.
Owned Data includes three sub-layers of data that are owned and controlled by the developer. Handwritten data is manually created and can be modified easily. File-based databases are imported from external files and can be modified through server code. Database schema connections are queried from connected databases and can be modified through queries.
1.1 Handwritten by Developer
This sub-layer comprises of data that is handwritten by the developer and is available from the server. It doesn't need to be imported, queried, fetched, or retrieved, and it is manually mutable data.
1.2 File-based Database
This sub-layer consists of data that is available from the server and is imported from a file (.env, json, csv, etc.). This data can be mutated via server code.
1.3 Database Schema Connection
This sub-layer consists of data that is available from the server and is queried from a connected database. This data can be mutated via queries.

Layer 2: Fetched Data
The second layer of data is the fetched data, which is data that is fetched from external sources.
Fetched Data includes three sub-layers of data that are fetched from external sources. Cached data is fetched from 3rd party servers and cached on re-entry. Fetched data from 3rd party endpoints is always updated on re-entry. Data saved in the browser is retrieved from the browser's local storage and can be modified by the user.
2.1 Stored in Cache
This sub-layer comprises data that is available from the server and is fetched from a third-party server. The data is cached upon re-entering, and it can be mutated via endpoint requests.
2.2 Fetched from 3rd Party Endpoint
This sub-layer consists of data that is available from the server and is fetched from a third-party server. The data is always updated upon re-entering, and it can be mutated via endpoint requests.
2.3 Saved in Browser
This sub-layer consists of data that is available from the client and is retrieved from the browser's local storage. This data can be mutated by the user and defaults to data available from the server.

Layer 3: User Data
The third and final layer of data is the user data, which is data that is generated by the user.
User Data includes three sub-layers of data that are generated and modified by the user. Authorized local endpoint data is fetched from 3rd party servers but called through a local endpoint that is authorized. Fetched data from 3rd party endpoints is available from the client and can be modified. Data saved in the browser is an empty list that can be filled by the user and is reactive.
3.1 Authorized Local Endpoint
This sub-layer comprises data that is available from the client and is fetched from a third-party server, but calling a local endpoint. The data and request are authorized.
3.2 3rd Party Endpoint Data
This sub-layer consists of data that is available from the client and is fetched from a third-party endpoint.
3.3 Saved in Browser
This sub-layer comprises an empty list ready to be filled by the user. This data is reactive and user-generated.