start an interface documentation

content/docs/50_platform/architecture/error_management/index.md

@@ -1,7 +1,7 @@
 ---
 title: "platform_error"
 description: ""
-weight: 1
+weight: 20
 icon: "error"
 ---
 

content/docs/50_platform/architecture/interface/index.md

@@ -0,0 +1,20 @@
+---
+title: "Interface"
+description: "How are organized the interfaces ?"
+weight: 1
+icon: "arrow_forward_ios"
+---
+
+
+Interfaces are mainly composed of 
+
+- Interface Data
+- FSM (Finite State Machine): Manage internal workflow of the interface
+- Listener: manage incoming message from the connection
+
+FSM et Listener have their own task.
+
+Other helper components:
+
+- Logger: Helper to log information that come from this specific interface
+

content/docs/50_platform/architecture/platform_services/index.md

@@ -1,7 +1,7 @@
 ---
 title: "Platform Services"
 description: ""
-weight: 1
+weight: 10
 icon: "rule_settings"
 ---
 

content/docs/50_platform/architecture/synoptic/index.md

@@ -10,3 +10,27 @@ icon: "architecture"
 ![](./schema.png)
 
 
+
+The platform sources are coded in Rust and are organized by directory reflecting its architecture.
+
+## builtin_devices
+
+This directory contains devices and interface implementations that come built-in the main platform sources.
+
+In this directory there must be one directory for each manufacturer. The manufacturer directory must hold devices related to its produc
+ts.
+
+## Meta
+
+In the meta directory, you will find generic interface implementations.
+Those implementations ease the adaptations of new device interfaces by taking care of most of the hard part of the behavior and letting to the user only the specific callback to implement.
+
+
+## Log
+
+In the log directory, you will find how traces of the application are managed.
+
+### class
+
+Traces in rust can take some attributes. Panduza has defined the log attribute “class” to sort event sources in the application.
+