@@ -195,12 +195,16 @@ This represents a request for all changes between `from` and `to` on `path`. You
195will be notified when a change is made to the node referenced by the `path` or to
195will be notified when a change is made to the node referenced by the `path` or to
196any of its children.
196any of its children.
198−### `++care:clay`, Clay submode
198+### `$care:clay`, Clay submode
201− ++ care ?(%u %v %w %x %y %z) :: Clay submode
201+ +$ care ?(%a %b %c %d %e %f %p %r %s %t %u %v %w %x %y %z) :: clay submode
204+TODO: The rest of these. Ask Ted if there is any docs on them because a lot of
205+these (implemented with +read-X) are uncommented. Also need to check the ones
206+that are already here.
204This specifies what type of information is requested in a subscription
208This specifies what type of information is requested in a subscription
205or a scry.
209or a scry.
@@ -220,10 +224,39 @@ if `q:ankh` is null), then this produces null.
221`%z` requests the `++ankh` of the specified commit at the specfied path.
225`%z` requests the `++ankh` of the specified commit at the specfied path.
227+#### `$ankh`, filesystem node
230+ ++ ankh :: fs node (new)
231+ $: p=cash :: recursive hash
232+ q=(unit ,[p=cash q=*]) :: file
233+ r=(map ,@ta ankh) :: folders
236++$ ankh :: expanded node
238+ $: fil=(unit [p=lobe q=cage]) :: file
239+ dir=(map @ta ankh) :: folders
243+This is a single node in the filesystem. This may be file or a directory
244+or both. In Earth filesystems, a node is a file xor a directory. On
245+Mars, we're inclusive, so a node is a file ior a directory.
247+`fil` is the contents of this file, if any. `p.fil` is a hash of the
248+contents while `q.fil` is the data itself.
250+`dir` is the set of children of this node. In the case of a pure file,
251+this is empty. The keys are the names of the children and the values
252+are, recursively, the nodes themselves.
223−### `++arch`, shallow filesystem node
255+### `$arch`, shallow filesystem node
226 ++ arch ,[p=@uvI q=(unit ,@uvI) r=(map ,@ta ,~)] :: fundamental node
258 ++ arch ,[p=@uvI q=(unit ,@uvI) r=(map ,@ta ,~)] :: fundamental node
229This is analogous to `++ankh:clay` except that the we have neither our
262This is analogous to `++ankh:clay` except that the we have neither our
@@ -290,29 +323,6 @@ behaves exactly as you would expect.
290can only be applied to numbered commits. Labels must be unique across a
323can only be applied to numbered commits. Labels must be unique across a
293−#### `++ankh`, filesystem node
296− ++ ankh :: fs node (new)
297− $: p=cash :: recursive hash
298− q=(unit ,[p=cash q=*]) :: file
299− r=(map ,@ta ankh) :: folders
303−This is a single node in the filesystem. This may be file or a directory
304−or both. In earth filesystems, a node is a file xor a directory. On
305−mars, we're inclusive, so a node is a file ior a directory.
307−`p` is a recursive hash that depends on the contents of the this file or
308−directory and on any children.
310−`q` is the contents of this file, if any. `p.q` is a hash of the
311−contents while `q.q` is the data itself.
313−`r` is the set of children of this node. In the case of a pure file,
314−this is empty. The keys are the names of the children and the values
315−are, recursively, the nodes themselves.
317#### `++cash`, ankh hash
327#### `++cash`, ankh hash