Ooh boy this is not how Vesherti thought labor law was going to come up.
"Yes, it's definitely tricky," he agrees. "They use a combination of techniques — the simplest one is just making sure that there are a lot of people available to be on call. The average emergency coordination session is pretty slow and involves lots of breaks and opportunities to read, so that when there is a big emergency or someone doesn't want to do it for a while there are enough people there. Another technique is tying in other cities; they use lightning-based communication so that if all the people here are busy your call will actually go to the next nearest city. The next nearest city won't do quite as good a job because they're not as familiar with the area, but they'll still be able to help. The fallback system is actually worldwide — so something would need to take a lot of cities out simultaneously, or at least cut all our lightning-links, in order to prevent an emergency call from being answered. That's very unlikely, though. This city's emergency lightning-links are designed to keep working during the most serious storm we've had here in the past thousand years."
"A tangentially related part is just reducing the number of emergencies that need sudden attention, such as by requiring that buildings be built out of things that are harder to set on fire, or reducing the amount of coordination necessary in an emergency by spreading out emergency responders, having unique symbols for every building in the city so that you can easily talk about where things are, and so on. Those are things that can reduce the number of necessary emergency coordinators by doing more work ahead of time, when it's convenient."
"The other techniques involve a topic that I haven't really gone into detail yet, because we think you might lack the concept entirely. You shared a lot of vocabulary with us, but none of it was really related to the concept of a job. The idea is that you can trade value-objects for people's time and energy, not just for other objects — that part I expect you to be familiar with — but that you can also trade value-objects for getting someone to do something consistently. So anyone can do the training to become an emergency coordinator, and they can help in an emergency. But the people who do it every day and handle most of the calls, many of them promise to come in at predictable times unless they get hurt or sick themselves. In exchange for the imposition of having to stick to a schedule like that, they get more value objects," he explains.
"There are a few people who make sure the promised predictable schedules all line up correctly to ensure someone is always available. If one of the emergency coordinators needs to change their schedule for some reason, they give them a few days notice, and they arrange to cover the gap in the schedule. Doing something like that does require a certain amount of dependability and willpower — which is why it's also a respected role and worth more value objects. Someone who can't commit to that kind of scheduled-in-advance life would mostly choose to do something else instead."
"Of all the systems I've pointed out to you so far, I think this is the one we're least proud of. It's very common — many projects that need predictable coverage do the same thing — and we do think it's worth it on average, because of the way that it makes some things, like guaranteed emergency calls, possible. But many people find scheduled roles like that stressful, even if they can mostly make them work. As we've learned to build more capable machines, and gotten better at predicting things, we've been able to decrease the number of roles like that over time. But some things just need someone to be there in order to work, and there's nothing to be done about it yet. Maybe in the future we'll be able to figure out a better solution."