Add solo operator context and self-healing design requirement

OWNER_PROFILE.md

@@ -59,6 +59,43 @@ This compressed years of typical platform maturity into a shorter cycle.
 
 ---
 
+## Operating Context — Solo Operator
+
+**This is the most important constraint on every design decision.**
+
+ZeroLagHub is built and operated by one person. That means:
+
+- No on-call rotation
+- No one watching dashboards at 3am
+- No team to absorb incident response
+
+The system must therefore be designed to operate without continuous human supervision. This is not a preference — it is a survival requirement.
+
+A solo-operated platform needs:
+- **Self-diagnosing** — knows when something is wrong without a human watching
+- **Self-recovering** — handles common failure modes automatically
+- **Loud about what it can't fix** — escalates only when it genuinely needs a human
+
+The pre-launch blockers in `OPEN_THREADS.md` are not just launch requirements. They are the gap between where the system is and where it can run unsupervised. Email notifications, quota enforcement, world backup, readiness gating — these are all self-healing pieces.
+
+What is already self-healing in ZLH today:
+- Crash recovery with backoff (agent)
+- DB as source of truth (survives restarts)
+- Redis ephemeral by design (clean state on restart)
+- Velocity rehydrates from DB on restart
+- Agent self-update
+
+What still requires human intervention (as of Apr 2026):
+- Fabric readiness gating (manual Velocity restart needed)
+- Velocity resync after restart (running containers go unrouted)
+- Game world data loss (no player-facing backup/restore yet)
+- Unbounded resource consumption (no quota enforcement)
+- Silent failures (no email notifications yet)
+
+Closing these gaps is the path to a system James can step away from.
+
+---
+
 ## Design Philosophy
 
 - Builds systems he wishes existed, not systems for their own sake
@@ -66,6 +103,7 @@ This compressed years of typical platform maturity into a shorter cycle.
 - "I want to wake up and say who do you work for? Me."
 - Applies industrial segmentation thinking to cloud infrastructure
 - No over-reliance on magic — prefers explicit, auditable behavior
+- **Designs for absence** — the system should work when no one is watching
 
 ---
 
@@ -96,3 +134,5 @@ The architecture already supports more than game servers:
 The application layer (games, dev environments) sits on top of what is effectively a lightweight infrastructure platform. The Ghost Shell concept and any future expansion builds on this foundation.
 
 ZLH is closer to an edge control system than a hosting panel. That framing should inform strategic discussions.
+
+See `GHOST_SHELL_VISION.md` for the longer-term platform strategy.