Add full architecture documentation and link it into README

- Added complete architecture.md with Mermaid diagram, component descriptions,
  and main application workflow
- Linked architecture.md from README for easier navigation
- Updated README layout to reflect polished project structure
- Ensured documentation matches the multi-component ESP-IDF C++ architecture
- Improves clarity

Author: CahillMeyer

README.md

@@ -1,5 +1,10 @@
 # ccm-esp32-vision-node
 
+![ESP-IDF](https://img.shields.io/badge/ESP--IDF-C%2B%2B%20project-orange)
+![Platform](https://img.shields.io/badge/Platform-ESP32--S3-blue)
+![Language](https://img.shields.io/badge/Language-C%2B%2B17-purple)
+[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)
+
 Embedded camera node for **ESP32-S3** with a modular C++ architecture for real-time computer vision.
 This project demonstrates professional embedded CV engineering: camera bring-up, modular pipelines,
 and efficient processing on low-power microcontrollers.
@@ -33,6 +38,7 @@ and efficient processing on low-power microcontrollers.
 ---
 
 ## 🧱 Project Architecture
+For a detailed component diagram and explanation, see [docs/architecture.md](docs/architecture.md).
 
 ```
 ccm-esp32-vision-node/
@@ -54,6 +60,22 @@ ccm-esp32-vision-node/
 
 ---
 
+## 🧪 Tested / Target Environment
+
+This project is being developed and tested with:
+
+- **Chip:** ESP32-S3
+- **SDK:** ESP-IDF (Linux / WSL)
+- **Host environment:** Windows 10 + WSL Ubuntu
+- **Tooling:** VS Code, `idf.py`, CMake
+
+Planned hardware targets include:
+
+- ESP32-S3 dev boards with PSRAM
+- Camera modules based on OV2640 / OV5640
+
+---
+
 ## 🖥️ Getting Started (ESP-IDF)
 
 ### 1. Install ESP-IDF

docs/architecture.md

@@ -0,0 +1,69 @@
+# Architecture – ccm-esp32-vision-node
+
+This project is organised as a set of ESP-IDF components to keep camera I/O,
+processing, and streaming responsibilities cleanly separated.
+
+```mermaid
+flowchart LR
+    A[CameraNode<br/>components/camera_node] --> B[CvPipeline<br/>components/cv_pipeline]
+    B --> C[StreamServer<br/>components/stream_server]
+    B --> D[UART / Logging<br/>components/utils]
+```
+
+---
+
+## Components
+
+### **CameraNode**
+Owns camera configuration and frame acquisition via the `esp32-camera` managed component.  
+Responsible for:
+- camera pin configuration  
+- sensor initialization  
+- frame buffer acquisition & release  
+- controlling resolution, format, grab mode  
+
+---
+
+### **CvPipeline**
+Processes frames (grayscale, thresholding, ROI, simple filters).  
+Designed to be modular so stages can be swapped or reordered.  
+Later this will include:
+- basic preprocessing  
+- simple blob detection  
+- region masking  
+- profiling hooks  
+
+---
+
+### **StreamServer** *(planned)*
+Exposes frames over Wi-Fi, either as:
+- MJPEG HTTP stream  
+- Raw frame endpoint  
+- Debug overlay with FPS  
+
+Useful for edge monitoring and remote debugging.
+
+---
+
+### **Utils / Drivers**
+Provides:
+- lightweight logging
+- timing & FPS measurement
+- board-specific pin setup
+- reusable helpers
+
+This keeps noise out of the main components.
+
+---
+
+## Main Application
+
+The `firmware/main` app wires all components together:
+
+1. Initialize the camera  
+2. Capture frames in a loop  
+3. Pass frames into `CvPipeline`  
+4. Forward processed frames or metadata to `StreamServer` *(when implemented)*  
+5. Output timing/debug info via UART  
+
+This layered structure mirrors real-world embedded vision systems and keeps the project modular and maintainable.