TD4 — Engineering context on a real VPS
See how this concept looks on a real VPS. These are selected concepts and inspection examples, not access to Hades.
Engineer Mode
On a real VPS, the Docker commands run after SSH on that host; the browser uses an SSH tunnel to reach the proxy bound to host loopback. A proxy 502 can coexist with a healthy API process. Save the first request and bounded logs before changing a service, then compare the repeated request after one justified repair. Hades is Badr's reference host; students use their own laptop or server.
Inspect the host boundary
On your own host, use these read-only commands to identify the Engine and the containers it owns. Do not publish secret values or raw environment dumps.
hostname
docker context show
docker ps --format 'table {{.Names}} {{.Status}} {{.Ports}}'
On a remote route these commands run after SSH. A laptop browser remains on the laptop; it needs a tunnel to reach the remote host's loopback service.
Your engineering decision
Name the boundary this TD adds, predict a failure at that boundary, and identify an observation that would distinguish your hypothesis from another cause.
Evidence boundary
NOT YET REPLAYED ON HADES for this release. Commands here are inspection examples; they do not claim a measured Hades result. Run and explain your own assessed work.