What problem does it solve? Working on the Hermes Agent Docker image requires understanding its s6-overlay v3 supervision tree — cont-init.d boot scripts, static s6-rc.d services, runtime-registered per-profile gateways, and the Architecture B CMD pattern. Without this knowledge, developers struggle to add services, debug crash-looping gateways, or understand why containers exit 143. ## Core Features & Use Cases - Service management guidance: Step-by-step recipes for adding static s6-rc.d services, registering per-profile gateway slots under /run/service, and controlling them with s6-svc. - Debugging playbooks: Diagnose gateway crash loops, reconciler failures, permission errors from root-owned profile directories, and exit-code 143 shutdown issues. - Architecture reference: Explains why the container uses the CMD-as-main-program pattern (Architecture B) instead of an s6-supervised main service, including the s6-overlay v3 mechanics that forced the pivot. - Use Case: A developer adds a new supervised service to the Hermes Docker image by creating the s6-rc.d type/run files, wiring dependencies, and verifying with the docker test harness. ## Quick Start Ask the assistant to add a new supervised service to the Hermes Docker image or to diagnose why a profile gateway keeps restarting.