@@ -144,7 +144,7 @@ The simplest way to handle a `%poke-ack` by passing it to `default-agent`'s
144144`on-agent` arm, which will just print an error message to the terminal if it's a
145145nack, and otherwise do nothing. Sometimes you'll want your agent to do something
146146different depending on whether the poke failed or succeeded (and therefore
147−whether it's a nack or an ack). In that case, you'd typically first test the
147+whether it's a nack or an ack). As stated in the [Precepts](/docs/development/precepts#specifics): "Route on wire before sign, never sign before wire.". Thus we first test the
148148`wire` so you can tell what the `%poke-ack` was for. You might do something
149149like:
150150
@@ -384,7 +384,7 @@ rather that updating its own state, it sends two pokes to `%pokeme`, so
384384 ?+ wire (on-agent:def wire sign)
385385 [%inc ~]
386386 ?. ?=(%poke-ack -.sign)
387− (on-agent wire sign)
387+ (on-agent:def wire sign)
388388 ?~ p.sign
389389 %- (slog '%pokeit: Increment poke succeeded!' ~)
390390 `this
@@ -393,7 +393,7 @@ rather that updating its own state, it sends two pokes to `%pokeme`, so
393393 ::
394394 [%dec ~]
395395 ?. ?=(%poke-ack -.sign)
396− (on-agent wire sign)
396+ (on-agent:def wire sign)
397397 ?~ p.sign
398398 %- (slog '%pokeit: Decrement poke succeeded!' ~)
399399 `this