@@ -292,7 +292,9 @@ marks and understand how they work.
292One further note on marks - while data from remote ships must have a matching
292One further note on marks - while data from remote ships must have a matching
293mark file in `/mar`, it's possible to exchange data between local agents with
293mark file in `/mar`, it's possible to exchange data between local agents with
294"fake" marks - ones that don't exist in `/mar`. Your `on-poke` arm could, for
294"fake" marks - ones that don't exist in `/mar`. Your `on-poke` arm could, for
295−example, use a made-up mark like `%foobar` for actions initiated locally.
295+example, use a made-up mark like `%foobar` for actions initiated locally. This
296+is because marks come into play only at validation boundries, none of which are
297+crossed when doing local agent-to-agent communications.
297## Permissions
299## Permissions