Architecture Overview

OpenStrate is built on a distributed, asynchronous architecture that prioritizes security, isolation, and observability.

The Nova Ignition Flow

The process of deploying code to the constellation is known as Nova Ignition.

1. Submission: A user submits a prompt via CLI, Aperture, or VS Code.
2. Uplink Processing: openstrate-uplink (Nova) uses generative AI to analyze the request and generate:
   • Executable code (Python/Bash).
   • A blueprint (UI schema for Aperture).
   • Requirement metadata (CPU, Memory, GPU).
3. Staging: The artifacts are pushed to openstrate-relay.
4. Discovery: openstrate-cli and openstrate-aperture use an Async mDNS Discovery Engine to locate the constellation and satellites.
5. Persistence: The mission state and job metadata are persisted in the Constellation's Redis-backed state engine to ensure durability across restarts.
6. Handshake: The selected Satellite pulls the artifacts from the Relay, verifying integrity.
7. Execution: The Satellite initializes a bubblewrap jail and executes the code with strict resource quotas.
8. Telemetry: High-frequency vitals and logs are streamed via ZMQ/WebSockets for real-time observation.

Networking & Data Plane

OpenStrate uses a hybrid networking model:

• Control Plane: mDNS ( Zeroconf) for service discovery.
• Data Plane: Direct HTTP/ZMQ links for artifact transfer and command dispatch.

IMPORTANT

Firewall Requirements: For remote satellites (e.g. Windows/WSL) to function, they must be able to reach the Relay service on your main PC. If your PC has a firewall (like ufw), you must explicitly allow the Relay's current port.

Component Relationship