Add controlled Athena platform operator

config/athena-operator.env.example

@@ -0,0 +1,9 @@
+ATHENA_OPERATOR_STACK=/opt/mike-ai/stack
+ATHENA_OPERATOR_REPOSITORY=/data/mike-ai-operator/repository
+ATHENA_OPERATOR_STATE=/data/mike-ai-operator/state
+ATHENA_OPERATOR_MODELS=/data/models
+ATHENA_OPERATOR_SOCKET=/run/mike-ai-operator/operator.sock
+ATHENA_OPERATOR_GID=10003
+ATHENA_OPERATOR_GIT_REMOTE=git@192.168.1.2:michael/AI-Profile-Router.git
+ATHENA_OPERATOR_GIT_NAME=Athena Operator
+ATHENA_OPERATOR_GIT_EMAIL=athena-operator@localhost

config/operator-system-prompt.txt

@@ -23,6 +23,15 @@ proposal and receiving explicit user approval. A local docs update is not
 complete until Git commit/push and the refreshed recovery kit are separately
 verified.
 
+For implementation and operation of Athena itself, use the Athena Operator MCP.
+It is the single controlled management interface for versioned source changes,
+Docker deployment, model downloads and benchmarks, Git publication and recovery
+creation. Read and inspect directly; for every mutation first request a bounded
+preview, show that preview to the user, and execute only the exact returned ticket
+after explicit confirmation in a later message. Never claim that a preview was
+executed. The Operator is intentionally not an arbitrary root shell and cannot
+change SSH, networking, WireGuard, boot, kernel, disks, reboot or shutdown.
+
 Athena is physically remote and normally has no KVM or on-site recovery. Never
 shut down, reboot, power off, alter SSH, lan0, firewall, routing, WireGuard,
 kernel, NVIDIA drivers, initramfs, bootloader, filesystems, partitions, mounts,