[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AQ0VSJPCQXMZ5CC3CPHFA1":3,"skill-same:01M7AQ0VSJPCQXMZ5CC3CPHFA1":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AQ0VSJPCQXMZ5CC3CPHFA1","endeavour-satellites-flight-software-and-instruments",null,"Use when designing or reviewing a satellite or space probe — picking an orbit regime and understanding the constraint that defines it, writing flight software whose hardware flips its own bits, building FDIR and a safe mode that survives a month, designing commands and telemetry to CCSDS, planning an in-flight software update, choosing science instruments against mass, power and data-volume budgets, or meeting planetary protection requirements. Part 7 of 12 of the Military Science, Rockets, Space, Fusion, and Mars reference.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fmilitary-space-rockets-and-fusion\u002Fskills\u002Fendeavour-satellites-flight-software-and-instruments\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: endeavour-satellites-flight-software-and-instruments\ndescription: \"Use when designing or reviewing a satellite or space probe — picking an orbit regime and understanding the constraint that defines it, writing flight software whose hardware flips its own bits, building FDIR and a safe mode that survives a month, designing commands and telemetry to CCSDS, planning an in-flight software update, choosing science instruments against mass, power and data-volume budgets, or meeting planetary protection requirements. Part 7 of 12 of the Military Science, Rockets, Space, Fusion, and Mars reference.\"\n---\n\n# Satellites, Flight Software, Instruments, and Planetary Protection\n\n> **Part 7 of 12** of the *Military Science, Rockets, Space, Fusion, and Mars* reference (plugin\n> `military-space-rockets-and-fusion`), covering §26–§28 — bus and payload with the orbit regimes and\n> the constraint that defines each, flight software from FDIR to in-flight update, scientific\n> instrumentation, and planetary protection. Sibling skills:\n> `endeavour-military-theory-levels-of-war-and-deterrence` (§1–§3 — what military science is, Clausewitz and the canon, the levels of war, deterrence and nuclear strategy),\n> `endeavour-logistics-doctrine-modern-conflict-and-the-law` (§4–§6 — force structure and logistics, doctrine, intelligence and procurement, modern conflict, and the law of armed conflict),\n> `endeavour-rocket-equation-nozzles-engines-and-propellants` (§7–§10 — Tsiolkovsky and staging, nozzle thermodynamics and the chamber, turbomachinery, engine cycles and cooling, propellants and density impulse),\n> `endeavour-orbits-ascent-structures-and-reentry` (§11–§16 — vis-viva, manoeuvres and perturbations, the ascent Δv budget, aerodynamic loads and structures, guidance and control, reentry physics, failure physics),\n> `endeavour-mission-architecture-and-spacecraft-subsystems` (§17–§22 — mission architecture, power and thermal, communications, navigation and autonomy, attitude control, in-space propulsion and EDL, human physiology, life support and ISRU, reliability and margins),\n> `endeavour-fusion-physics-confinement-and-engineering` (§23–§25 — fusion physics and the Lawson criterion, magnetic and inertial confinement, why fusion is hard to engineer, and the nuclear background),\n> `endeavour-the-martian-environment-and-in-situ-resources` (§29–§30 — Mars as engineering parameters, and Mars resources and ISRU),\n> `endeavour-mars-mission-design-and-settlement` (§31–§32 — Mars mission design, and habitats, mobility, ECLSS closure and the psychological challenge),\n> `endeavour-terraforming-warming-and-the-magnetic-field-problem` (§33–§35 — terraforming theory and the three thresholds, atmospheric thickening and warming, the magnetic field problem),\n> `endeavour-ecopoiesis-oxygen-timelines-and-ethics` (§36–§38 — ecopoiesis and the oxygen problem, timelines and paraterraforming, ethics, governance and Venus),\n> `endeavour-reference` (§39–§40 — the complete glossary and the complete further-reading list),\n>\n> Section numbers are **shared across the whole set**: a reference written as §N → `skill` points\n> into that sibling skill. The physics and the design principles here are durable; specific missions,\n> standards revisions and flight-hardware practice do move.\n\nA satellite or space probe is a **spacecraft bus** — the supporting infrastructure — plus a\n**payload**, the instrument or communication package that justifies the mission. The bus provides\npower, thermal control, attitude control, propulsion, communications, command and data handling, and\nstructure. The payload is what the mission is *for*. Everything else in this skill is what happens\nwhen that payload has to survive, be commanded, and return its data.\n\n---\n\n## §26 Satellite and space probe design, types, and orbits\n\n> **EVERYTHING IN THE DESIGN REDUCES TO MASS.** Power converts to mass, data rate converts to mass,\n> reliability converts to mass — and propellant mass is *exponential* in Δv. That last clause is why\n> the conversion is not a fair trade: an extra kilogram of payload is paid for at the mass ratio of\n> every burn that follows it. The exponent is Tsiolkovsky's (§7 →\n> `endeavour-rocket-equation-nozzles-engines-and-propellants`); the design cascade that this\n> bookkeeping drives is §17 → `endeavour-mission-architecture-and-spacecraft-subsystems`.\n\nThe bus subsystems themselves — power, thermal, communications, navigation, attitude control and\nin-space propulsion — are covered in §18–§20 →\n`endeavour-mission-architecture-and-spacecraft-subsystems`. What follows is the orbit side: where a\nspacecraft is put, and the one constraint that governs each regime.\n\n### Satellite types and orbits\n\n| Type | Orbit | Primary Use | Key Constraint |\n|---|---|---|---|\n| LEO communications | 400–1,200 km | Starlink, Iridium, Earth observation | Drag, constellation management |\n| Sun-synchronous | 600–900 km, ~98° | Imaging, weather, reconnaissance | Consistent lighting via J₂ precession |\n| GEO communications | 35,786 km, 0° | TV, data relay, weather | Station-keeping ~50 m\u002Fs\u002Fyr, latency |\n| Molniya | Highly elliptical, 63.4° | High-latitude communications | Apsidal precession frozen by inclination |\n| Navigation | MEO ~20,000 km | GPS, Galileo, GLONASS | Constellation geometry, atomic clock stability |\n| Scientific (deep space) | Interplanetary | Planetary probes, observatories | Power (solar 1\u002Fr²), light-time, autonomy |\n\n**Reading the table — each row is a different binding constraint, not a different altitude.**\n\n- **LEO communications, 400–1,200 km.** Drag is the governing physical effect and constellation\n  management the governing operational one — the first sets how long a satellite lasts and how\n  uncertain its reentry date is, the second is the standing problem of keeping many satellites\n  phased, separated and replaced. Drag's altitude and solar-activity dependence is §11 →\n  `endeavour-orbits-ascent-structures-and-reentry`.\n- **Sun-synchronous, 600–900 km at ~98°.** The retrograde inclination is chosen so that J₂ nodal\n  regression matches Earth's mean motion about the Sun, holding local solar time constant so every\n  image of a site is taken under the same lighting. It is a perturbation exploited rather than\n  fought; the geometry is §11 → `endeavour-orbits-ascent-structures-and-reentry`.\n- **GEO communications, 35,786 km at 0°.** Two constraints, both permanent: **station-keeping at\n  ~50 m\u002Fs\u002Fyr**, which sets the propellant the spacecraft must carry for its whole service life\n  (§20 → `endeavour-mission-architecture-and-spacecraft-subsystems`), and **latency**, which is\n  simply the distance and does not improve.\n- **Molniya, highly elliptical at 63.4°.** The inclination is not a coverage choice — it is the\n  value that **freezes apsidal precession**, so apogee stays where it was put and the long slow\n  apogee pass keeps recurring over the same high-latitude region: §11 →\n  `endeavour-orbits-ascent-structures-and-reentry`.\n- **Navigation, MEO ~20,000 km.** Constrained by **constellation geometry** — a user's position fix\n  is only as good as the spread of satellites in view — and by **atomic clock stability**, because\n  the measurement being made is time.\n- **Scientific, interplanetary.** Three constraints at once: **power**, because solar flux falls as\n  1\u002Fr² (§18 → `endeavour-mission-architecture-and-spacecraft-subsystems`); **light-time**, which\n  makes teleoperation impossible beyond the Moon; and **autonomy**, which is forced by that\n  light-time rather than chosen (§19 →\n  `endeavour-mission-architecture-and-spacecraft-subsystems`). Autonomy is where this skill picks up\n  the thread: it has to be implemented in software, on a computer that is being irradiated.\n\n---\n\n## §27 Flight software: FDIR, command and telemetry, and in-flight update\n\nThree properties make spacecraft software different from all other software.\n\n1. **You cannot patch your way out.** Uplink is bandwidth-limited, latency-bound, and sometimes\n   impossible. A bug that bricks the receiver ends the mission.\n2. **The hardware is actively hostile.** Radiation flips bits in RAM and registers with no warning\n   and no error signal. Software must assume its own memory is corrupting underneath it.\n3. **Correct-but-late is wrong.** A control loop that misses its deadline has failed regardless of\n   the answer it eventually produces.\n\n> **DETERMINISM OUTRANKS THROUGHPUT.** That ordering inverts almost every instinct from server-side\n> engineering, where throughput is the headline number and a late answer is merely slow. Here a late\n> answer is a wrong answer, and a fast average with an unbounded tail is a failed design.\n\n### FDIR: fault detection, isolation, and recovery\n\nFDIR is **the organizing principle of flight software, not a feature of it**. The chain:\n\n- **Detect** — limit checks, watchdogs, consistency checks, checksums, heartbeat monitors.\n- **Isolate** — determine *which* component, avoiding misattribution. This is **the hardest step**:\n  a detector fires on a symptom, and the symptom is rarely local to the fault.\n- **Recover** — an escalation ladder: retry → reconfigure to a redundant unit → reset component →\n  reset processor → safe mode. Redundancy types and common-cause failure are §22 →\n  `endeavour-mission-architecture-and-spacecraft-subsystems`.\n\n**Safe mode is the design that saves missions**: power-positive, thermally stable, Sun- or\nEarth-pointed, minimal software, survivable indefinitely awaiting ground instruction. Every\ndeep-space mission enters safe mode. **The design question is not whether, but whether it can sit\nthere for a month without degrading.** The operational companions to safe mode — command loss timers\nthat reconfigure after N days without contact — are §19 →\n`endeavour-mission-architecture-and-spacecraft-subsystems`.\n\n### The hard-won lessons\n\n- **Fault protection that misfires is itself a hazard.** A spurious safe-mode entry during orbit\n  insertion or EDL can lose the mission, so critical sequences **inhibit selected fault responses**.\n- **Don't recover into the fault.** Repeated automatic resets that re-trigger the same condition burn\n  power and can exhaust a resource.\n- **Log everything before acting.** The telemetry that explains a fault is often lost in the recovery\n  that follows it.\n\n### Command and telemetry\n\n**CCSDS is the international standard set, and it is genuinely worth following rather than\ninventing.** Command design principles:\n\n- **Idempotent where possible** — a retransmitted command should not do the thing twice.\n- **Two-stage arm\u002Ffire for hazardous commands** — deployments, pyros, engine starts.\n- **Validate before execute** — checksum, authenticate, range-check every parameter.\n- **Reject, don't clamp.** Silently clamping an out-of-range parameter hides the ground error that\n  produced it, which is the error you actually needed to see.\n\nFour telemetry types, each doing a different job:\n\n| Type | What it is | Why it exists |\n|---|---|---|\n| Housekeeping | Periodic state | The continuous health picture |\n| Event \u002F EVR messages | The spacecraft's log | **Your only debugger** |\n| Science data | The payload's output | The reason for the mission |\n| Diagnostic dwell | Read arbitrary memory addresses | Indispensable for in-flight debugging |\n\n**Design telemetry for the anomaly you haven't had yet.** The recurring operational regret is\ninsufficient telemetry to diagnose a fault after it occurs — and by then the channel list is fixed.\n\n### In-flight software update\n\n> **THE HIGHEST-STAKES OPERATION IN THE DISCIPLINE.** Six design rules, each written in blood:\n> (1) the bootloader must be immutable, or dual-redundant with a golden image; (2) uplink to inactive\n> memory, verify checksum, then switch; (3) automatic rollback on failure to check in after N\n> minutes; (4) never patch the receive chain and the patch mechanism at once; (5) test the exact\n> uplink product on the exact testbed configuration; (6) keep patch granularity small enough to fit\n> the uplink budget. **A failed update that bricks the command receiver is unrecoverable and has\n> ended missions.**\n\nThe counterexample worth knowing: **Voyager received a software patch in 2023–24 to work around\ndegraded memory, 46 years after launch**, on a system whose original engineers had retired or died.\nThat is only possible because the update path was designed conservatively from the start — the whole\ncase for rules that look paranoid on the ground.\n\n---\n\n## §28 Scientific instrumentation and planetary protection\n\n**The measurement drives the mission.** Instrument selection is the first real decision in the design\ncascade, and everything downstream — pointing, power, data volume, thermal — is sized from it\n(§17 → `endeavour-mission-architecture-and-spacecraft-subsystems`).\n\n### The instrument families\n\n**Remote sensing:**\n\n- **Imagers** — visible, IR, UV.\n- **Spectrometers** — reflectance, emission, Raman, and **mass spectrometers, the workhorses doing\n  most of the compositional science**.\n- **Radar and sounders** — subsurface structure.\n- **Lidar and altimeters.**\n- **Magnetometers** — usually on a boom, because the spacecraft is magnetically dirty.\n- **Particle and field instruments.**\n\n**In situ:**\n\n- **APXS.**\n- **LIBS** — laser composition at standoff distance, **which transformed rover operations**, because\n  it removes the need to drive to and contact every target before knowing what it is.\n- **Gas chromatograph–mass spectrometers.**\n- **Seismometers.**\n- **Meteorology packages.**\n- **Drills and sample handling.**\n\n### The constraints that shape instrument design\n\nMass and power; **data volume, often the true limit on science return** rather than instrument\ncapability — the link budget behind that limit, and the Voyager and New Horizons numbers that show\nit, are §19 → `endeavour-mission-architecture-and-spacecraft-subsystems`; thermal and cryogenic\nneeds; radiation tolerance; **calibration using onboard targets, because you cannot recalibrate\nagainst a lab standard after launch**; contamination control; and pointing stability.\n\n### Planetary protection\n\nLegally grounded in the **Outer Space Treaty (1967), Article IX**, and implemented through **COSPAR\npolicy**.\n\n| Category | Scope | What it imposes |\n|---|---|---|\n| I | No interest — Moon, Sun | — |\n| II | Interest, remote contamination risk | Documentation only |\n| III \u002F IV | Mars, Europa, Enceladus | Bioburden limits, cleanroom assembly, and for some categories sterilization |\n| V | Sample return | \"Restricted Earth return\" requires containment on the way back |\n\n**Two directions, two different worries.** **Forward contamination** protects the science — finding\nyour own Earth microbes and calling it life would be the worst possible outcome — and arguably any\nindigenous biosphere. **Backward contamination** is the sample-return problem.\n\nThe methods: **dry heat microbial reduction** — Viking baked its entire lander at **112 °C for 30\nhours**, expensive and hard on hardware; **vapour hydrogen peroxide**; **cleanroom assembly**; and\n**bioburden assay**.\n\n> **CATEGORY IV CLOSES OFF PRECISELY WHERE THE ASTROBIOLOGY IS.** Compliance materially constrains\n> design, adds cost, and restricts where you may land: **special regions — where liquid water might\n> exist — are effectively off-limits to non-sterilized hardware.** The Martian conditions a special\n> region turns on — the **580 Pa CO₂ partial pressure** against water's **611 Pa** triple point, and\n> the **perchlorate brines** that can exist transiently anyway — are §29 →\n> `endeavour-the-martian-environment-and-in-situ-resources`; the ethical\n> question this framework exists to hold open — whether a biosphere may be extinguished to make a\n> second Earth — is §38 → `endeavour-ecopoiesis-oxygen-timelines-and-ethics`.\n","# Satellites, Flight Software, Instruments, and Planetary Protection\n\n> **Part 7 of 12** of the *Military Science, Rockets, Space, Fusion, and Mars* reference (plugin\n> `military-space-rockets-and-fusion`), covering §26–§28 — bus and payload with the orbit regimes and\n> the constraint that defines each, flight software from FDIR to in-flight update, scientific\n> instrumentation, and planetary protection. Sibling skills:\n> `endeavour-military-theory-levels-of-war-and-deterrence` (§1–§3 — what military science is, Clausewitz and the canon, the levels of war, deterrence and nuclear strategy),\n> `endeavour-logistics-doctrine-modern-conflict-and-the-law` (§4–§6 — force structure and logistics, doctrine, intelligence and procurement, modern conflict, and the law of armed conflict),\n> `endeavour-rocket-equation-nozzles-engines-and-propellants` (§7–§10 — Tsiolkovsky and staging, nozzle thermodynamics and the chamber, turbomachinery, engine cycles and cooling, propellants and density impulse),\n> `endeavour-orbits-ascent-structures-and-reentry` (§11–§16 — vis-viva, manoeuvres and perturbations, the ascent Δv budget, aerodynamic loads and structures, guidance and control, reentry physics, failure physics),\n> `endeavour-mission-architecture-and-spacecraft-subsystems` (§17–§22 — mission architecture, power and thermal, communications, navigation and autonomy, attitude control, in-space propulsion and EDL, human physiology, life support and ISRU, reliability and margins),\n> `endeavour-fusion-physics-confinement-and-engineering` (§23–§25 — fusion physics and the Lawson criterion, magnetic and inertial confinement, why fusion is hard to engineer, and the nuclear background),\n> `endeavour-the-martian-environment-and-in-situ-resources` (§29–§30 — Mars as engineering parameters, and Mars resources and ISRU),\n> `endeavour-mars-mission-design-and-settlement` (§31–§32 — Mars mission design, and habitats, mobility, ECLSS closure and the psychological challenge),\n> `endeavour-terraforming-warming-and-the-magnetic-field-problem` (§33–§35 — terraforming theory and the three thresholds, atmospheric thickening and warming, the magnetic field problem),\n> `endeavour-ecopoiesis-oxygen-timelines-and-ethics` (§36–§38 — ecopoiesis and the oxygen problem, timelines and paraterraforming, ethics, governance and Venus),\n> `endeavour-reference` (§39–§40 — the complete glossary and the complete further-reading list),\n>\n> Section numbers are **shared across the whole set**: a reference written as §N → `skill` points\n> into that sibling skill. The physics and the design principles here are durable; specific missions,\n> standards revisions and flight-hardware practice do move.\n\nA satellite or space probe is a **spacecraft bus** — the supporting infrastructure — plus a\n**payload**, the instrument or communication package that justifies the mission. The bus provides\npower, thermal control, attitude control, propulsion, communications, command and data handling, and\nstructure. The payload is what the mission is *for*. Everything else in this skill is what happens\nwhen that payload has to survive, be commanded, and return its data.\n\n---\n\n## §26 Satellite and space probe design, types, and orbits\n\n> **EVERYTHING IN THE DESIGN REDUCES TO MASS.** Power converts to mass, data rate converts to mass,\n> reliability converts to mass — and propellant mass is *exponential* in Δv. That last clause is why\n> the conversion is not a fair trade: an extra kilogram of payload is paid for at the mass ratio of\n> every burn that follows it. The exponent is Tsiolkovsky's (§7 →\n> `endeavour-rocket-equation-nozzles-engines-and-propellants`); the design cascade that this\n> bookkeeping drives is §17 → `endeavour-mission-architecture-and-spacecraft-subsystems`.\n\nThe bus subsystems themselves — power, thermal, communications, navigation, attitude control and\nin-space propulsion — are covered in §18–§20 →\n`endeavour-mission-architecture-and-spacecraft-subsystems`. What follows is the orbit side: where a\nspacecraft is put, and the one constraint that governs each regime.\n\n### Satellite types and orbits\n\n| Type | Orbit | Primary Use | Key Constraint |\n|---|---|---|---|\n| LEO communications | 400–1,200 km | Starlink, Iridium, Earth observation | Drag, constellation management |\n| Sun-synchronous | 600–900 km, ~98° | Imaging, weather, reconnaissance | Consistent lighting via J₂ precession |\n| GEO communications | 35,786 km, 0° | TV, data relay, weather | Station-keeping ~50 m\u002Fs\u002Fyr, latency |\n| Molniya | Highly elliptical, 63.4° | High-latitude communications | Apsidal precession frozen by inclination |\n| Navigation | MEO ~20,000 km | GPS, Galileo, GLONASS | Constellation geometry, atomic clock stability |\n| Scientific (deep space) | Interplanetary | Planetary probes, observatories | Power (solar 1\u002Fr²), light-time, autonomy |\n\n**Reading the table — each row is a different binding constraint, not a different altitude.**\n\n- **LEO communications, 400–1,200 km.** Drag is the governing physical effect and constellation\n  management the governing operational one — the first sets how long a satellite lasts and how\n  uncertain its reentry date is, the second is the standing problem of keeping many satellites\n  phased, separated and replaced. Drag's altitude and solar-activity dependence is §11 →\n  `endeavour-orbits-ascent-structures-and-reentry`.\n- **Sun-synchronous, 600–900 km at ~98°.** The retrograde inclination is chosen so that J₂ nodal\n  regression matches Earth's mean motion about the Sun, holding local solar time constant so every\n  image of a site is taken under the same lighting. It is a perturbation exploited rather than\n  fought; the geometry is §11 → `endeavour-orbits-ascent-structures-and-reentry`.\n- **GEO communications, 35,786 km at 0°.** Two constraints, both permanent: **station-keeping at\n  ~50 m\u002Fs\u002Fyr**, which sets the propellant the spacecraft must carry for its whole service life\n  (§20 → `endeavour-mission-architecture-and-spacecraft-subsystems`), and **latency**, which is\n  simply the distance and does not improve.\n- **Molniya, highly elliptical at 63.4°.** The inclination is not a coverage choice — it is the\n  value that **freezes apsidal precession**, so apogee stays where it was put and the long slow\n  apogee pass keeps recurring over the same high-latitude region: §11 →\n  `endeavour-orbits-ascent-structures-and-reentry`.\n- **Navigation, MEO ~20,000 km.** Constrained by **constellation geometry** — a user's position fix\n  is only as good as the spread of satellites in view — and by **atomic clock stability**, because\n  the measurement being made is time.\n- **Scientific, interplanetary.** Three constraints at once: **power**, because solar flux falls as\n  1\u002Fr² (§18 → `endeavour-mission-architecture-and-spacecraft-subsystems`); **light-time**, which\n  makes teleoperation impossible beyond the Moon; and **autonomy**, which is forced by that\n  light-time rather than chosen (§19 →\n  `endeavour-mission-architecture-and-spacecraft-subsystems`). Autonomy is where this skill picks up\n  the thread: it has to be implemented in software, on a computer that is being irradiated.\n\n---\n\n## §27 Flight software: FDIR, command and telemetry, and in-flight update\n\nThree properties make spacecraft software different from all other software.\n\n1. **You cannot patch your way out.** Uplink is bandwidth-limited, latency-bound, and sometimes\n   impossible. A bug that bricks the receiver ends the mission.\n2. **The hardware is actively hostile.** Radiation flips bits in RAM and registers with no warning\n   and no error signal. Software must assume its own memory is corrupting underneath it.\n3. **Correct-but-late is wrong.** A control loop that misses its deadline has failed regardless of\n   the answer it eventually produces.\n\n> **DETERMINISM OUTRANKS THROUGHPUT.** That ordering inverts almost every instinct from server-side\n> engineering, where throughput is the headline number and a late answer is merely slow. Here a late\n> answer is a wrong answer, and a fast average with an unbounded tail is a failed design.\n\n### FDIR: fault detection, isolation, and recovery\n\nFDIR is **the organizing principle of flight software, not a feature of it**. The chain:\n\n- **Detect** — limit checks, watchdogs, consistency checks, checksums, heartbeat monitors.\n- **Isolate** — determine *which* component, avoiding misattribution. This is **the hardest step**:\n  a detector fires on a symptom, and the symptom is rarely local to the fault.\n- **Recover** — an escalation ladder: retry → reconfigure to a redundant unit → reset component →\n  reset processor → safe mode. Redundancy types and common-cause failure are §22 →\n  `endeavour-mission-architecture-and-spacecraft-subsystems`.\n\n**Safe mode is the design that saves missions**: power-positive, thermally stable, Sun- or\nEarth-pointed, minimal software, survivable indefinitely awaiting ground instruction. Every\ndeep-space mission enters safe mode. **The design question is not whether, but whether it can sit\nthere for a month without degrading.** The operational companions to safe mode — command loss timers\nthat reconfigure after N days without contact — are §19 →\n`endeavour-mission-architecture-and-spacecraft-subsystems`.\n\n### The hard-won lessons\n\n- **Fault protection that misfires is itself a hazard.** A spurious safe-mode entry during orbit\n  insertion or EDL can lose the mission, so critical sequences **inhibit selected fault responses**.\n- **Don't recover into the fault.** Repeated automatic resets that re-trigger the same condition burn\n  power and can exhaust a resource.\n- **Log everything before acting.** The telemetry that explains a fault is often lost in the recovery\n  that follows it.\n\n### Command and telemetry\n\n**CCSDS is the international standard set, and it is genuinely worth following rather than\ninventing.** Command design principles:\n\n- **Idempotent where possible** — a retransmitted command should not do the thing twice.\n- **Two-stage arm\u002Ffire for hazardous commands** — deployments, pyros, engine starts.\n- **Validate before execute** — checksum, authenticate, range-check every parameter.\n- **Reject, don't clamp.** Silently clamping an out-of-range parameter hides the ground error that\n  produced it, which is the error you actually needed to see.\n\nFour telemetry types, each doing a different job:\n\n| Type | What it is | Why it exists |\n|---|---|---|\n| Housekeeping | Periodic state | The continuous health picture |\n| Event \u002F EVR messages | The spacecraft's log | **Your only debugger** |\n| Science data | The payload's output | The reason for the mission |\n| Diagnostic dwell | Read arbitrary memory addresses | Indispensable for in-flight debugging |\n\n**Design telemetry for the anomaly you haven't had yet.** The recurring operational regret is\ninsufficient telemetry to diagnose a fault after it occurs — and by then the channel list is fixed.\n\n### In-flight software update\n\n> **THE HIGHEST-STAKES OPERATION IN THE DISCIPLINE.** Six design rules, each written in blood:\n> (1) the bootloader must be immutable, or dual-redundant with a golden image; (2) uplink to inactive\n> memory, verify checksum, then switch; (3) automatic rollback on failure to check in after N\n> minutes; (4) never patch the receive chain and the patch mechanism at once; (5) test the exact\n> uplink product on the exact testbed configuration; (6) keep patch granularity small enough to fit\n> the uplink budget. **A failed update that bricks the command receiver is unrecoverable and has\n> ended missions.**\n\nThe counterexample worth knowing: **Voyager received a software patch in 2023–24 to work around\ndegraded memory, 46 years after launch**, on a system whose original engineers had retired or died.\nThat is only possible because the update path was designed conservatively from the start — the whole\ncase for rules that look paranoid on the ground.\n\n---\n\n## §28 Scientific instrumentation and planetary protection\n\n**The measurement drives the mission.** Instrument selection is the first real decision in the design\ncascade, and everything downstream — pointing, power, data volume, thermal — is sized from it\n(§17 → `endeavour-mission-architecture-and-spacecraft-subsystems`).\n\n### The instrument families\n\n**Remote sensing:**\n\n- **Imagers** — visible, IR, UV.\n- **Spectrometers** — reflectance, emission, Raman, and **mass spectrometers, the workhorses doing\n  most of the compositional science**.\n- **Radar and sounders** — subsurface structure.\n- **Lidar and altimeters.**\n- **Magnetometers** — usually on a boom, because the spacecraft is magnetically dirty.\n- **Particle and field instruments.**\n\n**In situ:**\n\n- **APXS.**\n- **LIBS** — laser composition at standoff distance, **which transformed rover operations**, because\n  it removes the need to drive to and contact every target before knowing what it is.\n- **Gas chromatograph–mass spectrometers.**\n- **Seismometers.**\n- **Meteorology packages.**\n- **Drills and sample handling.**\n\n### The constraints that shape instrument design\n\nMass and power; **data volume, often the true limit on science return** rather than instrument\ncapability — the link budget behind that limit, and the Voyager and New Horizons numbers that show\nit, are §19 → `endeavour-mission-architecture-and-spacecraft-subsystems`; thermal and cryogenic\nneeds; radiation tolerance; **calibration using onboard targets, because you cannot recalibrate\nagainst a lab standard after launch**; contamination control; and pointing stability.\n\n### Planetary protection\n\nLegally grounded in the **Outer Space Treaty (1967), Article IX**, and implemented through **COSPAR\npolicy**.\n\n| Category | Scope | What it imposes |\n|---|---|---|\n| I | No interest — Moon, Sun | — |\n| II | Interest, remote contamination risk | Documentation only |\n| III \u002F IV | Mars, Europa, Enceladus | Bioburden limits, cleanroom assembly, and for some categories sterilization |\n| V | Sample return | \"Restricted Earth return\" requires containment on the way back |\n\n**Two directions, two different worries.** **Forward contamination** protects the science — finding\nyour own Earth microbes and calling it life would be the worst possible outcome — and arguably any\nindigenous biosphere. **Backward contamination** is the sample-return problem.\n\nThe methods: **dry heat microbial reduction** — Viking baked its entire lander at **112 °C for 30\nhours**, expensive and hard on hardware; **vapour hydrogen peroxide**; **cleanroom assembly**; and\n**bioburden assay**.\n\n> **CATEGORY IV CLOSES OFF PRECISELY WHERE THE ASTROBIOLOGY IS.** Compliance materially constrains\n> design, adds cost, and restricts where you may land: **special regions — where liquid water might\n> exist — are effectively off-limits to non-sterilized hardware.** The Martian conditions a special\n> region turns on — the **580 Pa CO₂ partial pressure** against water's **611 Pa** triple point, and\n> the **perchlorate brines** that can exist transiently anyway — are §29 →\n> `endeavour-the-martian-environment-and-in-situ-resources`; the ethical\n> question this framework exists to hold open — whether a biosphere may be extinguished to make a\n> second Earth — is §38 → `endeavour-ecopoiesis-oxygen-timelines-and-ethics`.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fmilitary-space-rockets-and-fusion\u002Fskills\u002Fendeavour-satellites-flight-software-and-instruments",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill endeavour-satellites-flight-software-and-instruments",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill endeavour-satellites-flight-software-and-instruments",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill endeavour-satellites-flight-software-and-instruments","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fmilitary-space-rockets-and-fusion\u002Fskills\u002Fendeavour-satellites-flight-software-and-instruments\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]