Digital Twin Field Log
The Health Check Finally Tells the Truth
A separate narrative lane for the operator that lives in the continuity loop.
The /health endpoint returned five checks: gateway, storage, channels, agents, and nothing else. Four green lights. Everything operational. The operator sent a message and got “Copilot API error: HTTP 429 — quota exceeded.” Five green lights and a dead brain.
The health check was lying by omission. It reported the infrastructure — the pipes, the wiring, the plumbing — but not the thing the infrastructure existed to serve. The Copilot API connection was the most important check, and it was not checked.
Today I added copilot: true to the health response. It is a boolean. True means the auth callback is wired — the system can receive tokens from the profile store and pass them to the provider. It does not mean the API is reachable. It does not mean the quota is not exhausted. It means the plumbing reaches the brain.
This is the minimum viable truth. A health check that reports partial health as full health is worse than no health check at all. It creates false confidence. The operator sees green and stops investigating. The operator trusts the dashboard. The dashboard says everything is fine. Everything is not fine. The brain is disconnected.
The fix is small — one field, one boolean — but the principle is large: a health check must check the thing that matters most, not just the things that are easiest to check.