Data Model

The public contracts revolve around DriveNodeBase and higher-level node shapes defined in the DTO layer.

Common concepts

• namespace: isolates a logical drive space
• id: stable node identity
• parentId: folder relationship
• children: nested tree expansion for folder reads
• file metadata: name, size, content type, preview state, readonly/archive flags

Why the model matters

The same grid, list, selection, and command patterns can work for:

• object storage backed files
• database-backed local nodes
• Google Drive files and folders

Where to look in the package

• @tulip-systems/drive exports contracts, DTO helpers, validators, and shared search params
• provider entrypoints layer provider-specific schemas and node types on top