|
1 | | -# Sentinel Network |
| 1 | +# Sentinel Network v4.6 |
2 | 2 |
|
3 | | -Systems-level modeling and simulation of a fault-tolerant Mars orbital relay constellation. |
| 3 | +**Mars Global Monitoring & Infrastructure Constellation** |
4 | 4 |
|
5 | | ---- |
6 | | - |
7 | | -## Overview |
8 | | - |
9 | | -Future Mars surface operations—human and robotic—will require continuous, low-latency, and resilient communications coverage. Today’s relay architecture relies on a small number of aging orbiters performing multiple roles simultaneously, creating single points of failure and constraining operational scale. |
10 | | - |
11 | | -Sentinel Network explores an alternative: a dense, fault-tolerant orbital relay layer designed explicitly as shared infrastructure rather than as a set of multi-mission flagship orbiters. In Sentinel, each satellite functions as a communications node, providing line-of-sight and store-and-forward connectivity between Mars surface assets, orbital users, and Earth relay paths. |
12 | | - |
13 | | -This repository contains open simulations and systems-level analyses that evaluate the feasibility, performance, and failure tolerance of such a network. |
| 5 | +A systems-level study of a fault-tolerant, cognitive-sensing orbital constellation designed as shared planetary infrastructure. |
14 | 6 |
|
15 | 7 | --- |
16 | 8 |
|
17 | | -## Problem Statement |
| 9 | +## Overview |
18 | 10 |
|
19 | | -Mars communications today face several structural limitations: |
| 11 | +Sentinel Network explores a fundamentally different approach to Mars orbital infrastructure: a dense, resilient constellation that combines **global synoptic monitoring** with **onboard cognitive intelligence** to deliver persistent awareness, low-latency decision support, and graceful degradation under failure. |
20 | 12 |
|
21 | | -- Reliance on a small number of critical relay assets |
22 | | -- Increasing data demand from surface operations |
23 | | -- Limited fault tolerance and graceful degradation |
24 | | -- Growing latency and availability constraints for autonomous systems |
| 13 | +Rather than relying on a small number of high-value relay orbiters, Sentinel distributes capability across 168 satellites, each carrying a dual-layer cognitive payload (wide-field global sensors + narrow-field AI-triggered inspection). The system is designed to operate as **planetary infrastructure** — supporting multiple users, missions, and operators over multi-decade lifetimes while maintaining performance even under significant satellite loss. |
25 | 14 |
|
26 | | -As surface activity scales, data transport—not sensing or computation—becomes the primary bottleneck. |
| 15 | +This repository contains the open simulations, analyses, and visualizations that define and validate the v4.6 architecture. |
27 | 16 |
|
28 | 17 | --- |
29 | 18 |
|
30 | | -## What Sentinel Is |
31 | | - |
32 | | -Sentinel Network is a conceptual Mars orbital relay constellation designed around the following principles: |
33 | | - |
34 | | -- **Fault tolerance by design** |
35 | | - No single satellite is mission-critical; resilience is achieved at the constellation and network layers. |
| 19 | +## What Sentinel Actually Is |
36 | 20 |
|
37 | | -- **Graceful degradation** |
38 | | - Network performance degrades predictably under partial or catastrophic loss, rather than via abrupt service failures. |
| 21 | +- **Dual-layer cognitive payload** on every satellite (global synoptic + AI-gated narrow-field inspection) |
| 22 | +- **Closed-loop autonomy** — onboard AI that detects, classifies, prioritizes, and retasks faster than light time to Earth |
| 23 | +- **Extreme fault tolerance** — graceful degradation even under 75% satellite loss |
| 24 | +- **Long-term infrastructure behavior** — 10+ year power/compute degradation modeling with adaptive modes |
| 25 | +- **Radiation-adaptive intelligence** — AI and sensors intelligently throttle or safe themselves during SEP events |
| 26 | +- **End-to-end latency modeling** — from event on Mars surface to actionable awareness on Earth |
39 | 27 |
|
40 | | -- **Infrastructure-first architecture** |
41 | | - A payload-agnostic relay layer that can support multiple missions, operators, and users over time. |
42 | | - |
43 | | -- **Scalable deployment** |
44 | | - Constellation sizing and orbital regimes are selected for long operational lifetimes, volumetric efficiency, and compatibility with bulk deployment. |
| 28 | +Sentinel is not just a communications relay. It is a **planetary nervous system** with onboard decision-making capability. |
45 | 29 |
|
46 | 30 | --- |
47 | 31 |
|
48 | | -## Key Characteristics (Current Model) |
49 | | - |
50 | | -- Constellation size: 168 satellites |
51 | | -- Function: Communications and navigation relay |
52 | | -- Coverage: Global Mars surface coverage |
53 | | -- Performance focus: Revisit time, availability, and resilience under loss |
54 | | -- Deployment philosophy: Bulk deployment compatible with high-capacity launch systems, without dependence on a specific launch vehicle |
55 | | -- Operational lifetime: Long-duration orbital regimes (multi-decade class) |
| 32 | +## Key Results (v4.6) |
56 | 33 |
|
57 | | -Quantitative performance results and failure-mode analyses are implemented in the simulations and supporting documentation within this repository. |
| 34 | +| Metric | Performance | Notes | |
| 35 | +|-------------------------------------|--------------------------------------|-------| |
| 36 | +| Mean global revisit (nominal) | ~1.0–1.5 minutes | Wide-FOV MARCI-class sensors | |
| 37 | +| Mean global revisit (75% loss) | Still under 10 minutes | Extreme resilience demonstrated | |
| 38 | +| End-to-end awareness latency | Minutes to low hours | Even in catastrophic scenarios | |
| 39 | +| Decision/retasking latency | Seconds (local) to minutes (global) | Faster than light time | |
| 40 | +| Propulsion-limited lifetime | 40+ years | With conservative margins | |
| 41 | +| Worst-case stacked failure survival | Survives (battery >0%) | Dust + eclipse + 500× SEP + 43% loss | |
58 | 42 |
|
59 | 43 | --- |
60 | 44 |
|
61 | | -## Repository Contents |
| 45 | +## Repository Structure |
62 | 46 |
|
63 | 47 | ```text |
64 | 48 | Sentinel-Network/ |
65 | | -├── README.md — Project overview and context |
66 | | -├── LICENSE — MIT License |
67 | | -├── simulations/ — Coverage, revisit, and loss-tolerance modeling |
68 | | -├── docs/ — Architecture summary and modeling scope |
69 | | -│ ├── architecture_summary.md |
70 | | -│ └── modeling_scope.md |
71 | | -├── figures/ — Generated plots and constellation visuals |
72 | | -└── data/ — Constants and reference parameters |
73 | | -``` |
74 | | - |
75 | | -This layout separates core simulations, documentation, figures, and reference data to support reproducible analysis and external review. |
76 | | - |
77 | | ---- |
78 | | - |
79 | | -## Fault Tolerance Model |
80 | | - |
81 | | -Fault tolerance is achieved at the constellation level through redundancy, spatial diversity, and orbital geometry rather than through highly complex, internally fault-tolerant satellites. |
82 | | - |
83 | | -Satellite loss—whether isolated, clustered, or catastrophic—is treated as an expected operating condition. Network performance degrades in a predictable and quantifiable manner as nodes are lost, instead of exhibiting sharp thresholds or single-point failures. |
84 | | - |
85 | | ---- |
| 49 | +├── README.md |
| 50 | +├── LICENSE |
| 51 | +├── scripts/ # Polished analysis scripts |
| 52 | +├── figures/ # Generated plots and animations |
| 53 | +├── docs/ # Architecture notes |
| 54 | +└── simulations/ # Original/raw versions + reference files |
86 | 55 |
|
87 | | -## Non-Goals |
| 56 | +Core Principles |
88 | 57 |
|
89 | | -This project intentionally does **not** attempt to: |
| 58 | +Fault tolerance by design — No single satellite is mission-critical |
| 59 | +Graceful degradation — Performance declines predictably, never catastrophically |
| 60 | +Closed-loop autonomy — Onboard AI makes decisions without waiting for Earth |
| 61 | +Infrastructure-first — Built for long-term, multi-user, multi-mission use |
| 62 | +Conservative modeling — All analyses intentionally use pessimistic assumptions |
90 | 63 |
|
91 | | -- Replace high-data-rate science orbiters or flagship missions |
92 | | -- Specify detailed RF link budgets, modulation schemes, or hardware designs |
93 | | -- Optimize for mission-specific payloads or proprietary architectures |
94 | | -- Address surface terminal, user equipment, or ground network implementation details |
95 | | - |
96 | | -The focus is on first-order system behavior, architectural feasibility, and fault-tolerance characteristics. |
97 | | - |
98 | | ---- |
99 | | - |
100 | | -## Relationship to Existing Mars Assets |
101 | | - |
102 | | -Sentinel Network is intended to complement existing and future Mars orbiters by providing a dedicated, resilient communications infrastructure layer optimized for availability and continuity. |
103 | | - |
104 | | -Science orbiters and specialized missions remain responsible for high-value sensing and data generation, while Sentinel provides a persistent relay backbone capable of supporting scaled surface operations and multi-user demand. |
105 | | - |
106 | | ---- |
107 | | - |
108 | | -## Project Status |
109 | | - |
110 | | -**Active and evolving.** |
111 | | - |
112 | | -- Core simulations: initial set complete |
113 | | -- Documentation: in progress |
114 | | -- Higher-fidelity modeling: planned |
115 | | -- External review, critique, and extension: encouraged |
116 | | - |
117 | | -This repository represents an open systems study, not a finalized design or flight program. |
118 | | - |
119 | | ---- |
120 | | - |
121 | | -## License |
122 | | - |
123 | | -This project is released under the MIT License. Reuse, modification, and extension are encouraged with attribution. |
124 | | - |
125 | | ---- |
126 | 64 |
|
127 | | -## Disclaimer |
| 65 | +Project Status |
| 66 | +v4.6 Complete — Full systems-level modeling suite finished. |
| 67 | +This is an open technical study. All scripts, models, and visualizations are released for review, critique, extension, and reuse. |
128 | 68 |
|
129 | | -This work is an independent technical exploration. It is not affiliated with, endorsed by, or representative of any space agency or commercial entity. |
| 69 | +License |
| 70 | +MIT License — reuse, modify, and extend freely with attribution. |
0 commit comments