Orbital darkness is less a threat than a test. A satellite treats every eclipse not as an emergency but as a planned entry into battery mode, scripted with the same care as a launch sequence and enforced by hardware that refuses to improvise.
The core trick is simple and ruthless. Charge by day, spend by night. During sunlit arcs, solar arrays feed both the operating bus and rechargeable cells, pushing current through maximum power point tracking units that squeeze as much energy as possible from each square meter of photovoltaic surface while the geometry is favorable. System engineers pre‑compute an energy balance for the entire orbit, then lock it into the power budget that decides which instruments may run, which heaters may cycle, and which tasks must wait.
Survival in shadow depends less on glamour payloads than on discipline. Once the satellite crosses into umbra, power conditioning and distribution electronics pull almost everything from batteries, while priority loads such as attitude control, onboard computer cores and thermal regulation stay latched on. Nonessential subsystems are shed by design through load shedding tables embedded in fault protection logic. State of charge limits, depth of discharge margins and cell temperature bounds are enforced to protect electrochemistry from damage, so the craft does not win a single eclipse at the cost of failing the next.
The harshest constraint is not space vacuum but accounting. Every orbit repeats the same cycle of harvest, storage and controlled depletion, turning the satellite into a closed energy ledger that must balance exactly, or go dark for good.
