@@ -69,9 +69,15 @@ containing useful functions for use by the agent arms. Such a helper core would
69typically contain functions that would only ever be used internally by the
69typically contain functions that would only ever be used internally by the
70agent - more general functions would usually be included in a separate `/lib`
70agent - more general functions would usually be included in a separate `/lib`
71library and imported with a [faslus](/docs/arvo/ford/ford#ford-runes) (`/+`)
71library and imported with a [faslus](/docs/arvo/ford/ford#ford-runes) (`/+`)
72−rune.
72+rune. Additionally, you might recall that the example agent of the
73−
73+[subscriptions lesson](/docs/userspace/gall-guide/8-subscriptions#example) used
74+a barket (`|^`) rune to create a door in the `on-poke` arm with a separate
75+`handle-poke` arm. That approach is typically used when functions will only be
76+used in that one arm. The helper core, on the other hand, is useful when
77+functions will be used by multiple agent arms.
74−The conventional pattern is to have the helper core _below_ the agent core, so the structure of the agent file is like:
79+The conventional pattern is to have the helper core _below_ the agent core, so
80+the structure of the agent file is like: