a333d01 · urbit.org · git.iko.soy

arvo/ames/ames.md+1−1

compare with master

unifiedsplit

@@ -386,7 +386,7 @@ until one of them changes their IP address, port, or networking keys.

386

387Urbit's functionality is split between the two binaries `urbit-worker` (sometimes

388called the Serf) and `urbit-king` (sometimes called the King). This division of

389−labor is currently not well-documented outside of the [Vere documents](@/docs/tutorials/vere/_index.md), but we summarize it here.

389+labor is currently not well-documented outside of the [Vere documents](@/docs/vere/_index.md), but we summarize it here.

390

391In short, the Serf is the Nock runtime and so keeps track of the current state

392of Arvo as a Nock noun and updates the state by `%poke`ing it with nouns, and

arvo/arvo.md+2−2

@@ -127,7 +127,7 @@ The formal state of an Arvo instance is an event history, as a linked list of [n

127

128The Arvo event log is a list of every action ever performed on your ship that

129lead up to the current state. In principle, this event log is maintained by the

130−[Nock runtime environment](@/docs/tutorials/vere/_index.md), but in practice

130+[Nock runtime environment](@/docs/vere/_index.md), but in practice

131event logs become too long over time to keep, as the event log has a size of

132O(n) where n is the number of events. Thus it is our intention to

133implement a feature whereby periodic snapshots of the state of Arvo are taken

@@ -207,7 +207,7 @@ Database theory studies in precise terms the possible properties of anything tha

207 Arvo

208 transactions are sequential and performed by the daemon, persistence and effect application are performed

209 in parallel by the worker; see [worker and

210− daemon](@/docs/tutorials/vere/_index.md) for more detail.

210+ daemon](@/docs/vere/_index.md) for more detail.

211

212 - Durability: Completed transactions will survive permanently. In other words,

213 since the event log is stored on disk, if power is lost you are guaranteed

glossary/jaque.md+1−1

@@ -12,4 +12,4 @@ The current worker utilized by Vere is written in C, while Jaque is written usin

12

13### Further Reading

14

15−- [The Vere tutorial](@/docs/tutorials/vere/_index.md): Learning information for Vere.

15+- [The Vere tutorial](@/docs/vere/_index.md): Learning information for Vere.

glossary/replay.md+1−1

@@ -10,4 +10,4 @@ category = "arvo"

10

11### Further Reading

12

13−- [The Vere tutorial](@/docs/tutorials/vere/_index.md): An in-depth technical guide to Vere.

13+- [The Vere tutorial](@/docs/vere/_index.md): An in-depth technical guide to Vere.

glossary/vere.md+1−1

@@ -15,4 +15,4 @@ Vere consists of two processes that communicate via a socket: a daemon process i

15### Further Reading

16

17- [The Technical Overview](@/docs/tutorials/concepts/technical-overview.md)

18−- [The Vere tutorial](@/docs/tutorials/vere/_index.md): An in-depth technical guide to Vere.

18+- [The Vere tutorial](@/docs/vere/_index.md): An in-depth technical guide to Vere.

nock/implementations.md+1−1

@@ -34,7 +34,7 @@ We use a C implementation for our Nock interpreter. But building a Nock interpre

34

35The actual production Nock interpreter. Note gotos for tail-call elimination,

36and manual reference counting. More about the C environment can be found

37−in the [runtime system documentation](@/docs/tutorials/vere/runtime.md).

37+in the [runtime system documentation](@/docs/vere/runtime.md).

38```

39/* _n_nock_on(): produce .*(bus fol). Do not virtualize.

40*/

vere/_index.md+4−4

@@ -11,12 +11,12 @@ Keep reading if you're planning to work on the Urbit interpreter, you're a

11language implementation geek, or you don't really understand anything until

12you've seen the actual structs.

13

14−## [C runtime system](@/docs/tutorials/vere/runtime.md)

14+## [C runtime system](@/docs/vere/runtime.md)

15

16The Urbit interpreter is built on a Nock runtime system written

17in C, `u3`. This section is a relatively complete description.

18

19−## [c3: C in Urbit](@/docs/tutorials/vere/c.md)

19+## [c3: C in Urbit](@/docs/vere/c.md)

20

21Under `u3` is the simple `c3` layer, which is just how we write C

22in Urbit.

@@ -27,10 +27,10 @@ The division between `c3` and `u3` is that you could theoretically

27imagine using `c3` as just a generic C environment. Anything to do

28with nouns is in `u3`.

29

30−## [u3: API overview by prefix](@/docs/tutorials/vere/api.md)

30+## [u3: API overview by prefix](@/docs/vere/api.md)

31

32A walkthrough of each of the `u3` modules.

33

34−## [How to write a jet](@/docs/tutorials/vere/jetting.md)

34+## [How to write a jet](@/docs/vere/jetting.md)

35

36A jetting guide by for new Urbit developers.