- key-val mappings to be stored in a repo with a light weight object store but lots of branches - actual data objects to be stored in another repo with no refs but lots of detached commits - key-val mapping basically maps keyIds to redirect commits (see #27) which are lightweight, all redirect commits sharing the same tree object - data store may be public, providing CDN access and permanent caching by JSDelivr - key-val repo may be private keeping the mappings or relations private - key-val store being lightweight easily cloned and mirrored periodically for backup - even if github goes down, data is retrieved using key-val repo mirror and CDN for data store
