flancian/garden
0
0
Fork 0
mirror of https://github.com/flancian/garden.git synced 2026-08-10 16:36:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

autopushed

Browse Source
This commit is contained in:
Flancian
2022-08-20 18:50:30 +02:00
parent a646ba80b6
commit 359ae0f8dd
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agora pkg chapter.md
+3 -1
View File
@@ -108,7 +108,9 @@ On a pragmatic level:
- [[Optimistic linking]] is encouraged. - [[Optimistic linking]] is encouraged.
- Links that lead nowhere (currently) are encouraged. - Links that lead nowhere (currently) are encouraged.
- In an Agora, the place they lead to by default includes resources written by others. - In an Agora, the place they lead to by default includes resources written by others.
- [[Outlines]] or [[Agora trees]], as encoded by nested lists such as this one, are parsed in an Agora by default as declaring [[heterarchies]] of [[intents]] or [[assertions]]. - [[Outlines]] or [[Agora trees]], as encoded by nested lists such as this one, might be parsed by default as declaring [[heterarchies]][^heterarchy].
[^heterarchy]: an Agora is a repository of heterarchies.
When interpreting the above and extensions, an Agora is liberal in what it accepts and when in doubt tries to default to being extra useful to the user -- meaning it is optimistic in association and surfaces all resources that have a claim to be associated with the context being served. For example: #CamelCase will be provided in all contexts matching [[camel case]] and all known variations, and this relationship is symmetric by default, in the sense that the user might provide either at write time and be later served matching resources in either context. When interpreting the above and extensions, an Agora is liberal in what it accepts and when in doubt tries to default to being extra useful to the user -- meaning it is optimistic in association and surfaces all resources that have a claim to be associated with the context being served. For example: #CamelCase will be provided in all contexts matching [[camel case]] and all known variations, and this relationship is symmetric by default, in the sense that the user might provide either at write time and be later served matching resources in either context.