MetaSpace V3.2 | Neural Sandbox

Subsystem network

Click a node, or use its Fail button in the table, to fail it. Lines show which subsystems talk to each other in this model.

What this simulates, and what is assumed

Eight Landsat-9 subsystems as a graph. Fail nodes and the model recomputes a mission decision, then repairs nodes step by step (one cycle every 3 s) as long as a power node is alive.

Feasibility = weighted mean of four module healths; a failed node counts as 0 %. Weights: payload 35 %, power 30 %, navigation 20 %, communications 15 %.

≥ 90 %	CONTINUE_NOMINAL
≥ 75 %	CONTINUE_WITH_MONITORING
≥ 60 %	REDUCE_IMAGING_RATE
≥ 40 %	SWITCH_TO_FALLBACK
≥ 20 %	SAFE_MODE
< 20 % or power module < 20 %	EMERGENCY_HALT

Repair adds velocity × (1 + safety margin / 100) health points per cycle to every damaged node, unless the action is SAFE_MODE or EMERGENCY_HALT, feasibility is ≤ 20 % or no power node is alive.

Assumed, not mission data: the weights, thresholds, repair rule and the links between nodes. Node names follow real Landsat-9 hardware. This is an illustrative model: not flight software, not formally proved, not certified. The runtime checks below only test this model for internal consistency.

Bio-code is a compact hexadecimal word encoding the state: Level 1 per node, Level 2 per module, Level 3 the mission decision (day, feasibility, action, safety margin).

Controls

Repair velocity (health points per 3 s cycle, before the safety-margin boost)

8.5

Each node fails with probability 0.4, drawn in your browser. Everything after that is deterministic.

Mission decision

Action

CONTINUE_NOMINAL

Feasibility

100.00%

Safety margin

points above the model's 40 % threshold

Level 3 bio-code

no data yet

Self-repair

Nothing to repair.

Nodes

Node	Module	Health

Event log

> Ready. Fail a node to start.