In a nutshell,
- ultimately Hook links individual resources bidirectionally. However, Hook enables users to quickly create a network (mesh or hub and spoke). But Hook does not maintain a model of the network.
- Hook can also generate URI’s, with the hook:// scheme. Those URI’s are unidirectional, in that Hook does not track where you use them. But once you have created the URI, Hook will serve them.
(Of course, Hook also enables users to get the URI of resources that have their own URI scheme, such as https:// and OmniFocus:// . The design principle there is: if there is an existing scheme that meets the requirements of Hook, Hook will use that. The file:// scheme does not meet our requirements, which is why we invented hook://file (“file” here is a scheme extension).
As noted elsewhere, Hook also can apply Finder tags, but those tags are not used by Hook at the moment.
Hook is designed to fill a tight cluster of requirements that no other app has addressed. We’re currently extending documentation, which I hope will help.