Skip to content

docs: create comprehensive deployment architecture diagrams (#4)#6

Closed
addidea wants to merge 1 commit intoClawland-AI:mainfrom
addidea:docs/architecture-diagram
Closed

docs: create comprehensive deployment architecture diagrams (#4)#6
addidea wants to merge 1 commit intoClawland-AI:mainfrom
addidea:docs/architecture-diagram

Conversation

@addidea
Copy link

@addidea addidea commented Feb 16, 2026

Description

Complete deployment architecture documentation with 8 Mermaid diagrams covering all layers of the Clawland edge AI network.

Closes #4

What's Included

Three-Tier Architecture Diagram

  • L1 (MicroClaw/PicoClaw): Edge sensors
  • L2 (NanoClaw): Regional gateways
  • L3 (MoltClaw/Fleet): Cloud orchestration
  • Visual representation of entire hierarchy

Data Flow Sequence Diagrams (2)

  1. Sensor data upload (L1→L2→L3)
  2. Command dispatch (L3→L2→L1)
  • Shows MQTT topics, validation, aggregation, alerts

Network Topology Options (3 diagrams)

  1. LAN + WiFi (office deployment)
  2. 4G/LTE (remote sites)
  3. LoRa (ultra-low power, 2-5km range)

Component Interaction (2 diagrams)

  • Fleet Manager components (API, Registry, Heartbeat, etc.)
  • NanoClaw regional gateway architecture
  • Data/message layer integration

Failure Scenarios (3 diagrams + recovery)

  1. Cloud connection lost → Offline mode
  2. Regional gateway failure → Auto-discover fallback
  3. Sensor node failure → Heartbeat monitoring

Deployment Examples (3 real-world scenarios)

  • Office: 30 sensors, 20 setup
  • Factory: 50 sensors, 70 setup
  • Smart farm: 200 sensors with LoRa, 15 setup

Scaling & Security

  • Scaling table (small/medium/large)
  • Technology stack reference
  • Security best practices

Diagrams

8 Mermaid diagrams total:

  1. Three-tier architecture (graph)
  2. Sensor data upload (sequence)
  3. Command dispatch (sequence)
  4. LAN topology (graph)
  5. 4G/LTE topology (graph)
  6. LoRa topology (graph)
  7. Fleet Manager components (graph)
  8. NanoClaw gateway (graph)

Plus 3 failure scenario sequences.

Key Insights

Data Flow:

L1 (sensor) → MQTT → L2 (aggregation) → MQTT → L3 (storage + alerts)
L3 (command) → MQTT → L2 (routing) → MQTT → L1 (execution)

Failure Resilience:

  • Offline mode with local rules (no cloud dependency)
  • Auto-discover fallback gateways (mDNS)
  • Heartbeat monitoring with 180s timeout

Network Options:

  • WiFi: Office/indoor deployments
  • 4G: Remote sites without fixed internet
  • LoRa: Ultra-low power, 2-5km range, ideal for farms

Benefits

  • Visual understanding of entire system
  • Reference for new contributors
  • Deployment planning guide
  • Failure scenario documentation
  • Real-world cost estimates

Ready for review! 🏗️

Closes #4

Complete architecture documentation with Mermaid diagrams:

**Three-Tier Architecture**:
- L1 (MicroClaw/PicoClaw): Edge sensors, -10 hardware
- L2 (NanoClaw): Regional gateways, Raspberry Pi
- L3 (MoltClaw/Fleet): Cloud orchestration

**Data Flow Diagrams**:
- Sensor data upload (L1→L2→L3) sequence
- Command dispatch (L3→L2→L1) sequence
- MQTT topic structure and routing

**Network Topology** (3 options):
1. LAN + WiFi (office deployment)
2. 4G/LTE (remote sites with cellular)
3. LoRa (ultra-low power, 2-5km range)

**Component Interaction**:
- Fleet Manager components (API, Registry, Heartbeat, Command, Event)
- NanoClaw gateway (Aggregator, Forwarder, Local Cache, Decision Engine)
- Data layer (PostgreSQL + Redis)
- Message layer (MQTT broker)

**Failure Scenarios** (with recovery):
1. Cloud connection lost → Offline mode with local rules
2. Regional gateway failure → Auto-discover fallback gateway
3. Sensor node failure → Heartbeat monitoring + alerts

**Deployment Examples**:
- Office building: 3 floors, 30 sensors, 20 setup
- Factory: 5 zones, 50 sensors, 70 setup
- Smart farm: 100 hectares, 200 sensors with LoRa, 15 setup

**Scaling Characteristics**:
- Small: 10-50 nodes, <0/month
- Medium: 50-500 nodes, 0-500/month
- Large: 500+ nodes, multi-region, >00/month

**Security**:
- L1→L2: PSK in MQTT
- L2→L3: TLS client certs
- API: JWT with RBAC
- Network isolation (sensor VLAN)

Production-ready architecture guide! 🏗️
@addidea addidea requested a review from Tonyfudecai as a code owner February 16, 2026 07:51
@addidea addidea closed this by deleting the head repository Mar 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: create deployment architecture diagram

1 participant