Home / The model / The lexicon / filesystem
filesystem
files and directories
A node carries no inherent meaning. What
filesystem means here emerges from the edges traceable from it, and confidence in that meaning is proportional to how richly it is connected. It is connected to 6 of 23 primitives here. That, and not the sentence above, is what it means. The discipline this follows.The 6 primitives with this family
| Primitive | Published gloss | Spelled out | Undo | In how many shapes |
|---|---|---|---|---|
delete.file.host | Delete files anywhere the account can reach | delete.file.host | no | 5 of 17 |
read.file.host | Read any file the account can reach | read.file.host | no | 11 of 17 |
read.file.project | Read the project it is working on | read.file.project | yes | 7 of 17 |
read.record.history | Read a retained record: shell history, past sessions | read.record.host | no | 8 of 17 |
write.file.host | Change any file the account can reach | write.file.host | with-effort | 8 of 17 |
write.file.project | Change the project it is working on | write.file.project | with-effort | 6 of 17 |
How this node connects
| Edge | Reads as | To |
|---|---|---|
family_of | filesystem is the family of these 6 primitives | 6 capabilities |
in_family | the inverse, walked the other way, with different fan out | one capability at a time |