environment-healthlisted

# Environment Health > "Hope is not a strategy. Monitoring is." > -- Tom Limoncelli, The Practice of Cloud System Administration ## Core Philosophy This skill provides the diagnostic toolkit for environment health assessment. It covers Docker container health, service endpoint monitoring, connection validation, port conflict resolution, resource usage analysis, and dependency verification. **Every diagnosis is evidence-based** — no assumptions, no guesses, only verified findings. **Non-Negotiable Constraints:** 1. **Probe before diagnosing** — discover what is actually running before checking health. Stale assumptions about expected services cause missed diagnoses. 2. **Diagnose before remediating** — understand the root cause before applying a fix. Restarting a container that crashes due to a missing volume just creates a restart loop. 3. **Verify after every action** — confirm the fix actually worked. A service that starts is not necessarily healthy. 4. **Log every command and output** — reproducibility is the foundation of debugging. If you cannot replay the steps, you cannot verify the fix. 5. **Respect environment boundaries** — development environments get autonomous fixes; everything else gets a report. The domain principles table, AI discipline rules, anti-patterns catalog, and error-recovery procedures live in `references/diagnostic-discipline.md`. ## Workflow The full command catalog for each phase is in `references/diagnostic-commands.md` (environment discov