@@ -441,25 +441,27 @@ associated with those hashes.
442`busy` tracks whether or not the request is currently being fulfilled.
442`busy` tracks whether or not the request is currently being fulfilled.
444−#### `++rang:clay`, data store
444+#### `$rang:clay`, data repository
447+ +$ rang :: repository
447− ++ rang $: hut=(map tako yaki) ::
448+ $: hut=(map tako yaki) :: changes
448− lat=(map lobe blob) ::
449+ lat=(map lobe blob) :: data
452−This is a set of data keyed by hash. Thus, this is where the "real" data
453+This is a data repository keyed by hash. Thus, this is where the "real" data
453is stored, but it is only meaningful if we know the hash of what we're
454is stored, but it is only meaningful if we know the hash of what we're
454looking for.
455looking for.
456−`hut` is a map from hashes to commits. We often get the hashes from
457+`hut` is a `map` from commit hashes (`tako`s) to commits (`yaki`s). We often get
457−`hit:dome:clay`, which keys them by logical id. Not every commit has an id.
458+the hashes from `hit:dome`, which keys them by numerical id. Not every commit
459−`lat` is a map from hashes to the actual data. We often get the hashes
461+`lat` is a `map` from content hashes (`lobe`s) to the actual content (`blob`s).
460−from a `++yaki`, a commit, which references this map to get the data.
462+We often get the hashes from a `yaki`, which references this `map` to get the
461−There is no `++blob:clay` in any `++yaki:clay`. They are only accessible through
463+data. There is no `blob` in `yaki:clay`. They are only accessible through
464#### `++tako:clay`, commit reference
466#### `++tako:clay`, commit reference