@@ -14,11 +14,25 @@ each `task` that Jael can be `%pass`ed, and which `gift`(s) Jael can `%give` in
1414
1515### `%dawn`
1616
17−This `task` is called only a single time per ship during the vane initialization
17+This `task` is called once per ship during the vane initialization
1818phase immediately following the beginning of the [adult
19−stage](@/docs/tutorials/arvo/arvo.md#structural-interface-core) to load Azimuth information such as private keys and the sponsor into
20−Jael. This `task` is `%pass`ed to Jael by Dill, as Dill is the first vane to be loaded for
21−technical reasons, though we consider Jael to be the true "first" vane.
19+stage](@/docs/tutorials/arvo/arvo.md#structural-interface-core). This `task` is `%pass`ed to Jael by Dill, as Dill is the first vane to be loaded for
20+technical reasons, though we consider Jael to be the true "first" vane. This
21+`task` is only used for ships that will join the Ames network - fake ships (i.e.
22+made with `./urbit -F zod`) use the `%fake` `task` instead.
23+
24+`%dawn` is used to perform a sequence of initialization tasks related to saving
25+information about Azimuth and the Ames network and booting other vanes for the first time. Upon
26+receipt of a `%dawn` `task`, Jael will:
27+ - record the Ethereum block the public key is registered to,
28+ - record the URL of the Ethereum node used,
29+ - save the signature of the parent planet (if the ship is a moon)
30+ - load the initial public and private keys for the ship
31+ - set the DNS suffix(es) used by the network (currently just `arvo.network`)
32+ - save the public keys of all galaxies
33+ - set Jael to subscribe to `%azimuth-tracker`
34+ - `%slip` a `%init` `task` to Ames, Clay, Gall, Dill, and Eyre, and `%give` an `%init`
35+`gift` to Unix??.
2236
2337#### Accepts
2438
@@ -36,16 +50,29 @@ technical reasons, though we consider Jael to be the true "first" vane.
3650```
3751
3852The `seed` is `[who=ship lyf=life key=ring sig=(unit oath:pki)]`. `who` is the
39−`@p` of the ship running the `task`, `lyf` is the current ship key revision, `key`
53+`@p` of the ship running the `task`, `lyf` is the current ship key revision,
54+`key` is the ship's private key, and `sig` is the signature of the ship's parent
55+planet if the ship is moon and `[~]` otherwise.
4056
57+`spon` is a `list` of ships and their `point`s in the ship's sponsorship chain,
58+all the way to the galaxy level. `point:azimuth-types` contains all Azimuth
59+related data and can be found in `zuse.hoon`.
4160
42−`spon` is a list (why?) of sponsors for the ship, `czar` is a map of ships you
43−know to their rift, life, and public key?
61+`czar` is a map from each galaxy's `@p` to its `rift`, `life`, and public key (`pass`).
4462
45−`turf` is a `(list @t)` ":: domain, tld first" ?? something to do with DNS?
63+`turf` is a `list` of DNS suffixes used by the Ames network, which for now is
64+just `arvo.network`.
65+
66+`bloq` is the number of the Ethereum block in which the ship registered its keys
67+with the Azimuth smart contract.
68+
69+`node` is the URL of the Ethereum node used to register the ship's keys with Azimuth.
4670
4771#### Returns
4872
73+As mentioned above, this `task` `%slip`s `%init` `task`s to most other vanes and
74+`%give`s an `%init` `gift` to Unix.
75+
4976
5077### `%fake`
5178