@@ -10,16 +10,17 @@ and _rift_. This numbering system partition messages according to the quantity
10of networking key changes and quantity of
10of networking key changes and quantity of
11[breaches](@/using/id/guide-to-breaches.md), respectively. This is explained in
11[breaches](@/using/id/guide-to-breaches.md), respectively. This is explained in
12more detail below. These values are utilized by [Ames](@/docs/arvo/ames/ames.md)
12more detail below. These values are utilized by [Ames](@/docs/arvo/ames/ames.md)
13−and [Jael](@/docs/arvo/jael/jael-api.md) to ensure that you are communicating
13+and [Jael](@/docs/arvo/jael/jael-api.md) to ensure that communication between
14−with a ship using its most recent set of keys.
14+ships is always done with the most recent set of networking keys, and that
15+networking state is appropriately reset when a breach has occurred.
16Before it has been spawned, every ship begin with a `life` and `rift` of 0. For
17Before it has been spawned, every ship begin with a `life` and `rift` of 0. For
17galaxies, stars, and planets, these values are stored in the Azimuth PKI, while
18galaxies, stars, and planets, these values are stored in the Azimuth PKI, while
18for moons, these values are stored by their parent. Comets cannot change their
19for moons, these values are stored by their parent. Comets cannot change their
19networking keys, nor can they breach, and so their `life` and `rift` are always 0.
20networking keys, nor can they breach, and so their `life` and `rift` are always 0.
21−You can check your current life and rift number by running the `+keys our`
22+You can check your current `life` and `rift` number by running the `+keys our`
22−generator in dojo. You can inspect another ship's life and rift by running
23+generator in dojo. You can inspect another ship's `life` and `rift` by running
23`+keys ~sampel-palnet`.
24`+keys ~sampel-palnet`.