Challenge 1: Explain the Structural Limit — Possible Solution
====================================================================

Compose's inability to reschedule work after a host fails isn't
missing a feature — it's missing an entire CONCEPT that would need to
be built from scratch. Compose's whole design is built around a
single docker-compose.yml describing services that run on ONE machine,
the machine docker compose up is invoked on. There is no notion
anywhere in Compose of "other machines that could also run this
workload" — no cluster membership, no way to track which machines are
currently healthy, no scheduler deciding where a container should run.

Adding "reschedule elsewhere if the host dies" would require Compose
to first know that other hosts EXIST, track their health continuously,
and make scheduling decisions across all of them — none of which is a
small addition to the existing tool. It's a fundamentally different
job: Compose manages "the containers on this one machine," while what
would be needed is "manage containers across an entire pool of
machines, treating them as one resource." That second job is precisely
what orchestrators like Swarm and Kubernetes exist to do — it's not
that Compose does this job poorly, it's that Compose was never built
to attempt it at all, which is why "beyond Compose" genuinely means
reaching for a different category of tool, not a Compose feature
request.