chore: update docs

docs/src/architecture/08_concepts/hermes_packaging_requirements/application.md

@@ -2,4 +2,7 @@
 
 ## HDF5 file structure
 
-TODO
+
+```kroki-d2
+@from_file:architecture/08_concepts/hermes_packaging_requirements/images/application_metadata.dot
+```

docs/src/architecture/08_concepts/hermes_packaging_requirements/overview.md

@@ -1,23 +1,33 @@
-# Hermes Application Packaging Requirements
+# Packaging Overview
 
-## Overview
+Applications in Hermes are packaged and distributed using [HDF5](https://docs.hdfgroup.org/hdf5/develop/) (Hierarchical Data Format Version 5) files.
+
+## Hermes HDF5 File Metadata
+
+## Hermes HDF5 File Structure
+
+```kroki-d2
+@from_file:architecture/08_concepts/hermes_packaging_requirements/images/hdf5_file_structure.dot
+```
 
-TODO
 
 ** SJ Notes **
 
 Each package needs metadata which can be associated with it.
 So we may want to define that in its own file.
 Example metadata are similar to a webasm module.
-1. App Author
-2. Version
-3. Repo
-4. License
-5. Description
-6. Json Schema for its configuration, so a user can configure it.
-   1. This is the only config a user actually sets,  it will embed (and can have references to that config) from individual wasm modules.
-   2. We need to work out how this will work and define it.
-7. other stuff
+
+  1. App Author
+  2. Version
+  3. Repo
+  4. License
+  5. Description
+  6. Json Schema for its configuration, so a user can configure it.
+
+     1. This is the only config a user actually sets,  it will embed (and can have references to that config) from individual wasm modules.
+     2. We need to work out how this will work and define it.
+
+  7. other stuff
 
 We also need to sign the package, and it needs to be able to support multisig, so it can be signed by the Author and then countersigned by a publisher.
 

docs/src/architecture/08_concepts/hermes_packaging_requirements/wasm_modules.md

@@ -1,21 +1,29 @@
 # Packaging WebAssembly (WASM) modules in a Hermes Application
 
-TODO
+```kroki-d2
+@from_file:architecture/08_concepts/hermes_packaging_requirements/images/wasm_module_metadata.dot
+```
 
 ** SJ Notes **
 Wasm modules need the following data:
+
 1. The compiled WASM code
 2. Metadata about the wasm module
-   1. Name
-   2. Author
-   3. Repo
-   4. License
-   5. etc.
+
+  1. Name
+  2. Author
+  3. Repo
+  4. License
+  5. etc.
+
 4. Configuration data (Json or CBOR) that parameterises the module.
+
    1. Json schema for "Preset" parameters.  These are not changeable by the user.
    2. Json schema for "Configurable" parameters.  These can be set by the user before the app runs.
    3. The actual "preset" parameters themselves (which must be valid according to the "preset" parameter schema.
+
 5. All of the above should be encoded using CBOR (Needs to be defined with a valid CDDL schema).
 5. A Signature of the Module Author and/or publisher validating its the code they "released".
+
    1. For this we should wrap all the above in COSE (See: RFC-9052, RFC-9053, RFC-0338)
    2. All CBOR is to be specified as needing to be encoded following the deterministic CBOR Rules.  See https://developer.blockchaincommons.com/dcbor/ and https://datatracker.ietf.org/doc/draft-mcnally-deterministic-cbor/

docs/src/architecture/08_concepts/hermes_runtime_engine/h_app_struct.md

@@ -8,15 +8,33 @@ bundled in [hdf5](https://www.hdfgroup.org/solutions/hdf5/) package.
 Each WASM component it is the event handlers implementation of `export` functions from the [WIT] file,
 specified by the [*Hermes runtime extension*].
 
-Package structure
+## Package structure
 
 ```bash
-├── module1.wasm
-├── module2.wasm
-├── config.json
-└── METADATA
+/ root
+├── static
+│   ├── data
+│   │   └── default
+│   │       ├── config.json
+│   │       └── ...
+│   └── www
+│       ├── site1
+│       │  ├── html
+│       │  └── ...
+│       └── site2
+│          ├── html
+│          └── ...
+├── data
+│   ├── module1_dataset
+│   ├── module2_dataset
+│   └── ...
+└── module
+    ├── module1.wasm
+    ├── module2.wasm
+    └── ...
 ```
 
+
 [WIT]: https://component-model.bytecodealliance.org/design/wit.html
 [*Hermes runtime extension*]: ./../../05_building_block_view/hermes_core.md#hermes-runtime-extension-hre
 [*Hermes application*]: ./../../05_building_block_view//hermes_core.md#hermes-application