Evidence before advice
What we tested. What we did not.
These first guides were developed with AI assistance and checked against isolated, reproducible Compose fixtures. We do not claim a human expert review or invent expert biographies.
Configuration-level proof
On 12 September 2026 we ran 16 checks with Docker Compose 5.3.0. Each test created its own temporary input files and called docker compose config --format json. The process received an isolated set of demonstration variables and an empty Docker configuration directory.
No images were pulled, no containers were created, and no running service was changed. The result establishes model resolution and validation behavior. It does not establish application behavior, security of a deployed host, or live network reachability.
Trace a claim
- Open the guide’s Sources & evidence section.
- Find the named fixture and its exact inputs.
- Compare expected and observed fields.
- Read the linked official reference for cases outside our fixture.
Port syntax was also checked using Compose. The browser tool has separate boundary and invalid-input tests; it makes no outbound requests.
Changes and corrections
A new Compose version or a different input can change the question. We publish the tested version and date rather than implying that every release was tested. A material correction requires updating the example, rerunning its fixture, and recording the changed evidence.