[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APYQ06XY4BXVMCC8ZH2K9F":3,"skill-same:01M7APYQ06XY4BXVMCC8ZH2K9F":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},"01M7APYQ06XY4BXVMCC8ZH2K9F","endeavour-mission-architecture-and-spacecraft-subsystems",null,"Use when sizing or trading a spacecraft mission — picking flyby versus orbiter versus lander, solar versus radioisotope power, chemical versus electric propulsion, direct versus gravity assist, relay versus direct-to-Earth — or when you need the numbers behind a bus subsystem: solar flux at Mars or Jupiter, RTG output and efficiency, radiator area at a given temperature, a deep space link budget and light-time, reaction wheel saturation, Isp by thruster type, the Mars EDL sequence and its landed-mass ceiling, crew radiation dose and SANS, ECLSS closure ratios, MOXIE's demonstrated output, or the standard mass and Δv margin schedule and the failures that produced it. Part 5 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-mission-architecture-and-spacecraft-subsystems\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: endeavour-mission-architecture-and-spacecraft-subsystems\ndescription: \"Use when sizing or trading a spacecraft mission — picking flyby versus orbiter versus lander, solar versus radioisotope power, chemical versus electric propulsion, direct versus gravity assist, relay versus direct-to-Earth — or when you need the numbers behind a bus subsystem: solar flux at Mars or Jupiter, RTG output and efficiency, radiator area at a given temperature, a deep space link budget and light-time, reaction wheel saturation, Isp by thruster type, the Mars EDL sequence and its landed-mass ceiling, crew radiation dose and SANS, ECLSS closure ratios, MOXIE's demonstrated output, or the standard mass and Δv margin schedule and the failures that produced it. Part 5 of 12 of the Military Science, Rockets, Space, Fusion, and Mars reference.\"\n---\n\n# Space Mission Architecture and Spacecraft Subsystems\n\n> **Part 5 of 12** of the *Military Science, Rockets, Space, Fusion, and Mars* reference (plugin\n> `military-space-rockets-and-fusion`), covering §17–§22 — mission architecture and the design cascade, power and thermal, communications and navigation, attitude control and EDL, human physiology and ISRU, and reliability. Sibling skills:\n> `endeavour-military-theory-levels-of-war-and-deterrence` (§1–§3 — what military science is, the theoretical canon, the levels of war, and deterrence and nuclear strategy),\n> `endeavour-logistics-doctrine-modern-conflict-and-the-law` (§4–§6 — force structure, logistics, doctrine, intelligence, procurement, modern conflict, and the law of armed conflict),\n> `endeavour-rocket-equation-nozzles-engines-and-propellants` (§7–§10 — the rocket equation and staging, nozzle thermodynamics and the combustion chamber, turbomachinery and cooling, and propellants),\n> `endeavour-orbits-ascent-structures-and-reentry` (§11–§16 — orbital mechanics, the ascent Δv budget, aerodynamic loads and structures, guidance and control, reentry physics, and failure physics),\n> `endeavour-fusion-physics-confinement-and-engineering` (§23–§25 — fusion physics and the Lawson criterion, magnetic and inertial confinement, and why fusion is hard to engineer),\n> `endeavour-satellites-flight-software-and-instruments` (§26–§28 — satellite design, types and orbits, flight software and FDIR, scientific instrumentation, and planetary protection),\n> `endeavour-the-martian-environment-and-in-situ-resources` (§29–§30 — the Martian environment as engineering parameters, and Mars resources and ISRU),\n> `endeavour-mars-mission-design-and-settlement` (§31–§32 — Mars launch windows, EDL, communications and surface power, and settlement),\n> `endeavour-terraforming-warming-and-the-magnetic-field-problem` (§33–§35 — terraforming theory and the habitability thresholds, atmospheric thickening and warming, and the magnetic field problem),\n> `endeavour-ecopoiesis-oxygen-timelines-and-ethics` (§36–§38 — ecopoiesis and the oxygen problem, timelines and paraterraforming, and ethics and the Venus comparison),\n> `endeavour-reference` (§39–§40 — the glossary spanning all six parts, and the further reading),\n>\n> Section numbers are **shared across the whole set**: a reference written as §N → `skill` points\n> into that sibling skill. The physics here is durable; specific mission figures, demonstrated\n> hardware performance and agency dose limits are as of the source and do drift.\n\nThree constraints generate every mission design, and everything below is downstream of them.\n**Mass is the currency, and everything converts to it** — power converts to mass (arrays,\nradioisotopes, radiators), data rate converts to mass (antenna, power), reliability converts to mass\n(redundancy), crew time converts to mass (consumables); you are always spending the same budget.\n**Distance imposes latency and darkness** — light-time makes teleoperation impossible beyond the\nMoon, forcing autonomy, and inverse-square makes both sunlight and signal scarce. And **for crewed\ndeep space the binding constraint is not propulsion but human physiology** — radiation dose and\nmicrogravity deconditioning bound mission duration more tightly than Δv does.\n\n---\n\n## §17 Mission architecture and the design cascade\n\nThe design cascade flows downward while mass flows upward, and the loop closes only by iteration:\n\n    science\u002Fmission objectives → measurement requirements → instrument selection\n      → pointing, power, data volume, thermal requirements → bus sizing\n      → mass and volume → launch vehicle and trajectory → constrains everything above\n\n> **THE CHARACTERISTIC MISTAKE IS TREATING THIS AS A WATERFALL.** It converges only if you carry\n> margins and re-run the loop when any element grows. A cascade run once, forward, with no reserve\n> produces a design that cannot absorb the first instrument that gains a kilogram.\n\n### The architecture trades\n\n| Trade | Poles |\n|---|---|\n| Flyby \u002F orbiter \u002F lander \u002F rover \u002F sample return | Cost and risk rise steeply; so does science return per target |\n| Solar vs. radioisotope | Decided largely by heliocentric distance and duty cycle |\n| Chemical vs. electric propulsion | Time versus propellant mass |\n| Direct vs. gravity assist | Δv versus flight time and window rigidity |\n| Store-and-forward vs. direct-to-Earth | Relay orbiters transform surface data return |\n\n### Windows, porkchops and assists\n\n**Launch windows** are set by planetary geometry. The Mars synodic period is ≈ 25.6 months — miss\nthe window and you wait over two years, which is the single hardest scheduling constraint in\nplanetary exploration; the Mars-specific consequences for crewed transfers are at §31 →\n`endeavour-mars-mission-design-and-settlement`.\n\n**Porkchop plots** — contours of C₃ (launch energy) and arrival v_∞ over departure and arrival\ndates — are the working tool of mission design.\n\n**Gravity assists** buy Δv at the cost of rigidity and flight time. Cassini's VVEJGA\n(Venus-Venus-Earth-Jupiter) took ~7 years to Saturn; direct would have needed a launch vehicle that\ndid not exist. **Assists do not just save propellant — they enable missions outright.** The\nunderlying two-body relations, the Oberth effect and plane-change costs are at §11 →\n`endeavour-orbits-ascent-structures-and-reentry`.\n\n## §18 Spacecraft power and thermal control\n\nA spacecraft is a **bus** (the supporting infrastructure — power, thermal, attitude control,\npropulsion, communications, command and data handling, structure) plus a **payload** (the instrument\nor communication package the mission exists for); the split itself, and the orbit regimes it gets\ndesigned into, are at §26 → `endeavour-satellites-flight-software-and-instruments`. This section\ncovers the first two subsystems.\n\n### Power\n\n**Solar flux scales as 1\u002Fr², and this single fact partitions the solar system.** At Mars (1.52 AU),\n590 W\u002Fm² — 43% of Earth. At Jupiter (5.20 AU), 50 W\u002Fm². Solar becomes impractical roughly beyond\nJupiter; Juno flies enormous arrays and is the outer limit. Beyond that, radioisotope power is not a\npreference, it is the only option.\n\n- **RTGs.** ²³⁸Pu, 87.7-year half-life, thermoelectric conversion at only **~6–7% efficiency**.\n  MMRTG ≈ **110 W electrical at BOL** from ~2,000 W thermal, decaying ~1.6%\u002Fyr. The binding\n  constraint is **plutonium supply, not engineering**. The waste heat is a feature — RTG thermal\n  output keeps spacecraft warm in the outer solar system.\n- **Batteries.** Li-ion at ~100–250 Wh\u002Fkg, sized to eclipse duration and peak load, with\n  depth-of-discharge traded against cycle life. A LEO spacecraft sees **~16 eclipses\u002Fday — about\n  90,000 cycles over 15 years**, which forces shallow DoD.\n- **Fission.** Kilopower\u002FKRUSTY demonstrated the 1–10 kW class, for surface power where solar duty\n  cycle fails: **a lunar night is 14 Earth days, and no practical battery bridges it.**\n\n### Thermal\n\nIn vacuum there is no convection. Heat moves by conduction and radiation only, and **radiation is\nthe only path off the vehicle**:\n\n    Q_rad = εσA(T⁴ − T_sink⁴)\n\n> **THE T⁴ IS BRUTAL.** A radiator at 300 K rejects ~460 W\u002Fm²; at 200 K, only ~91 W\u002Fm². Rejecting\n> heat from a cold instrument therefore costs area out of all proportion to the wattage, which is\n> why cryogenic payloads are a structural and geometric problem, not a plumbing one.\n\nThe **α\u002Fε ratio** — solar absorptivity over infrared emissivity — is the primary design knob, which\nis why thermal control is largely a **coatings** problem. **MLI blankets** (10–30 layers of\naluminized Mylar, effective emissivity ~0.01–0.03) are the single most effective thermal component\non most spacecraft.\n\nThe extremes are what break designs. JWST needs its instruments below ~40 K, achieved with a\ntennis-court-sized sunshield giving ~300 K of gradient across five layers. Parker Solar Probe\nsurvives ~1,400 °C on a carbon-composite shield while the bus stays near room temperature. The lunar\nsurface swings ~120 °C to −170 °C, and permanently shadowed craters sit near 25–40 K — colder than\nPluto's surface.\n\n## §19 Communications, navigation, and autonomy\n\n### The link budget\n\n    P_r = P_t + G_t + G_r − L_fs − L_other\n\nPath loss scales as d², so **data rate falls as 1\u002Fd²**. Mars at opposition versus conjunction varies\nby ~7× in distance — about 17 dB. **Coding buys enormous margin:** turbo and LDPC codes operate\nwithin ~1 dB of the Shannon limit, against the ~9 dB gap of uncoded BPSK — an order of magnitude in\neffective data rate for free, and the reason deep space missions return anything at all.\n\n> **THE NUMBERS THAT SHOW THE PROBLEM.** Voyager 1 at ~24 billion km returns ~160 bit\u002Fs on a 3.7 m\n> dish with 23 W. New Horizons at Pluto returned ~1–2 kbit\u002Fs and took **16 months** to downlink the\n> encounter data. Data volume, not instrument capability, is frequently the limiting factor for\n> outer-planet science. And the Deep Space Network (Goldstone, Madrid, Canberra — 120° apart for\n> continuous coverage) is **oversubscribed**, a real and under-appreciated constraint on mission\n> planning.\n\n**Light-time**, one-way: Moon 1.3 s (teleoperation marginal); Mars 3–22 min (teleoperation\nimpossible); Jupiter 33–53 min; Voyager 1 ~23 hours. Round-trip to Mars exceeds 40 minutes at\nconjunction. This is the single reason surface robots must be autonomous and why EDL must be\nentirely self-contained — **the spacecraft has landed or crashed before Earth knows it entered.**\n\n**Relay architecture.** Mars surface missions overwhelmingly return data via orbiters rather than\ndirect-to-Earth, because an orbiter passes overhead at ~400 km instead of 200 million, and the 1\u002Fd²\nadvantage is astronomical. The Mars relay fleet and the conjunction blackout are at §31 →\n`endeavour-mars-mission-design-and-settlement`.\n\n### Navigation\n\nThree complementary measurement types, plus one optical. **Doppler** gives line-of-sight velocity,\nprecise to ~0.1 mm\u002Fs. **Ranging** gives round-trip time — metres at planetary distance. **Delta-DOR**\nhas two stations observe the spacecraft and a quasar alternately, and differencing removes common\nerrors to give plane-of-sky position to **nanoradians**. **Optical navigation** — imaging the target\nagainst background stars — is essential for approach and for small bodies where the ephemeris is\npoor.\n\n### Autonomy\n\nAutonomy is not a nicety at distance; **it is forced by light-time.** **Safe mode** — power-positive,\nthermally stable, Earth-pointed, awaiting instructions — is entered by every deep space mission, and\nthe design question is whether it can survive there indefinitely. **Command loss timers** reconfigure\nafter N days without a command, which has saved missions whose primary receivers failed. And **fault\nprotection that misfires is itself a hazard**: a spurious safe-mode entry during a critical event can\nlose the mission. The detect\u002Fisolate\u002Frecover machinery that implements all of this, and the rules for\nnot recovering into the fault, are at §27 → `endeavour-satellites-flight-software-and-instruments`.\n\n## §20 Attitude control, in-space propulsion, and entry, descent and landing\n\n**Sensing:** star trackers (arcsecond-class, best), sun sensors, horizon sensors, magnetometers (LEO\nonly), gyros.\n\n**Actuation:** reaction wheels (precise, but they **saturate and must be desaturated**, and wheel\nfailure has crippled missions — **Kepler and Hayabusa both lost wheels**), control moment gyros\n(higher torque, used on ISS), thrusters (fast, consume propellant), magnetorquers (LEO only), spin\nstabilization (simple and robust, at the cost of pointing flexibility).\n\n| Type | Isp (s) | Use |\n|---|---|---|\n| Cold gas | 50–70 | Simple, small ΔV, contamination-free |\n| Monopropellant (hydrazine) | 220–235 | The RCS workhorse |\n| Bipropellant (MMH\u002FNTO) | 300–330 | Orbit insertion, hypergolic and storable |\n| Hall thruster | 1,500–2,500 | Station-keeping and orbit raising, now standard |\n| Gridded ion | 3,000–4,000 | Dawn visited two main-belt bodies — impossible chemically |\n| Solar sail | ∞ | No propellant; tiny thrust |\n\n**The electric propulsion trade, stated properly.** 10× the Isp means ~1\u002F10 the propellant for the\nsame Δv — but thrust is millinewtons, so burns last months and the power system must be sized to\nfeed it. **The mass moves from the propellant tank to the solar arrays.** It wins when the mission\nhas time and the Δv is large. (Isp, the mass ratio and why propellant mass is exponential in Δv are\nat §7 → `endeavour-rocket-equation-nozzles-engines-and-propellants`.)\n\n**Station-keeping budgets.** GEO needs ~50 m\u002Fs\u002Fyr, with north-south dominant. LEO needs drag makeup.\nHalo orbits need small but continual maintenance because they are unstable.\n\n### EDL — the Martian squeeze\n\nMars EDL is the canonical hard case, and the reason is a genuine physical squeeze: **the atmosphere\nis ~1% of Earth's — thick enough to demand a heat shield, too thin to slow you to safe landing speed\nwith parachutes alone.** The sequence, roughly seven minutes:\n\n    entry interface (~125 km, ~5.5–7.5 km\u002Fs) → peak heating (~100 s), peak deceleration (~8–15 g)\n      → supersonic parachute deploy (Mach 1.5–2.2, ~10 km) → heat shield jettison\n      → radar\u002FTRN acquisition → backshell separation → powered descent → touchdown\n\nEverything is autonomous. The heating physics behind the blunt aeroshell — compression rather than\nfriction, the v³ scaling of stagnation-point flux, and the entry corridor — is at §15 →\n`endeavour-orbits-ascent-structures-and-reentry`.\n\n**Landing methods and their regimes:**\n\n- **Airbags** (Pathfinder, MER) — mass-efficient, but cap landed mass around a few hundred kg.\n- **Legs** (Viking, Phoenix, InSight) — the engine plume excavates regolith and can contaminate\n  samples.\n- **Sky crane** (MSL, Perseverance) — the correct answer for ~1-tonne rovers: it keeps the engines\n  away from the surface and puts the wheels down directly.\n\n**The landed-mass ceiling.** Mars EDL has historically capped landed mass near ~1 tonne, because\nparachute area scales badly and supersonic retropropulsion was unproven. Scaling past it requires\neither much larger decelerators or supersonic retropropulsion.\n\n## §21 Human physiology, life support, and ISRU\n\n> **A MARS MISSION EXCEEDS NASA'S RADIATION DOSE LIMIT.** NASA's current career limit is **600 mSv**\n> effective dose. Estimates based on two 180-day transits plus ~500 days on the surface put the dose\n> **near 1,000 mSv — above the limit.** This is not a margin problem to be engineered away at the\n> edges; it is the mission, stated as a number.\n\nTwo sources, with opposite characters. **GCR** is continuous, high-energy heavy ions, hard to shield\nbecause they produce secondary particle showers — the dominant **chronic** risk. **SPE** is sporadic,\nproton-dominated and potentially **acute** — the reason a storm shelter is required. And a perverse\ncoupling: **solar maximum brings more SPE risk but suppresses GCR.** Solar minimum is\nsafer for acute events and worse for chronic dose. Surface dose measurements and regolith shielding\nare at §29 → `endeavour-the-martian-environment-and-in-situ-resources`.\n\n**Microgravity effects.** Bone loss ~1–1.5% per month in weight-bearing bone, not fully recovered\npost-flight. Muscle atrophy, cardiovascular fluid shift, orthostatic intolerance.\n\n**SANS (Spaceflight Associated Neuro-Ocular Syndrome)** is the constraint people underestimate —\noptic disc oedema, posterior globe flattening, choroidal folds, hyperopic shifts up to 1.5\ndioptres, affecting **roughly 70% of astronauts on missions over six months**, with no terrestrial\nequivalent. **The underlying aetiology is not understood.** SANS is why \"we've done a year on ISS, so\nMars is fine\" does not follow — a round-trip Mars mission is 2–2.5 years, well beyond any flown\nexperience.\n\n### ECLSS and closure\n\nFunctions: atmosphere pressure and composition, CO₂ removal, O₂ generation, water recovery, waste\nmanagement, humidity, fire detection, trace contaminant control.\n\nOn ISS: O₂ by water electrolysis; CO₂ removal by molecular sieve; a **Sabatier reactor (CO₂ + 4H₂ →\nCH₄ + 2H₂O) recovering ~50% of the oxygen loop**; water recovery up to **~93%** from urine, sweat\nand condensate.\n\n**The gap between 93% and 98% is where the engineering difficulty lives.** At 5 kg\u002Fperson\u002Fday of\nconsumables, a 1,000-day Mars mission for four people needs **20 tonnes open-loop**. Closure ratio is\nthe single biggest lever on crewed mission mass; what a permanent settlement needs beyond these\nfigures is at §32 → `endeavour-mars-mission-design-and-settlement`.\n\n### ISRU — MOXIE proved the principle\n\nMOXIE on Perseverance was the first demonstration of ISRU on another planet: a **15 kg** instrument\nperforming solid-oxide electrolysis of atmospheric CO₂ at **800 °C**, producing **12 g of oxygen per\nhour at ≥98% purity**.\n\n**The energy cost is the real constraint on scaling: ~30–70 kWh per kilogram of oxygen.** A Mars\nascent vehicle needs tens of tonnes of oxygen; at even 15 kWh\u002Fkg, 30 tonnes is **~450 MWh** — which\nis a power plant, not an instrument, and is why surface fission keeps appearing in Mars\narchitectures. Both figures are the source's, and **15 kWh\u002Fkg is below the 30–70 kWh\u002Fkg range it\ngives one sentence earlier** — not at its floor — so **~450 MWh understates the plant**: the same\n30 tonnes at the stated range is **900–2,100 MWh**. Reworking it only strengthens the section's\npoint, because the power plant gets bigger. The full mine-to-methalox chain is at §30 →\n`endeavour-the-martian-environment-and-in-situ-resources`.\n\n**Why ISRU matters at all:** the rocket equation means propellant for the return trip, launched from\nEarth, costs enormously more than its own mass at departure. **Making it at the destination breaks\nthe exponential.**\n\n## §22 Reliability, margins, and the failures that teach them\n\nStandard margins carried through design phases:\n\n| Quantity | Margin |\n|---|---|\n| Mass | 30% at concept → 5–10% at CDR |\n| Power | 20–30% early |\n| Data rate \u002F volume | ~25% |\n| Δv | 5–10%, plus explicit statistical margin |\n\n**The mass margin exists because mass always grows, and a programme that spends its margin early has\nno options later.**\n\n**Redundancy** comes in three forms: **block** (a whole second string), **functional** (a different\nsubsystem achieves the same end), and **cross-strapping**. Watch **common-cause failure** — two\nidentical units with the same design flaw fail identically, so two of them is not two chances.\n**Deployments** (solar arrays, antennas, booms) are classic single-point failures: Galileo's\nhigh-gain antenna never fully opened, forcing the entire mission onto the low-gain link.\n\nThe recurring lessons, each named with its actual cause:\n\n- **Mars Climate Orbiter (1999)** — pound-force-seconds versus newton-seconds in a ground software\n  interface. A units error.\n- **Mars Polar Lander (1999)** — leg-deployment vibration read as touchdown; engines cut at\n  altitude. A software response to an unanticipated sensor transient.\n- **Ariane 501** — reused inertial software on a trajectory it was not designed for.\n- **Beagle 2** — incomplete solar panel deployment blocked the antenna; no telemetry, so no\n  diagnosis for a decade.\n\n> **TEST AS YOU FLY.** Most of the above are failures of that principle. The organizational pattern\n> by which a known anomaly becomes an accepted one — normalization of deviance, with Challenger and\n> Columbia as its canonical cases — is at §16 → `endeavour-orbits-ascent-structures-and-reentry`.\n","# Space Mission Architecture and Spacecraft Subsystems\n\n> **Part 5 of 12** of the *Military Science, Rockets, Space, Fusion, and Mars* reference (plugin\n> `military-space-rockets-and-fusion`), covering §17–§22 — mission architecture and the design cascade, power and thermal, communications and navigation, attitude control and EDL, human physiology and ISRU, and reliability. Sibling skills:\n> `endeavour-military-theory-levels-of-war-and-deterrence` (§1–§3 — what military science is, the theoretical canon, the levels of war, and deterrence and nuclear strategy),\n> `endeavour-logistics-doctrine-modern-conflict-and-the-law` (§4–§6 — force structure, logistics, doctrine, intelligence, procurement, modern conflict, and the law of armed conflict),\n> `endeavour-rocket-equation-nozzles-engines-and-propellants` (§7–§10 — the rocket equation and staging, nozzle thermodynamics and the combustion chamber, turbomachinery and cooling, and propellants),\n> `endeavour-orbits-ascent-structures-and-reentry` (§11–§16 — orbital mechanics, the ascent Δv budget, aerodynamic loads and structures, guidance and control, reentry physics, and failure physics),\n> `endeavour-fusion-physics-confinement-and-engineering` (§23–§25 — fusion physics and the Lawson criterion, magnetic and inertial confinement, and why fusion is hard to engineer),\n> `endeavour-satellites-flight-software-and-instruments` (§26–§28 — satellite design, types and orbits, flight software and FDIR, scientific instrumentation, and planetary protection),\n> `endeavour-the-martian-environment-and-in-situ-resources` (§29–§30 — the Martian environment as engineering parameters, and Mars resources and ISRU),\n> `endeavour-mars-mission-design-and-settlement` (§31–§32 — Mars launch windows, EDL, communications and surface power, and settlement),\n> `endeavour-terraforming-warming-and-the-magnetic-field-problem` (§33–§35 — terraforming theory and the habitability thresholds, atmospheric thickening and warming, and the magnetic field problem),\n> `endeavour-ecopoiesis-oxygen-timelines-and-ethics` (§36–§38 — ecopoiesis and the oxygen problem, timelines and paraterraforming, and ethics and the Venus comparison),\n> `endeavour-reference` (§39–§40 — the glossary spanning all six parts, and the further reading),\n>\n> Section numbers are **shared across the whole set**: a reference written as §N → `skill` points\n> into that sibling skill. The physics here is durable; specific mission figures, demonstrated\n> hardware performance and agency dose limits are as of the source and do drift.\n\nThree constraints generate every mission design, and everything below is downstream of them.\n**Mass is the currency, and everything converts to it** — power converts to mass (arrays,\nradioisotopes, radiators), data rate converts to mass (antenna, power), reliability converts to mass\n(redundancy), crew time converts to mass (consumables); you are always spending the same budget.\n**Distance imposes latency and darkness** — light-time makes teleoperation impossible beyond the\nMoon, forcing autonomy, and inverse-square makes both sunlight and signal scarce. And **for crewed\ndeep space the binding constraint is not propulsion but human physiology** — radiation dose and\nmicrogravity deconditioning bound mission duration more tightly than Δv does.\n\n---\n\n## §17 Mission architecture and the design cascade\n\nThe design cascade flows downward while mass flows upward, and the loop closes only by iteration:\n\n    science\u002Fmission objectives → measurement requirements → instrument selection\n      → pointing, power, data volume, thermal requirements → bus sizing\n      → mass and volume → launch vehicle and trajectory → constrains everything above\n\n> **THE CHARACTERISTIC MISTAKE IS TREATING THIS AS A WATERFALL.** It converges only if you carry\n> margins and re-run the loop when any element grows. A cascade run once, forward, with no reserve\n> produces a design that cannot absorb the first instrument that gains a kilogram.\n\n### The architecture trades\n\n| Trade | Poles |\n|---|---|\n| Flyby \u002F orbiter \u002F lander \u002F rover \u002F sample return | Cost and risk rise steeply; so does science return per target |\n| Solar vs. radioisotope | Decided largely by heliocentric distance and duty cycle |\n| Chemical vs. electric propulsion | Time versus propellant mass |\n| Direct vs. gravity assist | Δv versus flight time and window rigidity |\n| Store-and-forward vs. direct-to-Earth | Relay orbiters transform surface data return |\n\n### Windows, porkchops and assists\n\n**Launch windows** are set by planetary geometry. The Mars synodic period is ≈ 25.6 months — miss\nthe window and you wait over two years, which is the single hardest scheduling constraint in\nplanetary exploration; the Mars-specific consequences for crewed transfers are at §31 →\n`endeavour-mars-mission-design-and-settlement`.\n\n**Porkchop plots** — contours of C₃ (launch energy) and arrival v_∞ over departure and arrival\ndates — are the working tool of mission design.\n\n**Gravity assists** buy Δv at the cost of rigidity and flight time. Cassini's VVEJGA\n(Venus-Venus-Earth-Jupiter) took ~7 years to Saturn; direct would have needed a launch vehicle that\ndid not exist. **Assists do not just save propellant — they enable missions outright.** The\nunderlying two-body relations, the Oberth effect and plane-change costs are at §11 →\n`endeavour-orbits-ascent-structures-and-reentry`.\n\n## §18 Spacecraft power and thermal control\n\nA spacecraft is a **bus** (the supporting infrastructure — power, thermal, attitude control,\npropulsion, communications, command and data handling, structure) plus a **payload** (the instrument\nor communication package the mission exists for); the split itself, and the orbit regimes it gets\ndesigned into, are at §26 → `endeavour-satellites-flight-software-and-instruments`. This section\ncovers the first two subsystems.\n\n### Power\n\n**Solar flux scales as 1\u002Fr², and this single fact partitions the solar system.** At Mars (1.52 AU),\n590 W\u002Fm² — 43% of Earth. At Jupiter (5.20 AU), 50 W\u002Fm². Solar becomes impractical roughly beyond\nJupiter; Juno flies enormous arrays and is the outer limit. Beyond that, radioisotope power is not a\npreference, it is the only option.\n\n- **RTGs.** ²³⁸Pu, 87.7-year half-life, thermoelectric conversion at only **~6–7% efficiency**.\n  MMRTG ≈ **110 W electrical at BOL** from ~2,000 W thermal, decaying ~1.6%\u002Fyr. The binding\n  constraint is **plutonium supply, not engineering**. The waste heat is a feature — RTG thermal\n  output keeps spacecraft warm in the outer solar system.\n- **Batteries.** Li-ion at ~100–250 Wh\u002Fkg, sized to eclipse duration and peak load, with\n  depth-of-discharge traded against cycle life. A LEO spacecraft sees **~16 eclipses\u002Fday — about\n  90,000 cycles over 15 years**, which forces shallow DoD.\n- **Fission.** Kilopower\u002FKRUSTY demonstrated the 1–10 kW class, for surface power where solar duty\n  cycle fails: **a lunar night is 14 Earth days, and no practical battery bridges it.**\n\n### Thermal\n\nIn vacuum there is no convection. Heat moves by conduction and radiation only, and **radiation is\nthe only path off the vehicle**:\n\n    Q_rad = εσA(T⁴ − T_sink⁴)\n\n> **THE T⁴ IS BRUTAL.** A radiator at 300 K rejects ~460 W\u002Fm²; at 200 K, only ~91 W\u002Fm². Rejecting\n> heat from a cold instrument therefore costs area out of all proportion to the wattage, which is\n> why cryogenic payloads are a structural and geometric problem, not a plumbing one.\n\nThe **α\u002Fε ratio** — solar absorptivity over infrared emissivity — is the primary design knob, which\nis why thermal control is largely a **coatings** problem. **MLI blankets** (10–30 layers of\naluminized Mylar, effective emissivity ~0.01–0.03) are the single most effective thermal component\non most spacecraft.\n\nThe extremes are what break designs. JWST needs its instruments below ~40 K, achieved with a\ntennis-court-sized sunshield giving ~300 K of gradient across five layers. Parker Solar Probe\nsurvives ~1,400 °C on a carbon-composite shield while the bus stays near room temperature. The lunar\nsurface swings ~120 °C to −170 °C, and permanently shadowed craters sit near 25–40 K — colder than\nPluto's surface.\n\n## §19 Communications, navigation, and autonomy\n\n### The link budget\n\n    P_r = P_t + G_t + G_r − L_fs − L_other\n\nPath loss scales as d², so **data rate falls as 1\u002Fd²**. Mars at opposition versus conjunction varies\nby ~7× in distance — about 17 dB. **Coding buys enormous margin:** turbo and LDPC codes operate\nwithin ~1 dB of the Shannon limit, against the ~9 dB gap of uncoded BPSK — an order of magnitude in\neffective data rate for free, and the reason deep space missions return anything at all.\n\n> **THE NUMBERS THAT SHOW THE PROBLEM.** Voyager 1 at ~24 billion km returns ~160 bit\u002Fs on a 3.7 m\n> dish with 23 W. New Horizons at Pluto returned ~1–2 kbit\u002Fs and took **16 months** to downlink the\n> encounter data. Data volume, not instrument capability, is frequently the limiting factor for\n> outer-planet science. And the Deep Space Network (Goldstone, Madrid, Canberra — 120° apart for\n> continuous coverage) is **oversubscribed**, a real and under-appreciated constraint on mission\n> planning.\n\n**Light-time**, one-way: Moon 1.3 s (teleoperation marginal); Mars 3–22 min (teleoperation\nimpossible); Jupiter 33–53 min; Voyager 1 ~23 hours. Round-trip to Mars exceeds 40 minutes at\nconjunction. This is the single reason surface robots must be autonomous and why EDL must be\nentirely self-contained — **the spacecraft has landed or crashed before Earth knows it entered.**\n\n**Relay architecture.** Mars surface missions overwhelmingly return data via orbiters rather than\ndirect-to-Earth, because an orbiter passes overhead at ~400 km instead of 200 million, and the 1\u002Fd²\nadvantage is astronomical. The Mars relay fleet and the conjunction blackout are at §31 →\n`endeavour-mars-mission-design-and-settlement`.\n\n### Navigation\n\nThree complementary measurement types, plus one optical. **Doppler** gives line-of-sight velocity,\nprecise to ~0.1 mm\u002Fs. **Ranging** gives round-trip time — metres at planetary distance. **Delta-DOR**\nhas two stations observe the spacecraft and a quasar alternately, and differencing removes common\nerrors to give plane-of-sky position to **nanoradians**. **Optical navigation** — imaging the target\nagainst background stars — is essential for approach and for small bodies where the ephemeris is\npoor.\n\n### Autonomy\n\nAutonomy is not a nicety at distance; **it is forced by light-time.** **Safe mode** — power-positive,\nthermally stable, Earth-pointed, awaiting instructions — is entered by every deep space mission, and\nthe design question is whether it can survive there indefinitely. **Command loss timers** reconfigure\nafter N days without a command, which has saved missions whose primary receivers failed. And **fault\nprotection that misfires is itself a hazard**: a spurious safe-mode entry during a critical event can\nlose the mission. The detect\u002Fisolate\u002Frecover machinery that implements all of this, and the rules for\nnot recovering into the fault, are at §27 → `endeavour-satellites-flight-software-and-instruments`.\n\n## §20 Attitude control, in-space propulsion, and entry, descent and landing\n\n**Sensing:** star trackers (arcsecond-class, best), sun sensors, horizon sensors, magnetometers (LEO\nonly), gyros.\n\n**Actuation:** reaction wheels (precise, but they **saturate and must be desaturated**, and wheel\nfailure has crippled missions — **Kepler and Hayabusa both lost wheels**), control moment gyros\n(higher torque, used on ISS), thrusters (fast, consume propellant), magnetorquers (LEO only), spin\nstabilization (simple and robust, at the cost of pointing flexibility).\n\n| Type | Isp (s) | Use |\n|---|---|---|\n| Cold gas | 50–70 | Simple, small ΔV, contamination-free |\n| Monopropellant (hydrazine) | 220–235 | The RCS workhorse |\n| Bipropellant (MMH\u002FNTO) | 300–330 | Orbit insertion, hypergolic and storable |\n| Hall thruster | 1,500–2,500 | Station-keeping and orbit raising, now standard |\n| Gridded ion | 3,000–4,000 | Dawn visited two main-belt bodies — impossible chemically |\n| Solar sail | ∞ | No propellant; tiny thrust |\n\n**The electric propulsion trade, stated properly.** 10× the Isp means ~1\u002F10 the propellant for the\nsame Δv — but thrust is millinewtons, so burns last months and the power system must be sized to\nfeed it. **The mass moves from the propellant tank to the solar arrays.** It wins when the mission\nhas time and the Δv is large. (Isp, the mass ratio and why propellant mass is exponential in Δv are\nat §7 → `endeavour-rocket-equation-nozzles-engines-and-propellants`.)\n\n**Station-keeping budgets.** GEO needs ~50 m\u002Fs\u002Fyr, with north-south dominant. LEO needs drag makeup.\nHalo orbits need small but continual maintenance because they are unstable.\n\n### EDL — the Martian squeeze\n\nMars EDL is the canonical hard case, and the reason is a genuine physical squeeze: **the atmosphere\nis ~1% of Earth's — thick enough to demand a heat shield, too thin to slow you to safe landing speed\nwith parachutes alone.** The sequence, roughly seven minutes:\n\n    entry interface (~125 km, ~5.5–7.5 km\u002Fs) → peak heating (~100 s), peak deceleration (~8–15 g)\n      → supersonic parachute deploy (Mach 1.5–2.2, ~10 km) → heat shield jettison\n      → radar\u002FTRN acquisition → backshell separation → powered descent → touchdown\n\nEverything is autonomous. The heating physics behind the blunt aeroshell — compression rather than\nfriction, the v³ scaling of stagnation-point flux, and the entry corridor — is at §15 →\n`endeavour-orbits-ascent-structures-and-reentry`.\n\n**Landing methods and their regimes:**\n\n- **Airbags** (Pathfinder, MER) — mass-efficient, but cap landed mass around a few hundred kg.\n- **Legs** (Viking, Phoenix, InSight) — the engine plume excavates regolith and can contaminate\n  samples.\n- **Sky crane** (MSL, Perseverance) — the correct answer for ~1-tonne rovers: it keeps the engines\n  away from the surface and puts the wheels down directly.\n\n**The landed-mass ceiling.** Mars EDL has historically capped landed mass near ~1 tonne, because\nparachute area scales badly and supersonic retropropulsion was unproven. Scaling past it requires\neither much larger decelerators or supersonic retropropulsion.\n\n## §21 Human physiology, life support, and ISRU\n\n> **A MARS MISSION EXCEEDS NASA'S RADIATION DOSE LIMIT.** NASA's current career limit is **600 mSv**\n> effective dose. Estimates based on two 180-day transits plus ~500 days on the surface put the dose\n> **near 1,000 mSv — above the limit.** This is not a margin problem to be engineered away at the\n> edges; it is the mission, stated as a number.\n\nTwo sources, with opposite characters. **GCR** is continuous, high-energy heavy ions, hard to shield\nbecause they produce secondary particle showers — the dominant **chronic** risk. **SPE** is sporadic,\nproton-dominated and potentially **acute** — the reason a storm shelter is required. And a perverse\ncoupling: **solar maximum brings more SPE risk but suppresses GCR.** Solar minimum is\nsafer for acute events and worse for chronic dose. Surface dose measurements and regolith shielding\nare at §29 → `endeavour-the-martian-environment-and-in-situ-resources`.\n\n**Microgravity effects.** Bone loss ~1–1.5% per month in weight-bearing bone, not fully recovered\npost-flight. Muscle atrophy, cardiovascular fluid shift, orthostatic intolerance.\n\n**SANS (Spaceflight Associated Neuro-Ocular Syndrome)** is the constraint people underestimate —\noptic disc oedema, posterior globe flattening, choroidal folds, hyperopic shifts up to 1.5\ndioptres, affecting **roughly 70% of astronauts on missions over six months**, with no terrestrial\nequivalent. **The underlying aetiology is not understood.** SANS is why \"we've done a year on ISS, so\nMars is fine\" does not follow — a round-trip Mars mission is 2–2.5 years, well beyond any flown\nexperience.\n\n### ECLSS and closure\n\nFunctions: atmosphere pressure and composition, CO₂ removal, O₂ generation, water recovery, waste\nmanagement, humidity, fire detection, trace contaminant control.\n\nOn ISS: O₂ by water electrolysis; CO₂ removal by molecular sieve; a **Sabatier reactor (CO₂ + 4H₂ →\nCH₄ + 2H₂O) recovering ~50% of the oxygen loop**; water recovery up to **~93%** from urine, sweat\nand condensate.\n\n**The gap between 93% and 98% is where the engineering difficulty lives.** At 5 kg\u002Fperson\u002Fday of\nconsumables, a 1,000-day Mars mission for four people needs **20 tonnes open-loop**. Closure ratio is\nthe single biggest lever on crewed mission mass; what a permanent settlement needs beyond these\nfigures is at §32 → `endeavour-mars-mission-design-and-settlement`.\n\n### ISRU — MOXIE proved the principle\n\nMOXIE on Perseverance was the first demonstration of ISRU on another planet: a **15 kg** instrument\nperforming solid-oxide electrolysis of atmospheric CO₂ at **800 °C**, producing **12 g of oxygen per\nhour at ≥98% purity**.\n\n**The energy cost is the real constraint on scaling: ~30–70 kWh per kilogram of oxygen.** A Mars\nascent vehicle needs tens of tonnes of oxygen; at even 15 kWh\u002Fkg, 30 tonnes is **~450 MWh** — which\nis a power plant, not an instrument, and is why surface fission keeps appearing in Mars\narchitectures. Both figures are the source's, and **15 kWh\u002Fkg is below the 30–70 kWh\u002Fkg range it\ngives one sentence earlier** — not at its floor — so **~450 MWh understates the plant**: the same\n30 tonnes at the stated range is **900–2,100 MWh**. Reworking it only strengthens the section's\npoint, because the power plant gets bigger. The full mine-to-methalox chain is at §30 →\n`endeavour-the-martian-environment-and-in-situ-resources`.\n\n**Why ISRU matters at all:** the rocket equation means propellant for the return trip, launched from\nEarth, costs enormously more than its own mass at departure. **Making it at the destination breaks\nthe exponential.**\n\n## §22 Reliability, margins, and the failures that teach them\n\nStandard margins carried through design phases:\n\n| Quantity | Margin |\n|---|---|\n| Mass | 30% at concept → 5–10% at CDR |\n| Power | 20–30% early |\n| Data rate \u002F volume | ~25% |\n| Δv | 5–10%, plus explicit statistical margin |\n\n**The mass margin exists because mass always grows, and a programme that spends its margin early has\nno options later.**\n\n**Redundancy** comes in three forms: **block** (a whole second string), **functional** (a different\nsubsystem achieves the same end), and **cross-strapping**. Watch **common-cause failure** — two\nidentical units with the same design flaw fail identically, so two of them is not two chances.\n**Deployments** (solar arrays, antennas, booms) are classic single-point failures: Galileo's\nhigh-gain antenna never fully opened, forcing the entire mission onto the low-gain link.\n\nThe recurring lessons, each named with its actual cause:\n\n- **Mars Climate Orbiter (1999)** — pound-force-seconds versus newton-seconds in a ground software\n  interface. A units error.\n- **Mars Polar Lander (1999)** — leg-deployment vibration read as touchdown; engines cut at\n  altitude. A software response to an unanticipated sensor transient.\n- **Ariane 501** — reused inertial software on a trajectory it was not designed for.\n- **Beagle 2** — incomplete solar panel deployment blocked the antenna; no telemetry, so no\n  diagnosis for a decade.\n\n> **TEST AS YOU FLY.** Most of the above are failures of that principle. The organizational pattern\n> by which a known anomaly becomes an accepted one — normalization of deviance, with Challenger and\n> Columbia as its canonical cases — is at §16 → `endeavour-orbits-ascent-structures-and-reentry`.\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fmilitary-space-rockets-and-fusion\u002Fskills\u002Fendeavour-mission-architecture-and-spacecraft-subsystems",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-mission-architecture-and-spacecraft-subsystems",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill endeavour-mission-architecture-and-spacecraft-subsystems",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill endeavour-mission-architecture-and-spacecraft-subsystems","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fmilitary-space-rockets-and-fusion\u002Fskills\u002Fendeavour-mission-architecture-and-spacecraft-subsystems\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",[],[]]