edgelesssys · m1ghtym0 · Aug 14, 2023 · Jul 19, 2023 · Jul 19, 2023 · Jul 19, 2023
diff --git a/docs/docs/_media/cert-chain.svg b/docs/docs/_media/cert-chain.svg
diff --git a/docs/docs/_media/enc-state-distributed.svg b/docs/docs/_media/enc-state-distributed.svg
diff --git a/docs/docs/_media/enc-state-single.svg b/docs/docs/_media/enc-state-single.svg
diff --git a/docs/docs/_media/security_architecture.svg b/docs/docs/_media/security_architecture.svg
diff --git a/docs/docs/getting-started/concepts.md → docs/docs/architecture/concepts.md b/docs/docs/getting-started/concepts.md → docs/docs/architecture/concepts.md
diff --git a/docs/docs/getting-started/coordinator.md → docs/docs/architecture/coordinator.md b/docs/docs/getting-started/coordinator.md → docs/docs/architecture/coordinator.md
@@ -1,6 +1,14 @@
 # Coordinator
 
 The Coordinator is MarbleRun's control plane.
+Conceptionally it operators as trusted controller in your confidential deployment.
+Therefore, it securely holds the deployment's state in form of the [manifest](../features/manifest.md) and the defined [secrets](../features/secrets-management.md).
+Based on the manifest, the Coordinator uses [remote attestation](../features/attestation.md) to authenticate the application's enclaves.
+
+
+
+## API and Configuration
+
 It communicates with the Marble's data plane through gRPC and provides an HTTP REST interface on the client-side.
 The Coordinator can be configured with several environment variables:
 

diff --git a/docs/docs/architecture/marbles.md b/docs/docs/architecture/marbles.md
@@ -0,0 +1,6 @@
+# Marbles
+
+Marbles are MarbleRun's data planes and run your application code in secure enclaves within otherwise regular Docker containers.
+Marbles communicate with the Coordinator via gRPC over TLS.
+MarbleRun natively [supports multiple enclave runtimes](../features/runtimes.md) as the data plane.
+See the [Add a Service](../workflows/add-service.md) section on how to build and configure an enclave as Marble.