Spaces:
Running
Running
| NACC System Architecture | |
| ======================== | |
| Overview: | |
| NACC uses a Hub-and-Spoke architecture where a central Orchestrator | |
| manages multiple distributed Nodes. | |
| Components: | |
| 1. Main Space (Orchestrator) | |
| - Central brain of the system | |
| - Hosts the Gradio UI | |
| - Routes commands to appropriate nodes | |
| - Manages node registry | |
| - Integrates with AI backends | |
| 2. VM Space (Node) | |
| - Lightweight agent | |
| - Executes commands locally | |
| - Reports system metrics | |
| - Restricted by security policies | |
| 3. Communication | |
| - Protocol: HTTP with JSON payloads | |
| - Authentication: Token-based (optional) | |
| - Transport: HTTPS for cross-space | |
| - Error handling: Graceful degradation | |
| 4. Security | |
| - Command whitelisting | |
| - Path restrictions | |
| - No shell injection vulnerabilities | |
| - Read-only file systems where applicable | |
| Flow: | |
| User -> UI -> Orchestrator -> AI Backend -> Node Selection -> Command Execution -> Response | |