Checking in base code before renaming from Atym to ocre

Author: gonzolively

_config.yml

@@ -12,10 +12,13 @@ destination: _site
 favicon_ico: "/assets/images/favicon.png"
 logo: "/assets/images/logo.png"
 # Misc
-heading_anchors: true
 enable_copy_code_button: true
 permalink: pretty
 
+# Heading anchors/TOC
+heading_anchors: true
+toc: true
+
 ### Defaults paths/content types
 defaults:
   - scope:
@@ -98,6 +101,8 @@ aux_links:
 # Back to top link
 back_to_top: true
 back_to_top_text: "Back to top"
+# Enable or disable the previous/next buttons (may need to update all pages with "nav_order" to work)
+#show_previous_next: true
 
 # Copyright/license stuff
 footer_content: 'Copyright &copy; 2024 Contributors to Project Ocre, which has been established as <a href="https://lfedge.org/projects/ocre"> Project Ocre a Series of LF Projects</a>, LLC. Distributed by an <a href="https://github.com/project-ocre/project-ocre.github.io/blob/main/LICENSE.txt">Apache 2.0 License.</a>'

docs/architecture/atym_solution.png

@@ -0,0 +1,16 @@
+---
+layout: default
+title: Binary Objects (Optional)
+parent: Components
+nav_order: 2 
+---
+
+Atym containers can optionally include binary objects as part of the container image. These are additional resources that can be referenced by the WebAssembly module during execution.
+
+Common use cases for binary objects include:
+
+* Storing images or sound files
+* Incorporating pre-trained AI/ML models
+* Including any other form of binary data required by the application
+
+This feature allows developers to package necessary non-executable resources alongside their application code, enhancing the container's functionality and self-sufficiency while maintaining a clear separation between executable code and static data.

docs/architecture/containers/components/Container_Applications_Container_Services.png

@@ -0,0 +1,47 @@
+---
+layout: default
+title: Container Configuration 
+parent: Components
+nav_order: 1
+---
+
+
+The container configuration defines how a container should be run on the device. It provides essential metadata that dictates the behavior of the container, including parameters like environment variables, entry points, and permissions. These configurations ensure that containers operate within defined constraints and have access only to necessary system resources.
+
+---
+
+### Example:
+```json
+{
+  "architecture": "amd64",
+  "os": "nubix",
+  "config": {
+    "Entrypoint": "on_init",
+    "Environment": [
+      "VAR1=value1",
+      "VAR2=value2"
+    ],
+    "Permissions": [
+      "filesystem",
+      "http",
+      "i2c",
+      "gpio"
+    ]
+  }
+}
+```
+### Configuration Parameters
+
+The elements within the container configuration are defined as follows:
+
+#### Required:
+- `architecture` (*string*): CPU architecture of the binaries in this image; this value MUST be set to **wasm**. This parameter also supports an optional variant value. For example, `thumbv4`.
+- `os` (*string*): Operating system which this image is built to run on; this MUST be **nubix**.
+- `config` (*object*): Specifies the parameters used for execution
+  - `EntryPoint`: The WASM function to call on container start.
+  - `Environment`: Array of variables to set in the container environment.
+  - `Permissions`: Aarray of permissions granted to the container.
+
+#### Optional:
+- `os.version`: Specify version of the operating system.
+- `os.features` Specify os-specific features.

docs/architecture/containers/components/atym_container.png

@@ -0,0 +1,19 @@
+---
+layout: default
+title: Components 
+parent: Containers 
+has_children: true 
+nav_order: 0 
+---
+
+# Container Components
+
+Atym containers are designed to bring cloud-native principles to embedded devices, combining efficiency with flexibility. Each container is a self-contained unit that encapsulates an application and its dependencies, structured to optimize performance and resource usage on constrained hardware.
+
+![](atym_container.png)
+
+An Atym container consists of **three** main elements, which are defined and organized within a **[Container Image Manifest](../container_image_manifest/)**:
+
+- **[WebAssembly Module:](../components/webassembly_module/)** The core executable portion of the container, compiled from the developer's chosen language.
+- **[Container Configuration:](../components/container_configuration/)** Metadata including the application name, execution properties, variables, and permissions.
+- **[Binary Objects:](../components/binary_objects/)** Optional resources that can be referenced by the WebAssembly module. Examples include machine learning models, configuration files, or any other data needed by the application.

docs/architecture/containers/components/binary_objects/index.md

@@ -0,0 +1,14 @@
+---
+layout: default
+title: WebAssembly Modules 
+parent: Components
+nav_order: 0
+---
+
+# WebAssembly Modules
+
+Atym containers use [WebAssembly (WASM)](https://webassembly.org/) modules as the format for executable code. These modules are stateless binaries compiled to run on the WASM virtual machine.
+
+Modules can either be pure WebAssembly or Ahead-of-Time (AOT) compiled binaries optimized for a specific platform target. In general, the Atym Orchestration Hub will automatically AOT compile modules on-demand based on the architecture of the deployment target. However, there are instances where a pure WASM binary may be preferred.
+
+**Note:** Currently, only a single WASM module is supported per container image. However, we are exploring extending this to support multiple modules and/or components via the WebAssembly Component Model.

docs/architecture/containers/components/container_configuration/index.md

@@ -0,0 +1,55 @@
+---
+layout: default
+title: Container Image Manifest 
+parent: Containers
+nav_order: 1 
+---
+
+
+The Container Image Manifest is a crucial component of Atym containers, providing a comprehensive description of the container's structure and contents. It serves as the blueprint that defines and references the three main elements of an Atym container described in the [Components](../components/index.md) section. The manifest ensures that all components can be correctly deployed and executed by the [Atym Runtime](../../runtime). 
+
+Atym container images follow the [Open Container Initiative (OCI)](https://opencontainers.org/) format where possible, with some modifications to support the needs of constrained, embedded devices. The manifest format is modeled after the [OCI Image Manifest](https://github.com/opencontainers/image-spec/blob/main/manifest.md) format and conforms to the [Wasm OCI Artifact](https://tag-runtime.cncf.io/wgs/wasm/deliverables/wasm-oci-artifact/) layout specifications. This structure ensures that all components of the container are properly defined, versioned, and can be efficiently managed in resource-constrained environments.
+
+---
+
+### Example
+
+Here's an example of an Atym Container Image Manifest:
+
+```json
+{
+  "schemaVersion": 2,
+  "mediaType": "application/vnd.oci.image.manifest.v1+json",
+  "config": {
+    "mediaType": "application/vnd.atym.image.config.v1+json",
+    "digest": "sha256:32b81b11f15ea9c198d59e143b2a5f15446b50b8954ce2e6cfab959988271c78",
+    "size": 341
+  },
+  "layers": [
+    {
+      "mediaType": "application/vnd.atym.image.v1.wasm",
+      "digest": "sha256:6d61671e8d62f5e77ed054c2d3df4dc9b31e3c74fee7d478f3f2bbdc99a6f256",
+      "size": 330
+    },
+    {
+      "mediaType": "application/vnd.atym.image.v1.blob",
+      "digest": "sha256:201ef6570d2967b299cf5ab8f946f061d5db523c106bc90f72729693b798f431",
+      "size": 709
+    }
+  ]
+}
+```
+
+### Configuration Parameters
+
+The elements within the container configuration are defined as follows:
+
+#### Required:
+- `schemaVersion` (*int*): Image manifest schema version; per the OCI Image Spec this
+MUST be **2**.
+- `mediaType` (*string*): Required type of this manifest file. For Atym containers, this MUST be
+**application/vnd.nubixio.image.manifest.v1+json**.
+- `config` (*object*): References the configuration object for this container image. Schema follows the [OCI Content Descriptor schema](https://github.com/opencontainers/image-spec/blob/main/descriptor.md). It has the
+following restrictions:
+  - `mediaType` must be set to **application/vnd.nubixio.image.config.v1+json**.
+- `layers` (*array*): List of elements that comprise this container image. Each layer is a descriptor. One and only one layer MUST be of type **application/vnd.nubixio.image.layer.v1.wasm** or **application/vnd.nubixio.image.layer.v1.wasm+aot**.