Artemis IV splashed down in the Pacific twelve days ago. Routine recovery. The Navy fished the capsule out, the crew waved at cameras from the recovery ship, and the whole thing looked like a textbook mission. Except NASA's post-flight briefing to local emergency services was unusually specific: the crew would be held at a quarantine facility on Naval Base San Diego, and any 911 calls originating from the facility or from crew members' temporary housing should be "coordinated through the NASA liaison before dispatch." Your watch commander noted this, forwarded the email to the shift supervisors, and assumed it would never matter.
It matters now.
A woman calls 911 from base housing. Her husband is one of the Artemis IV crew members. She is calm but very precise: "My husband's skin has changed. It's hardening. It looks like rock and it's spreading. He can't fit through the bathroom door anymore and I need someone to come look at him." Your call-taker asks the standard EMD questions. Is he conscious? Yes. Is he breathing? Yes. Is he in pain? "He says it doesn't hurt. He says it feels like armor." Is he having an allergic reaction? "This is not an allergic reaction."
The call-taker has a decision to make. This presents as either SICK/UNKNOWN with a possible environmental exposure history, or a PSYCH/WELFARE call from a distressed spouse. The call-taker was not on shift when the NASA briefing came through. The email is sitting in a supervisor's inbox. The supervisor is on break.
Before the first call clears, a second comes in. This one is from base security. They're reporting a "thermal anomaly" in the crew quarters parking lot. A vehicle is on fire, but there's no accelerant, no impact, no visible ignition source. A male subject is standing next to the vehicle and appears to be the source of the heat. He is not on fire. He is, according to the security officer, "generating fire." The security officer would like to know what nature code this falls under. You would also like to know.
Then a third call. A neighbor in base housing reports that she saw a woman "disappear" on the sidewalk. Not walk away. Not go inside. She was there, and then she was not. The caller is sober, articulate, and insistent. "I know how this sounds. I'm telling you what I saw."
Your fourth call comes from the NASA liaison, who is now awake. He identifies himself, confirms the crew members' identities, and says the situation is "anticipated but accelerated." He asks you not to dispatch standard EMS and says a federal medical team is en route. He does not explain what "anticipated" means. He asks you to hold all units.
You now have four calls, three of which describe physically impossible events, one of which is a federal liaison telling you to stand down. Your call-taker who took the first call coded it as SICK/UNKNOWN. Your call-taker who took the second coded it as a vehicle fire. The third is sitting in CAD as a welfare check. None of these are right. None of these are wrong, either.
The supervisor comes back from break, reads the NASA email, looks at the CAD screen, and says "oh." She picks up the phone and calls the watch commander at home. He asks what's going on. She says "the astronauts are having a medical issue." He asks her to be more specific. She says "one of them appears to be made of rock." There is a long pause. He says he's coming in.
This is the exercise in a single question. The caller is presenting credible, consistent information about a physically implausible event. Without context, every EMD protocol in existence routes this toward behavioral health. The caller isn't confused, isn't incoherent, isn't escalating — she's describing something that doesn't fit any medical category your system has. And your call-taker, following protocol correctly, is going to make a classification that determines who shows up and how fast.
Now add the NASA briefing. If the call-taker knows that Artemis IV crew may present with unusual symptoms from a radiation exposure event, this is a SICK/UNKNOWN with environmental exposure history. Different response profile, different urgency, different resources. The classification changes everything downstream — and the only variable is whether a single email made it from a supervisor's inbox to the person answering the phone.
This happens in the real world constantly, minus the comic book framing. A hazmat exposure two counties over produces delayed symptoms in a transient patient who shows up at your ER. A military training exercise generates civilian calls about explosions. An industrial release creates symptoms that look psychiatric until someone connects them to the chemical. The briefing is the bridge between "this person sounds delusional" and "this person is describing a known exposure."
This is a jurisdiction and duty-to-act problem. A federal liaison can request coordination. They cannot order a municipal or county agency to withhold emergency response to active 911 calls. Your legal obligation is to the callers, not to the liaison's preference for operational control.
The practical question is whether your responding units can actually help. If the patient's skin is turning to rock, what is your paramedic going to do? Start an IV in granite? The honest answer might be that standard EMS has nothing to offer here, and staging until the federal team arrives is the operationally sound decision — not because the liaison told you to, but because you don't have the resources to treat what you're being described.
But you still have a duty to assess. You can stage units at the perimeter, you can have them standing by, but you don't cancel the response entirely on a federal request without your own command authority signing off. If the watch commander agrees to hold, that's a defensible decision. If the call-taker just stops dispatching because someone from NASA said to, that's a liability.
This is the multi-entry problem that shows up in every complex event. A mass casualty incident generates dozens of CAD entries with different nature codes — medical, fire, traffic, welfare check — before someone connects them into a single operational picture. The connection usually happens when a supervisor or experienced dispatcher recognizes the geographic cluster and says "these are all the same thing."
The tool is a master incident number. Link all related CAD entries under one umbrella event so every dispatcher and every responding unit sees the same picture. The individual nature codes can stay — they're useful for resource typing — but the master incident tells the story: these aren't five separate calls, they're five manifestations of one event.
The harder problem is what you name the master incident. "Space Weather Medical Contingency" is what the NASA liaison offered, and it's technically accurate, but it doesn't help your dispatchers or your units understand what they're walking into. Something functional works better: "Artemis IV Crew Medical — Multiple Patients, Federal Coordination." It's not poetic, but it tells every person who touches the CAD entry what this is and who's involved.
This comes up more often than you'd think — not with astronauts, but with any incident involving federal facilities, military installations, or classified operations. A call originates from a military base, your agency dispatches, your CAD creates the record. Then someone from the installation asks you to restrict, reclassify, or redact those records. Whose data is it?
Your CAD records are your agency's records. They were created by your personnel in response to calls for service in your jurisdiction. A federal liaison can request that you flag them, and you might cooperate as a professional courtesy, but they cannot compel you to restrict access to your own operational records without a legal instrument — a court order, a formal classification directive, something with actual authority behind it.
The practical advice is to flag the records as requested, notify your agency's legal counsel that the request was made, and document everything. If a FOIA request comes in tomorrow from a journalist who heard something weird happened on the naval base, your records custodian needs to know what's flagged and why. The answer might still be "release it" — but they need the full picture.
This is a fictional scenario. No Artemis crew members have been exposed to cosmic rays, developed anomalous physical conditions, or required extrication from base housing due to increased mass. The scenario is inspired by the Fantastic Four, Marvel's first superhero team, who gained their powers from cosmic ray exposure during a space mission in 1961 and have been causing jurisdictional headaches ever since. The dispatch problems in this exercise — information flow failures, call classification without precedent, federal coordination tensions, duty to act versus request to hold, and records management under pressure — are real. The astronaut made of rock is not. We checked.