8fc874c · urbit.org · git.iko.soy

git.iko.soy/urbit.org

on master help sign in

links: arvo.md

8fc874cdrbeefsupreme6 years ago

arvo/ames/ames-api.md+1−1

compare with master

unifiedsplit

@@ -189,7 +189,7 @@ Ames does not `give` a `gift` in response to a `%crud` `task`, but it does

189## `%init`

190

191`%init` is called a single time during the very first boot process, immediately

192−after the [larval stage](@/docs/tutorials/arvo/arvo.md#larval-stage-core)

192+after the [larval stage](@/docs/arvo/arvo.md#larval-stage-core)

193is completed. This initializes the vane. Jael is initialized first, followed by

194other vanes such as Ames.

195

arvo/ames/ames.md+1−1

@@ -28,7 +28,7 @@ vane or app, is defined in Ames.

28This section summarizes the design of Ames. Beyond this section are deeper

29elaborations on the concepts presented here.

31−Ames extends [Arvo's](@/docs/tutorials/arvo/arvo.md) `%pass`/`%give` `move` semantics across the network.

31+Ames extends [Arvo's](@/docs/arvo/arvo.md) `%pass`/`%give` `move` semantics across the network.

33Ames receives packets as Arvo events and emits packets as Arvo

34effects. The runtime is responsible for transferring the bytes in

arvo/dill/dill-api.md+3−3

@@ -68,7 +68,7 @@ Dill returns no `gift` in response to a `%blew` `task`.

68### `%boot`

70This `task` is used only once, when Arvo first enters the [adult

71−stage](@/docs/tutorials/arvo/arvo.md#structural-interface-core). Dill is

71+stage](@/docs/arvo/arvo.md#structural-interface-core). Dill is

72technically the first vane to be activated, via the `%boot` `task`, which then

73send Jael (considered the the "true" first vane) an `%init` `task`, which then goes on to

74call `%init` `task`s for other vanes (including Dill).

@@ -176,7 +176,7 @@ This `task` is not used.

176### `%init`

177

178This `task` is called only once, when Arvo first enters the [adult

179−stage](@/docs/tutorials/arvo/arvo.md#structural-interface-core). It performs

179+stage](@/docs/arvo/arvo.md#structural-interface-core). It performs

180initial setup for Dill, such as setting the width of the console.

181

182Note that this is not actually the first `task` passed to Dill - see [%boot](#%boot).

@@ -353,7 +353,7 @@ This `task` returns no `gift`s.

353

354This `task` toggles verbose mode for all of Arvo, which is located here since

355Dill is the vane that prints errors. To be precise, `%verb` toggles the laconic

356−bit `lac` in the [Arvo state](@/docs/tutorials/arvo/arvo.md#the-state).

356+bit `lac` in the [Arvo state](@/docs/arvo/arvo.md#the-state).

357

358#### Accepts

359

arvo/jael/jael-api.md+1−1

@@ -14,7 +14,7 @@ each `task` that Jael can be `%pass`ed, and which `gift`(s) Jael can `%give` in

15This `task` is called once per ship during the vane initialization

16phase immediately following the beginning of the [adult

17−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

17+stage](@/docs/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

18technical reasons, though we consider Jael to be the true "first" vane. This

19`task` is only used for ships that will join the Ames network - fake ships (i.e.

20made with `./urbit -F zod`) use the `%fake` `task` instead.

arvo/move-trace.md+5−5

@@ -7,7 +7,7 @@ template = "doc.html"

7In this tutorial we will run a simple "move trace" and use the output to get a

8picture of what the Arvo kernel proper does during the routine task of setting a

9timer. Some level of familiarity with the kernel is required for this section,

10−which can be obtained in our [Arvo kernel tutorial](@/docs/tutorials/arvo/arvo.md#the-kernel).

10+which can be obtained in our [Arvo kernel tutorial](@/docs/arvo/arvo.md#the-kernel).

12## Running a move trace

@@ -20,7 +20,7 @@ has elapsed.

20To follow along yourself, boot up a fake `~zod` and enter `|verb` into the dojo

21and press Enter to enable verbose mode (this is tracked by the laconic bit

22introduced in the section on [the

23−state](@/docs/tutorials/arvo/arvo.md#the-state)) in the kernel documentation, followed by `-time ~s1`

23+state](@/docs/arvo/arvo.md#the-state)) in the kernel documentation, followed by `-time ~s1`

24followed by Enter. Your terminal should pretty print a series of `move`s that looks something like this:

26```

@@ -105,7 +105,7 @@ arrow to Vane B, this represents either a `%pass` `note/task` sequence or a

105`%give` `gift/sign` sequence that actually has the Arvo kernel in the middle.

106That is to say, Vane A `%pass`es a `note` to the Arvo kernel addressed to Vane

107B, and the Arvo kernel then `%pass`es a `task` to Vane B. For more information,

108−see the [Arvo kernel tutorial](@/docs/tutorials/arvo/arvo.md#the-kernel).

108+see the [Arvo kernel tutorial](@/docs/arvo/arvo.md#the-kernel).

109

110This simple action ends up involving four vanes - Dill, Gall, Behn, and Ford -

111as well as four applications - hood, spider, dojo, and time.

@@ -118,7 +118,7 @@ This tells us that Unix has sent a `%belt` `card`, which corresponds to

118terminal input (the Enter keystroke) at time `~2020.1.14..19.01.25..7556`

119

120Here is the line of code in `arvo.hoon`, found in the [section

121−3bE core](@/docs/tutorials/arvo/arvo.md#section-3be-core), that generated the output:

121+3bE core](@/docs/arvo/arvo.md#section-3be-core), that generated the output:

122

123```hoon

124 ~? !lac ["" %unix -.q.ovo p.ovo now]

@@ -170,7 +170,7 @@ Here, Dill `%pass`es a `task` `card` saying to `%poke` Gall's hood app (with the

170Enter keystroke).

171

172Let's glance at part of the `+jack` arm in `arvo.hoon`, located in the [section 3bE

173−core](@/docs/tutorials/arvo/arvo.md#section-3be-core). This arm is what the Arvo kernel uses to send `card`s,

173+core](@/docs/arvo/arvo.md#section-3be-core). This arm is what the Arvo kernel uses to send `card`s,

174and here we look at the segment that includes `%pass` `move`s.

175

176```hoon