@@ -144,7 +144,7 @@ The simplest way to handle a `%poke-ack` by passing it to `default-agent`'s
144`on-agent` arm, which will just print an error message to the terminal if it's a
144`on-agent` arm, which will just print an error message to the terminal if it's a
145nack, and otherwise do nothing. Sometimes you'll want your agent to do something
145nack, and otherwise do nothing. Sometimes you'll want your agent to do something
146different depending on whether the poke failed or succeeded (and therefore
146different 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
148`wire` so you can tell what the `%poke-ack` was for. You might do something
148`wire` so you can tell what the `%poke-ack` was for. You might do something
@@ -384,7 +384,7 @@ rather that updating its own state, it sends two pokes to `%pokeme`, so
384 ?+ wire (on-agent:def wire sign)
384 ?+ wire (on-agent:def wire sign)
386 ?. ?=(%poke-ack -.sign)
386 ?. ?=(%poke-ack -.sign)
387− (on-agent wire sign)
387+ (on-agent:def wire sign)
388 ?~ p.sign
388 ?~ p.sign
389 %- (slog '%pokeit: Increment poke succeeded!' ~)
389 %- (slog '%pokeit: Increment poke succeeded!' ~)
@@ -393,7 +393,7 @@ rather that updating its own state, it sends two pokes to `%pokeme`, so
395 ?. ?=(%poke-ack -.sign)
395 ?. ?=(%poke-ack -.sign)
396− (on-agent wire sign)
396+ (on-agent:def wire sign)
397 ?~ p.sign
397 ?~ p.sign
398 %- (slog '%pokeit: Decrement poke succeeded!' ~)
398 %- (slog '%pokeit: Decrement poke succeeded!' ~)