39cf2ed · urbit.org · git.iko.soy

glossary/aqua.md+1−1

compare with master

unifiedsplit

@@ -13,4 +13,4 @@ Aqua is jetted with the usual [Nock](../nock) interpreter and thus virtual ships

13

14### Further Reading

15

16−- [The Gall tutorial](@/docs/tutorials/arvo/gall.md): An technical guide to the Gall vane.

16+- [The Gall tutorial](@/docs/tutorials/arvo/gall.md): A technical guide to the Gall vane.

glossary/atom.md+3−3

@@ -8,11 +8,11 @@ category = "hoon-nock"

8An **atom** is any non-negative integer of any size. The atom is the most basic data type in [Nock](../nock) and [Hoon](../hoon).

9

10A Hoon atom type consists of a Nock atom with two additional pieces of metadata: an [aura](../aura) and an optional constant. A Hoon atom type is _warm_ or _cold_ based on whether or not the constant exists:

11−* An Hoon atom type is **warm** if the constant is `~` (null), any atom is in the type.

11+* A Hoon atom type is **warm** if the constant is `~` (null), any atom is in the type.

12−* An Hoon atom type is **cold** if the constant is `[~ atom]`, its only legal value is atom.

12+* A Hoon atom type is **cold** if the constant is `[~ atom]`, its only legal value is atom.

13

14### Further Reading

15

16- [The Hoon Tutorial](@/docs/tutorials/hoon/_index.md): Our guide to learning the Hoon programming language.

17− - [Lesson 1.2: Nouns](@/docs/tutorials/hoon/nouns.md): An Hoon Tutoral lesson that explains how atoms work.

17+ - [Lesson 1.2: Nouns](@/docs/tutorials/hoon/nouns.md): A Hoon Tutoral lesson that explains how atoms work.

18- [The Nock explanation](@/docs/tutorials/nock/explanation.md): Includes an explanation of atoms.

glossary/behn.md+1−1

@@ -11,4 +11,4 @@ Behn is located in `/home/sys/vane/behn.hoon` within [Arvo](../arvo).

11

12### Further Reading

13

14−- [The Behn tutorial](@/docs/tutorials/arvo/behn.md): An technical guide to the Behn vane.

14+- [The Behn tutorial](@/docs/tutorials/arvo/behn.md): A technical guide to the Behn vane.

glossary/chat.md+1−1

@@ -8,7 +8,7 @@ category = "arvo"

8

9**Chat**, also referred to as `:chat-cli`, is an application that handles communication between ships.

10

11−There are four types of chats (lowercase) Each is a named collection of messages created by and hosted on a ship's [Hall](../hall), usually represented as `~ship-name/circle-name`. Most of Chat revolves around doing things with these chats.

11+There are four types of chats (lowercase). Each is a named collection of messages created by and hosted on a ship's [Hall](../hall), usually represented as `~ship-name/circle-name`. Most of Chat revolves around doing things with these chats.

12

13Circles are subscribed to by some number of ships which are permitted to post and retrieve messages from the circle.

14

glossary/clay.md+1−1

@@ -15,4 +15,4 @@ Clay is located at `/home/sys/vane/clay.hoon` within Arvo.

15### Further Reading

16

17- [Using Your Ship](@/using/operations/using-your-ship.md#filesystem): A user guide that includes instructions on using Clay.

18−- [The Clay tutorial](@/docs/tutorials/arvo/clay.md): An technical guide to the Clay vane.

18+- [The Clay tutorial](@/docs/tutorials/arvo/clay.md): A technical guide to the Clay vane.

glossary/dill.md+1−1

@@ -19,4 +19,4 @@ Dill is located at `/home/sys/vane/dill.hoon` within [Arvo](../arvo).

19

20### Further Reading

21

22−- [The Dill tutorial](@/docs/tutorials/arvo/dill.md): An technical guide to the Dill vane.

22+- [The Dill tutorial](@/docs/tutorials/arvo/dill.md): A technical guide to the Dill vane.

glossary/ecliptic.md−4

@@ -9,7 +9,3 @@ category = "azimuth"

9The **Ecliptic** contract sets the rules for what is and is not possible on Azimuth. It's the point of entry for interacting with the [Azimuth](../azimuth) ledger data; the Azimuth contract itself is just data, and the Ecliptic contract is the logic for controlling that data. Examples of such logic include verifying permissions of the person asking to access their data, and ensuring a requested change is actually valid.

10

11The Senate (the voting body of [galaxies](../galaxy)) has the power to replace Ecliptic.

12−

13−### Further Reading

14−

15−- [The Dill tutorial](@/docs/tutorials/arvo/behn.md): An technical guide to the Dill van.

glossary/eventlog.md+1−1

@@ -12,7 +12,7 @@ The event log is maintained by [Vere](../vere).

12

13If the physical machine loses power and your urbit's state is 'lost' from memory, when your urbit restarts it will replay its entire event log and recover its last valid state from scratch.

14

15−In practice event logs become large and unwieldy over time. Periodically a snapshot of the permanent state is taken and the logs are pruned. You're still able to rebuild your state in case of power outage down to the last keystroke. This is due to the practice of persistence.

15+In practice, event logs become large and unwieldy over time. Periodically a snapshot of the permanent state is taken and the logs are pruned. You're still able to rebuild your state in case of power outage down to the last keystroke. This is due to the practice of persistence.

16

17Persistence, in the context of storing data in a computer system, means that data is stored in a non-volatile manner and that input must be recorded before the output result is performed. Thus, every event must be written to disk - or must be _persisted_ - before the event effects actually take place.

18

glossary/eyre.md+1−1

@@ -14,4 +14,4 @@ Eyre is located at `/home/sys/vane/eyre.hoon` within [Arvo](../arvo).

14

15### Further Reading

16

17−- [The Eyre tutorial](@/docs/tutorials/arvo/eyre.md): An technical guide to the Eyre vane.

17+- [The Eyre tutorial](@/docs/tutorials/arvo/eyre.md): A technical guide to the Eyre vane.

glossary/ford.md+1−1

@@ -14,4 +14,4 @@ Ford is located at `/home/sys/vane/ford.hoon` within [Arvo](../arvo).

14

15### Further Reading

16

17−- [The Ford tutorial](@/docs/tutorials/arvo/ford.md): An technical guide to the Ford vane.

17+- [The Ford tutorial](@/docs/tutorials/arvo/ford.md): A technical guide to the Ford vane.

glossary/galaxy.md+1−1

@@ -8,7 +8,7 @@ category = "arvo"

8

9A **galaxy** is can be one of two related things:

10

11−- A kind of [Azimuth](../azimuth) Urbit identity that sits at the top of the identity hierarchy. Stars, in this sense, have the power to issue [stars](../moon), meaning that all other kinds of identities ultimate derive from stars. Galaxies also form a [Senate](../senate), the governing body of Azimuth. The Senate has the power to update the logic of Azimuth by [majority vote](../voting).

11+- A kind of [Azimuth](../azimuth) Urbit identity that sits at the top of the identity hierarchy. Galaxies, in this sense, have the power to issue [stars](../star), meaning that all other kinds of identities ultimate derive from galaxies. Galaxies also form a [Senate](../senate), the governing body of Azimuth. The Senate has the power to update the logic of Azimuth by [majority vote](../voting).

12

13- A [ship](../ship) on the Arvo network whose identity is a planet in the former definition. In this sense, galaxies act as infrastructure for the [Arvo](../arvo) network, providing [Ames](../ames)-related services, such as peer-to-peer routing and distributing [over-the-air software updates](../ota-updates). Stars rely on galaxies for these services in the way that planets rely on stars.

14

glossary/gall.md+2−2

@@ -13,5 +13,5 @@ Gall is located at `/home/sys/vane/gall.hoon` within Arvo.

13### Further Reading

14

15- [The Hoon Tutorial](@/docs/tutorials/hoon/_index.md): Our guide to learning the Hoon programming language that will give you the foundation necessary for app development.

16− - [Lesson 2.7: Gall](@/docs/tutorials/hoon/gall.md): An Hoon Tutorial lesson that explains how to write simple Gall app.

16+ - [Lesson 2.7: Gall](@/docs/tutorials/hoon/gall.md): A Hoon Tutorial lesson that explains how to write a simple Gall app.

17−- [The Gall tutorial](@/docs/tutorials/arvo/gall.md): An technical guide to the Gall vane.

17+- [The Gall tutorial](@/docs/tutorials/arvo/gall.md): A technical guide to the Gall vane.

glossary/mark.md+2−2

@@ -13,5 +13,5 @@ The [Ford](../ford) [vane](../vane) converts data between marks and validates da

13

14### Further Reading

15

16−- [The Clay tutorial](@/docs/tutorials/arvo/clay.md): An technical guide to the Clay vane.

16+- [The Clay tutorial](@/docs/tutorials/arvo/clay.md): A technical guide to the Clay vane.

17−- [The Ford tutorial](@/docs/tutorials/arvo/ford.md): An technical guide to the Ford vane.

17+- [The Ford tutorial](@/docs/tutorials/arvo/ford.md): A technical guide to the Ford vane.

glossary/modulo.md+2−2

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

10

11### Further Reading

12

13−- [Lesson 2.7: Gall](@/docs/tutorials/hoon/gall.md): An Hoon Tutorial lesson that explains how to write simple tile.

13+- [Lesson 2.7: Gall](@/docs/tutorials/hoon/gall.md): A Hoon Tutorial lesson that explains how to write simple tile.

14−- [The Gall tutorial](@/docs/tutorials/arvo/gall.md): An technical guide to the Gall van.

14+- [The Gall tutorial](@/docs/tutorials/arvo/gall.md): A technical guide to the Gall van.

glossary/ota-updates.md−6

@@ -7,9 +7,3 @@ category = "arvo"

7+++

8

9[Ships](../ship) have the ability to upgrade themselves **over the air**. They receive updates from a sponsor [star](../star) or [galaxy](../galaxy).

10−

11−### Further Reading

12−

13−- [The Hoon Tutorial](@/docs/tutorials/hoon/_index.md): Our guide to learning the Hoon programming language.

14− - [Lesson 1.2: Nouns](@/docs/tutorials/hoon/nouns.md): A Hoon Tutoral lesson that explains how nouns work.

15−- [The Nock explanation](@/docs/tutorials/nock/_index.md): Includes a low-level explanation of nouns.

glossary/pill.md+1−3

@@ -11,6 +11,4 @@ A **Pill** is a bootstrap sequence to launch an Urbit ship for the first time. T

11A Pill consists of three ordered lists:

12 * A list of events which are interpreted by Nock to create an [Arvo](../arvo) kernel.

13 * A list of Arvo events to run once the Arvo kernel is created.

14− * A list of userspace events to run once the Arvo events have been run. Currently, this consists of setting up the file system [Clay](../clay).

14+ * A list of userspace events to run once the Arvo events have been run. Currently, this consists of setting up the [Clay](../clay) file system.

15−

16−

glossary/senate.md+1−1

@@ -6,4 +6,4 @@ template = "doc.html"

6category = "azimuth"

7+++

8

9−The **Galactic Senate** is the body of all [galaxies](../galaxy) that governs [Azimuth](../azimuth) by [majority vote](../voting). There are two types of votes: a [constitution vote](../constitution), which is a motion to update the logic of Azimuth; and a [documentation vote](../docvote), which is a motion to legitimize or approve the content of an arbitrary document.

9+The **Galactic Senate** is the body of all [galaxies](../galaxy) that governs [Azimuth](../azimuth) by [majority vote](../voting). There are two types of votes: a constitution vote, which is a motion to update the logic of Azimuth; and a [documentation vote](../docvote), which is a motion to legitimize or approve the content of an arbitrary document.

glossary/star.md+2−2

@@ -10,8 +10,8 @@ A **star** is the kind of Urbit identity that sits between the [galaxy](../galax

10

11A **star** is can be to one of two related things:

12

13−- A kind of [Azimuth](../azimuth) Urbit identity that sits between the [galaxy](../galaxy) and [planets](../planet) in the identity hierarchy. Stars, in this sense, have the power to issue [planets](../moon), and are themselves are issued by galaxies.

13+- A kind of [Azimuth](../azimuth) Urbit identity that sits between the [galaxy](../galaxy) and [planets](../planet) in the identity hierarchy. Stars, in this sense, have the power to issue [planets](../planet), and are themselves are issued by galaxies.

14

15−- A [ship](../ship) on the Arvo network whose identity is a planet in the former definition. In this sense, stars act as infrastructure for the [Arvo](../arvo) network, providing planets with [Ames](../ames)-related services, such as peer-to-peer routing and distributing [over-the-air software updates](../ota-updates). Stars rely on galaxies for these services in the way that planets rely on stars.

15+- A [ship](../ship) on the Arvo network whose identity is a star in the former definition. In this sense, stars act as infrastructure for the [Arvo](../arvo) network, providing planets with [Ames](../ames)-related services, such as peer-to-peer routing and distributing [over-the-air software updates](../ota-updates). Stars rely on galaxies for these services in the way that planets rely on stars.

16

17Stars have addresses that are representable by 16 bits. This means that there are 65,535 possible stars, and each of these stars is able to issue 65,535 planets. Stars have two-syllable names like `~taglux` or `~hallet`.