SpaceMesh: Autonomous Telemetry Workflow Engine

THE PROBLEM: Space and satellite data engineers building real-time telemetry pipelines face three severe developer workflow bottlenecks: 1. Brittle Manual DAG Wiring: Adding a new orbital, radiation, or collision-analysis model requires manually rewriting DAG dependency files and restarting the orchestration server, causing pipeline downtime. 2. Telemetry Payload Bloat: Raw satellite API streams contain massive unrequested sensor noise and redundant fields, wasting downlink bandwidth, memory, and downstream compute/token budgets. 3. Pipeline Fragility Under Load: Sudden telemetry bursts or upstream API rate limits crash static pipelines, forcing engineers to manually intervene, debug schema mismatches, and restart workers. THE SOLUTION — SPACEMESH: SpaceMesh is an autonomous, self-healing developer workflow mesh that ingests live, keyless telemetry from the International Space Station (NORAD 25544) and NASA JPL Close-Approach APIs and orchestrates processing nodes automatically. TARGET USERS & HOW THEY INTERACT: Built for space systems engineers, telemetry pipeline developers, and edge-compute architects. Developers simply drop a Python node class inheriting from `SpaceMeshNode` into the `/nodes/` directory and monitor the workflow via the SpaceMesh Live Mission Dashboard (Streamlit). Through the dashboard, users stream live NASA/ISS packets, inspect the auto-wired DAG topology, monitor stripped payload keys, view real-time maneuver advisories, and trigger live hot-plugging and burst simulations. WHAT MAKES IT CREATIVE, UNIQUE & EFFICIENT: - Zero-Restart Dynamic DAG Discovery: `MeshOrchestrator` scans `/nodes/*.py` at runtime, reads each node's `required_inputs` and `produced_outputs`, and automatically wires the execution order using Kahn's topological sort algorithm—allowing developers to hot-add new nodes (like our Geomagnetic Storm Detector) with zero server restarts. - Intelligent Node I/O Pruning: Each node runs `analyze_and_filter_io()`, stripping unrequested upstream keys and reducing raw payload size by 70.5% to 79.3% before forwarding data downstream. - Self-Healing & Auto-Scaling Runtime: SpaceMesh dynamically scales async worker replicas from 1 to 8 per node based on queue depth and latency (processing packets in ~0.1–1.0 ms) and wraps every node in a stateful Circuit Breaker (`CLOSED -> OPEN -> HALF_OPEN`) with automated fallback injection so a failing node or rate-limited API never crashes the mission pipeline.