@@ -172,3 +172,51 @@ This journey is broken into several stages:
172172A `%plea` `note` is given by `[vane=@tas =path payload=*]`, where
173173`vane` is the destination vane on the remote ship, `path` is the internal
174174route on the receiving ship `payload` is the semantic message content.
175+
176+
177+### Notes
178+
179+%plea must trigger some kind of gift, most likely %send, but i can't seem to
180+fucking find where!
181+
182+%plea comes in.
183+
184++call is called, which triggers +on-plea:event-core
185+
186++on-plea calls +on-memo:make-peer-core
187+
188++on-memo returns a peer-core and makes a peer-core via (run-message-pump bone
189+%memo message-blob)
190+
191+run-message-pump (also an arm of make-peer-core)
192+
193+
194+SOMEWERE GIFTS ARE DEFINED. WHAT GIFT IS
195+
196+gift is an alias for i.pump-gifts
197+pump-gifts is assigned to be the head of (work:message-pump task)
198+message-pump is a face for (make-message-pump message-pump-state channel)
199+message-pump-state is the face for something create by gut
200+
201+
202+gifts are defined somewhere in here i think
203+```hoon
204+ ++ work
205+ |= task=message-pump-task
206+ ^+ [gifts state]
207+ ::
208+ =~ (dispatch-task task)
209+ feed-packets
210+ (run-packet-pump %halt ~)
211+ assert
212+ [(flop gifts) state]
213+ ==
214+```
215+
216+dispatch-task fork on %memo and calls on-memo:message-pump, which adds the
217+message to unsent-messages.state
218+
219+feed-packets calls process-packet-pump-gifts, which takes in a list of
220+packet-pump-gifts. this seems to come from res? =/ res (feed:packet-pump unsent-fragments.state)
221+
222+ and feed:packet-pump seems to call %send! finally