@@ -24,8 +24,8 @@ approach is to define a head-tagged union of all possible poke types the agent
24will accept, and another for all possible updates it might send out to
24will accept, and another for all possible updates it might send out to
25subscribers. Rather than defining these types in the agent itself, you would
25subscribers. Rather than defining these types in the agent itself, you would
26typically define them in a separate core saved in the `/sur` directory of the
26typically define them in a separate core saved in the `/sur` directory of the
27−desk. The `/sur` directory is short for "**s**truct**ur**es", and is the
28−canonical location for userspace type definitions.
27+desk. The `/sur` directory is the canonical location for userspace type
30With this approach, your agent can simply import the structures file and make use
30With this approach, your agent can simply import the structures file and make use
31of its types. Additionally, if someone else wants to write an agent that
31of its types. Additionally, if someone else wants to write an agent that
@@ -392,8 +392,8 @@ Permissions:
392 of the `bowl` with the `@p`.
392 of the `bowl` with the `@p`.
393- Permissions are most commonly enforced with wutgar (`?>`) and wutgal (`?<`)
393- Permissions are most commonly enforced with wutgar (`?>`) and wutgal (`?<`)
394 assertions in the relevant agent arms.
394 assertions in the relevant agent arms.
395−- Messages can be restricted to the local ship with `?> =(src.bowl our.bowl)` or to
395+- Messages can be restricted to the local ship with `?> =(src.bowl our.bowl)` or to
396− its moons as well with `?> (team:title our.bowl src.bowl)`.
396+ its moons as well with `?> (team:title our.bowl src.bowl)`.
397- There are many other ways to handle permissions, it just depends on the needs
397- There are many other ways to handle permissions, it just depends on the needs
398 of the particular agent.
398 of the particular agent.