Data Model
This document describes the conceptual data model for Próx OS.
Purpose
This document describes the conceptual data model for Próx OS.
It is not a complete physical schema. Drizzle schema will become the implementation source of truth once tables are created.
Core Domains
Project
A project represents a long-running product, experiment, content direction, technical initiative, or personal plan.
Possible fields:
idslugnamedescriptionstatusvisibilitycreated_atupdated_at
Relationships:
- A project can have many bookmarks.
- A project can own datasets.
- A project can attach assets.
Bookmark
A bookmark represents an external URL or reference saved into the Próx OS data layer.
Examples:
- Documentation pages
- GitHub repositories
- Articles
- Design references
- Tools
- Immigration resources
- AI product references
Possible fields:
idurltitledescriptiontagssourcerelated_project_idcreated_at
Dataset
A dataset represents a structured collection of data that can be consumed by Próx OS apps.
Possible fields:
idslugnamedescriptionvisibilityowner_project_idcreated_at
Data Source
A data source represents an origin or connector for a dataset.
Examples:
- Manual table
- Airtable migration
- CSV import
- API source
- NocoDB-managed source
- Future MCP source
Asset
An asset represents metadata for a binary object stored in R2 or another S3-compatible provider.
The database stores metadata. The object store stores the file body.
Possible fields:
idproviderbucketobject_keymime_typesizechecksumowner_typeowner_idcreated_at
App
An app represents a launchable unit inside the OS Shell.
Possible fields:
idnameentry_typerouteiconpermissions
App Installation Future
An app installation represents a user-specific app availability or configuration.
Window State Future
Window state represents shell UI state such as open windows, focus, position, size, and minimized state.
This may start as local frontend state and later become persistent user state.