LumenClip DocsData
Data dictionary
Field-level data structures grouped by application domain.
Data dictionary
Application data is classified into six domain groups. Each group has one page containing a field-level table for every object. Every table uses the same columns: Field, Type, Example, and Description.
| Group | Contains | Reference |
|---|---|---|
| Persistence | Physical PostgreSQL rows, consolidated records, and dedicated tables | Persistence and physical records |
| Workspace and assets | Runtime workspace data, media, image/word/product collections, and assets | Workspace, collections, and assets |
| Automations | Slideshow, video, UGC, and X/Threads automation definitions and nested configuration | Automation definitions |
| Generation outputs | Runs, plans, results, slideshows, exports, and X/Threads drafts | Generation runs and outputs |
| Publishing and analytics | Social integrations, publications, calendar items, and metric snapshots | Publishing, calendar, and analytics |
| Operations and access | Jobs, usage ledger entries, workspace members, and demo metadata | Operations and access |
Reading the tables
- Optionality and allowed values are included in the field description.
- ISO timestamps use ISO 8601 strings, for example
2026-08-01T09:00:00.000Z. - Storage projections use
snake_case; domain objects normally usecamelCase. - Examples illustrate shape and format. They are not defaults unless the description says so.
- TypeScript definitions under
lib/remain the executable source of truth.
Architecture, routes, and local infrastructure remain separate because they describe system behavior rather than object fields: