Canonical user data
Derived / disposable
Future / separate durable data
Why not canonical SQLite for views?
A live SQLite file is awkward to sync through object storage (S3 / Google Drive) because conflicts happen at the whole-file level. Zorid view definitions are readable, sync-friendly, conflict-detected text files instead.Embedding views
Markdown uses normal embed syntax with the vault-relative.zbase path:
.zorid/views/ is only the default creation location. Users may store .zbase files anywhere in the vault:
Storage diagram
Source
Full storage model on GitHub.