Schema Decisions

This file records important data model and schema decisions.

2026-04-25: Drizzle is the stable schema authority

Decision:

Drizzle will be used as the stable schema and migration authority once physical tables are created.

Reason:

The project needs schema changes to be version-controlled, AI-readable, and reviewable.

NocoDB or similar tools may be used for human data editing and migration experiments, but stable schema changes should move into packages/db.

Decision:

Binary files will live in R2 or another S3-compatible object store. PostgreSQL will store metadata in an assets-like table.

Reason:

Object storage is better for binary file bodies. PostgreSQL is better for ownership, tags, relationships, filtering, and audit metadata.

Decision:

The project will not use a waterfall-style complete database design before development starts.

Reason:

The app contract, data domains, OS Shell behavior, and future community model are still evolving.

The project will maintain conceptual docs and Mermaid ERD while using migrations for stable schema changes.