update tech book for docusaurus

docs/features/compute/_category_.json

@@ -0,0 +1,7 @@
+{
+    "label": "Compute",
+    "position": 2,
+    "link": {
+      "type": "generated-index",
+    }
+  }

docs/features/compute/compute.md

@@ -0,0 +1,24 @@
+---
+sidebar_position: 1
+title: Compute Layer
+---
+
+# Compute Layer
+
+![](../../img/zos_compute.png)
+
+Default features:
+
+- Compatible with Docker
+- Compatible with any VM (Virtual Machine)
+- Compatible with any Linux workload
+- Integrated unique storage & network primitives
+- Integrated smart contract for IT layer
+
+We have the following unique advantages:
+
+- No need to work with images, we work with our unique ZOS FS
+- Every container runs in a dedicated virtual machine providing more security
+- The containers talk to each other over a private network (Mycelium)
+- The containers can use a web gateway to allow internet users to connect to the applications which are running in their secure containers 
+- Can use core-x to manage the workload

docs/features/compute/zero_deploy.md

@@ -0,0 +1,39 @@
+---
+sidebar_position: 3
+title: Zero-Deploy
+---
+
+
+## Deterministic Deployment
+
+
+The concept of Zero-Deploy is a key component of the **Smart Contract for IT** framework, which can be applied to any type of workload—whether it's containers, virtual machines (VMs), network gateways, volumes, Kubernetes resources, or other network elements. This framework serves as a formal agreement between a farmer (provider) and a user regarding the deployment of an IT workload.
+
+### Process
+
+1. **Build Your Code**  
+   Develop and prepare your application code.
+
+2. **Convert to Zero-Image**  
+   Use a CI/CD solution (e.g., Hero CI/CD) to convert your Docker build (or other format) into a Zero-Image format.
+
+3. **Define the Workload**  
+   Specify all the details of your workload, including network bridges, web gateways, required machines, and more.
+
+4. **Register and Sign**  
+   Register the workload and sign it with your private key.
+
+5. **Automatic Detection**  
+   All necessary Zero-OS nodes (our infrastructure) will detect that a new workload needs to be deployed.
+
+6. **Deployment Process**  
+   The nodes will pull down the formal workload descriptions and initiate the deployment process.
+
+7. **Validation**  
+   Every step of the deployment is verified by Zero-OS (ZOS) to ensure that the intended result is accurately replicated. If any discrepancies are detected, ZOS will halt the deployment and provide an error message.
+
+### Benefits
+
+- **Deterministic Deployment**: There is no dynamic behavior during deployment at runtime, ensuring a consistent and predictable outcome.
+- **Strict Compliance**: No process can start unless all files and configurations are fully described at the flist level.
+

docs/features/compute/zero_install.md

@@ -0,0 +1,35 @@
+---
+sidebar_position: 4
+title: Zero-Install
+---
+
+
+## Zero install
+
+![](../../img/boot.png)  
+
+The Zero-OS is delivered to the 3Nodes over the internet network (network boot) and does not need to be installed.
+
+
+### 3Node Install
+
+1. Deploy a computer
+2. Configure a farm on the TFGrid explorer
+3. Download the bootloader and put on a USB stick or configure a network boot device
+4. Power on the computer and connect to the internet
+5. Boot! The computer will automatically download the components of the operating system (Zero-OS)
+
+The actual bootloader is very small, it brings up the network interface of your computer and queries TFGrid for the remainder of the boot files needed.
+
+The operating system is not installed on any local storage medium (hard disk, ssd), Zero-OS is stateless.
+
+The mechanism to allow this to work in a safe and efficient manner is an innovation called our container virtual filesystem. 
+
+### Process
+
+- optionally: configure booting from secure BIOS
+- optionally: install signing certificate in the BIOS, to make sure that only the right bootloader can be started
+- the bootloader (ISO, PXE, USB, ...) get's downloaded from Internet (TFGrid CDN or private deployment)
+- core-0 (the first boot process) starts, self verification happens
+- the metadata for the the required software modules is downloaded and checked against signature and hashes 
+- the core-0 zero_image service

docs/features/compute/zero_os.md

@@ -0,0 +1,46 @@
+---
+sidebar_position: 2
+title: Zero-OS
+---
+
+
+# Zero-OS
+
+![](../../img/zos23.png)
+
+A revolutionary operating system which can be booted on most modern computers. Once installed Zero-OS locks the hardware and makes it accessible to the decentralized marketplace or a centralized ultra secure deployment system. Blockchain mechanism can be used to strongly control how workloads are deployed on the system.
+
+![](../../img/zos_overview.png)
+
+## ZOS Compute & Storage Overview
+
+![](../../img/zos_overview_compute_storage.jpg)
+
+## ZOS Network Overview
+
+![](../../img/zos_network_overview.jpg)
+
+
+### Imagine An Operating System With The Following Benefits
+
+- Up to 10x more efficient for certain workloads (e.g. storage)
+- No install required
+- All files are deduped for the VM's, containers and the ZOS itself, no more data duplicated filesystems
+- The hacking footprint is very small which leads to much safer systems
+    - Every file is fingerprinted and gets checked at launch time of an application
+    - There is no shell or server interface on the operating system
+    - The networks are end2end encrypted between all Nodes
+- It is possible to completely disconnect the compute/storage from the network service part which means hackers have a lot less chance to access the data
+- A smart contract for the IT layer allows groups of people to deploy IT workloads with consensus and full control
+- All workloads which can run on linux can run on Zero-OS but in a much more controlled, private and safe way
+
+> We have created an operating system from scratch. We used the Linux kernel and its components and then built further on it. We have been able to achieve all of the above benefits.
+
+## Requirements:
+
+- **Autonomy**: TF Grid needs to create compute, storage and networking capacity everywhere. We could not rely on a remote (or a local) maintenance of the operating system by owners or operating system administrators.
+- **Simplicity**: An operating system should be simple, able to exist anywhere for anyone, and be good for the planet.
+- **Stateless**: In a grid (peer-to-peer) set up, the sum of the components provides a stable basis for single elements to fail and not bring the whole system down. Therefore, it is necessary for single elements to be stateless, and the state needs to be stored within the grid.
+
+
+

docs/features/compute/zkube.md

@@ -0,0 +1,34 @@
+---
+sidebar_position: 5
+title: ZKube
+---
+
+
+# ZKube
+
+TFGrid is compatible with Kubernetes Technology.
+
+![](../../img/kubernetes_0.jpg)
+
+### Unique for our Kubernetes implementation
+
+- The Kubernetes networks are on top of our Mycelium technology which means all traffic between containers and kubernetes hosts is end2end encrypted independent of where your Kubernetes nodes are deployed.
+- You can mount a Quantum Safe Storage System underneath a Kubernetes Node (VM), which means that you can deploy containers on top of QSFS to host unlimited amounts of storage in a super safe way.
+- You Kubernetes environment is for sure 100% decentralized, you define where you want to deploy your Kubernetes nodes and only you have access to the deployed workloads on the TFGrid.
+
+### Features
+
+*   integration with znet (efficient, secure encrypted network between the zero_vms)
+*   can be easily deployed at the edge
+*   single-tenant!
+
+<!-- 
+### Zero VM Benefits
+
+*   [ZOS Protect](zos_protect): no hacking surface to the Zero-Nodes, integrate silicon route of trust
+*   [ZNet](znet) and [Planetary Net](planetary_network): a true global single backplane network connecting us all -->
+
+### Architecture
+
+![](../../img/zkube_architecture.jpg)
+