@@ -149,3 +149,26 @@ The body is of variable length and consists of three parts in this order:
149149
150150 The sender and receiver live outside of the jammed data section to simplify
151151 packet filtering for the interpreter.
152+
153+
154+## Journey of a Packet
155+
156+In this section we follow a packet through its entire journey, originating from
157+the Ames vane of ship A and ending in the Ames vane of ship B.
158+
159+This journey is broken into several stages:
160+
161+1. Ames receives a `%plea` note.
162+1.5 Does encryption happen here?
163+2. Serf A gives the note to King A (in what form? does it jam the payload?)k
164+3. King A checks that it is a valid Ames packet and wraps the Ames packet in a UDP packet (what does this look like?) and
165+ give it to its Ames I/O submodule to send
166+4. UDP packet is sent to the receiving IP address (how is this determined? along
167+ some port?)
168+5. King B receives a UDP packet on socket ? via the Ames submodule. It checks
169+ that it is a valid Ames packet
170+
171+
172+A `%plea` `note` is given by `[vane=@tas =path payload=*]`, where
173+`vane` is the destination vane on the remote ship, `path` is the internal
174+route on the receiving ship `payload` is the semantic message content.