Bibliographic record
Abstract
Abstract Processes and procedures, concepts, requirements, and design specifications, and design and productions standards are necessary but not always sufficient for building a robust space system. These entities are only documentation and not knowledge. The preponderance of these entities are success‐centric and are created from within the system. That is, they generally do not provide enough emphasis on addressing what can go wrong and they are limited by the knowledge of the people developing the system. This paper is divided into three parts. The first part examines specific occurrences of space mission degradation, failure and recovery. These examples will illustrate the notion that anything can go wrong in a space mission, but a robust design and ingenious work‐arounds can often save the mission. The second part provides examples of recovery from failures. The third part provides an overview of six methodologies that are critical to building a robust system. These methodologies should be standard practices in any program, but can be overlooked or under‐worked when a program first encounters the prospect of missed milestones and insufficient funding.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.013 | 0.099 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.004 | 0.003 |
| Science and technology studies | 0.003 | 0.005 |
| Scholarly communication | 0.006 | 0.004 |
| Open science | 0.001 | 0.004 |
| Research integrity | 0.002 | 0.003 |
| Insufficient payload (model declined to judge) | 0.013 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".