GitBook: [main] 54 pages and 6 assets modified

README.md

@@ -0,0 +1,24 @@
+# Introduction
+
+Fluence Labs builds distributed networks, development tools, components and support systems to allow developers to efficiently and reliably build, operate, maintain, and monetize distributed and decentralized services and applications. An integral component of the Fluence solution is [Aquamarine](https://github.com/fluencelabs/aquamarine), a programming language enabling peer-to-peer coordination for distributed applications and backends.
+
+Fluence is also developing the [Fluence Compute Engine](https://github.com/fluencelabs/fce) \(FCE\) -- a general purpose runtime for multi-module WebAssembly applications with WASI support and a [shared-nothing](https://en.wikipedia.org/wiki/Shared-nothing_architecture) linking scheme. FCE allows for the rapid development and deployment of portable Wasm services which can be composed and coordinated with Aquamarine into secure applications. Furthermore, Fluence has implemented innovations at the p2p [node](https://github.com/fluencelabs/fluence) level, such as [TrustGraph](https://github.com/fluencelabs/trust-graph), local development and testing tools, such as [FCE-Repl](https://github.com/fluencelabs/fce/tree/master/tools/repl), and support tooling, such as [Fluence Distributor](https://github.com/fluencelabs/proto-distributor).
+
+In combination, Aquamarine and the Fluence runtimes and tools allow developers to avoid the typical peer-to-peer development challenges and accelerate the development and deployment of distributed services and applications.
+
+The remainder of this document introduces a set of incremental, hands-on tutorials developing with Aquamarine on the Fluence stack.
+
+Additional resources and support are available:
+
+* [Youtube](https://www.youtube.com/channel/UC3b5eFyKRFlEMwSJ1BTjpbw)
+* [Github](https://github.com/fluencelabs)
+* [Discord](https://discord.gg/aR2AYErM)
+* [Telegram](https://t.me/fluence_project)
+* [Twitter](https://twitter.com/fluence_project)
+
+Documentation is work in progress and your feedback is extremely valuable and much appreciated. If you have suggestions or unearth errors or inaccuracies, please open an Issue or push a PR.
+
+Thank You and Enjoy,
+
+The Fluence Team
+

knowledge_knowledge/knowledge_aquamarine/knowledge_aquamarine_air.md

@@ -23,7 +23,7 @@ AIR instructions are intended to launch the execution of a service method as fol
 4. The arguments specified by the argument list are passed to the method
 5. The result of the method returned under the name output name
 
-**Figure 2: Sequential Instruction** ![Execution](../../.gitbook/assets/air_sequential_2%20%281%29.png)
+**Figure 2: Sequential Instruction** ![Execution](../../.gitbook/assets/air_sequential_2%20%281%29%20%281%29.png)
 
 The seq instruction takes two instructions at most as its arguments and executes them sequentially, one after the other.
 
@@ -33,7 +33,7 @@ The par</i.> instruction takes two instructions at most as its arguments a
 
 TODO: add better graphic showing the disticntion of branching vs seq.
 
-**Figure 4: Fold Instruction** ![Execution](../../.gitbook/assets/air_fold_4.png)
+**Figure 4: Fold Instruction** ![Execution](../../.gitbook/assets/air_fold_4%20%281%29.png)
 
 The fold instruction iterates over the elements of an array and workds as follows:
 
@@ -49,7 +49,7 @@ This instruction is intended for organizing branches in the flow of execution as
 * The first instruction is executed and if the execution is successful, then the second instruction is ignored
 * If the first instruction fails, then the second one is executed.
 
-**Figure 6: Null Instruction** ![Execution](../../.gitbook/assets/air_null_6.png)
+**Figure 6: Null Instruction** ![Execution](../../.gitbook/assets/air_null_6%20%281%29%20%281%29.png)
 
 This is an empty instruction: it takes no arguments and does nothing. The null instruction is useful for generating code.