on master help sign in
links: arvo/ames.md
commita57676fbc577dad20629775f5d37a1cefa7c6b2f authordrbeefsupreme <drbeefsupreme@discordja.net> dateThu 18 Feb 2021, 15:53 (6 years ago) parent5a23def
2 files changed+4−4
arvo/arvo.md+3−3 glossary/ames.md+1−1
arvo/arvo.md+3−3
@@ -176,7 +176,7 @@ Typically, updates to an operating system are given via a pre-compiled binary,
176176which is why some updates will work on some systems but not on others where the
177177hardware and environment may differ. This is not so on Arvo - because it is an
178178[interpreter](#solid-state-interpreter), Arvo may update itself by receiving
179−source code from your sponsor over [Ames](@/docs/tutorials/arvo/ames.md), our
179+source code from your sponsor over [Ames](@/docs/arvo/ames/ames.md), our
180180network. As Hoon compiles down to Nock, which is an axiomatic representation of
181181a deterministic computer, this code is guaranteed to run identically on your machine as it
182182would on anybody else's.
@@ -444,7 +444,7 @@ A short summary of the purpose of each these arms are as follows:
444444 - `+poke` is the transition function that `move`s Arvo from one state to the
445445 next. It is the most fundamental arm in the entire system. It is a typed
446446 transactional message that is processed at most once. If the `+poke` causes
447− Arvo to send an message over [Ames](@/docs/tutorials/arvo/ames.md) Ames
447+ Arvo to send an message over [Ames](@/docs/arvo/ames/ames.md) Ames
448448 guarantees that the message will be delivered exactly once. This is sometimes said
449449 to be impossible, and it is for standard operating systems, but that is not the case for single-level stores engaged in
450450 a permanent session, as is the case among Arvo ships.
@@ -561,7 +561,7 @@ data that directly causes the desired outcome of a `move`. This event data is co
561561
562562As of this writing, we have nine vanes, which each provide the following services:
563563
564−- [Ames](@/docs/tutorials/arvo/ames.md): the name of both our network and the vane that communicates over it.
564+- [Ames](@/docs/arvo/ames/ames.md): the name of both our network and the vane that communicates over it.
565565- [Behn](@/docs/tutorials/arvo/behn.md): a simple timer.
566566- [Clay](@/docs/tutorials/arvo/clay.md): our version-controlled, referentially- transparent, and global filesystem.
567567- [Dill](@/docs/tutorials/arvo/dill.md): a terminal driver. Unix sends keyboard events to `%dill` from the console, and `%dill` produces terminal output.
glossary/ames.md+1−1
@@ -14,6 +14,6 @@ level to fix networking issues or at a network-wide level to update Arvo beyond
1414what OTA updates are capable of doing. These events are called [breaches](../breach).
1515### Further Reading
1616
17−- [The Ames tutorial](@/docs/tutorials/arvo/ames.md): An in-depth technical guide to the Ames protocol.
17+- [The Ames tutorial](@/docs/arvo/ames/ames.md): An in-depth technical guide to the Ames protocol.
1818- [A Guide to Breaches](@/docs/tutorials/guide-to-breaches.md): Instructions on handling continuity breaches (resets) on the Ames network.
1919- [Ship Troubleshooting](@/docs/tutorials/ship-troubleshooting.md): General instructions on getting your ship to work, which includes network connectivity issues.