Topics — What a work is about. Nucleation holds whatever reading the owner files here, whether or not an Anthology of the SOTA topic could also hold it; instruction for ML practice belongs to the anthology (ADR-048). The words are seeded from the clusters the reading-time triage of 2026-09-25 found, and grow by decision.
Operations research — optimization of real systems — routing, scheduling, facility location, combinatorial algorithms.
3 of 191 CASE documents. Back to the full index.
| # | Title | Summary | Status |
|---|---|---|---|
| CASE-127 v2 | United 173 and Crew Resource Management: a crew whose concern about the fuel did not reach the captain as a demand to act, and the training that followed, which asked for participative captains and assertive crews | The owner’s case at U25 of the exchange of 2026-10-22: “the history underlying the evolution of Crew Resource Management”. A cockpit had the information and lacked the organization to make it govern. The reform changed the organization of authority, not its holder. Not shown: that CRM caused the later fall in accidents, which the case does not test. | Active |
| CASE-135 v2 | The Brookhollow Apartments fire, Wichita, 2023: a mayday after a stair roof collapses on two companies opens a second emergency inside a search for a trapped resident, and an independent review finds an unorganized rescue effort without finding that it changed the outcome | The owner’s class of case, a fireground mayday inside an escalating response organized under the National Incident Management System (U23 of the exchange of 2026-10-22); A23 and A24’s instance. It is the record’s first real multi-regime emergency, beside the fictional Northstar (CASE-023). It shows two regimes, rescue of a member and the original mission, needing to be held at once, and a review that recommends change. Not shown: that the department’s safety culture changed, or what the review’s recommendations were, since the report was not read. | Active |
| CASE-138 v2 | Challenger to Columbia: NASA corrected its launch decisions and its safety organization after 1986, and the Columbia board found in 2003 that related organizational failure mechanisms had recurred, while its lessons-learned system was little used in between | The owner’s case at U25 of the exchange of 2026-10-22: NASA’s mechanisms for documenting and learning from mistakes, with Challenger as the classic example. The record already reads the Columbia board’s account (THEORY-140, from LIT-734). This case files the history around it: a warning whose standing changed as it moved, a correction made in the rules, and a capacity not maintained. Not shown: why the correction decayed, which THEORY-140 explains and this case only displays. | Active |