Architecture

Data Model

Namespace (user or org)
└── Project
    ├── Episode (a recording session)
    │   ├── Files (video, audio, labels, text tracks)
    │   ├── Tracks (time-series scalars/tensors)
    │   ├── Logs
    │   └── Parameters
    ├── Bindrs (curated file collections)
    ├── Datasets (groups of bindrs)
    └── Node tree (folder hierarchy, materialized paths)

Node Tree

Uses MongoDB materialized paths. All files and folders are nodes in a unified tree.

Path convention: root = ",", depth 1 = ",camera,", depth 2 = ",camera,front,".

Auth

Two-token system:

1. Login — OAuth device flow via vuer-auth → short-lived token
2. Exchange — POST /auth/exchange → long-lived dreamlake JWT (HS256)
3. API calls — Authorization: Bearer <dreamlake-token>

First login auto-creates User + Namespace records.

Upload Flow

CLI → chunk file (10 MB) → S3 multipart upload via BSS
    → register asset in DreamLake Server (creates node hierarchy)
    → trigger Lambda for HLS splitting (video/audio)

Uploads are resumable. State persisted to ~/.dreamlake/uploads/.

Tech Stack