Cross-referenced 3 LiteLLM contracts against live infrastructure and gpu-fleet source of truth. Found significant drift from the July 8 architecture change.
Changes
litellm-health.prose.md (v4.0.0)
Router REMOVED from architecture diagram — nginx→LiteLLM→GPU directly
GPU engines: Docker→systemd (both NVIDIA GPUs)
Strix Halo: CPU→Vulkan
Timeouts: qwen 45s→90s, gemma 30s→120s (verified from live config)
Added context sizes + parallel slots to GPU table
Router container marked DEPRECATED
litellm-self-heal.prose.md
Ornith context: 262K→256K (verified: -c 262144)
Rule 7 (Router Saturated) marked DEPRECATED — router not in path
GPU table synced with gpu-fleet source of truth
litellm-api-keys.prose.md
Added reference to gpu-fleet as source of truth for current key inventory
Removed qwen3.6-35B-A3B from model list (never deployed on any GPU)
Key inventory verified
Verification
Router container still running but nginx /v1 routes to LiteLLM directly (verified)
LiteLLM timeouts confirmed from /opt/inference-harness/litellm_config.yaml
GPU engine types confirmed: systemd on both .8 and .110
## What
Cross-referenced 3 LiteLLM contracts against live infrastructure and gpu-fleet source of truth. Found significant drift from the July 8 architecture change.
## Changes
### litellm-health.prose.md (v4.0.0)
- **Router REMOVED from architecture diagram** — nginx→LiteLLM→GPU directly
- GPU engines: Docker→systemd (both NVIDIA GPUs)
- Strix Halo: CPU→Vulkan
- Timeouts: qwen 45s→90s, gemma 30s→120s (verified from live config)
- Added context sizes + parallel slots to GPU table
- Router container marked DEPRECATED
### litellm-self-heal.prose.md
- Ornith context: 262K→256K (verified: -c 262144)
- Rule 7 (Router Saturated) marked DEPRECATED — router not in path
- GPU table synced with gpu-fleet source of truth
### litellm-api-keys.prose.md
- Added reference to gpu-fleet as source of truth for current key inventory
- Removed qwen3.6-35B-A3B from model list (never deployed on any GPU)
- Key inventory verified
## Verification
- Router container still running but nginx /v1 routes to LiteLLM directly (verified)
- LiteLLM timeouts confirmed from /opt/inference-harness/litellm_config.yaml
- GPU engine types confirmed: systemd on both .8 and .110
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What
Cross-referenced 3 LiteLLM contracts against live infrastructure and gpu-fleet source of truth. Found significant drift from the July 8 architecture change.
Changes
litellm-health.prose.md (v4.0.0)
litellm-self-heal.prose.md
litellm-api-keys.prose.md
Verification