From f1490b656e913dbbc9b4d5d87c1d07fa441068e3 Mon Sep 17 00:00:00 2001 From: root Date: Sat, 1 Aug 2026 13:35:21 +0000 Subject: [PATCH] no-mistakes(document): docs: fix stale ornith refs to strix-server/strix-moe --- docs/AUTHORING-GUIDE.md | 2 +- infrastructure-update.prose.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/AUTHORING-GUIDE.md b/docs/AUTHORING-GUIDE.md index b9e3533..bd68ee9 100644 --- a/docs/AUTHORING-GUIDE.md +++ b/docs/AUTHORING-GUIDE.md @@ -13,7 +13,7 @@ the description: 1. **What system does this contract touch?** Name the hosts, CTs, containers, and services explicitly. "The inference fleet" is vague. "GPU .8 (RTX 3090, - qwen), .110 (RTX 5070, gemma), .15 (Strix Halo, ornith), and LiteLLM on CT + qwen), .110 (RTX 5070, gemma), .15 (Strix Halo, strix-moe), and LiteLLM on CT 116" is specific. 2. **Who runs this contract, and when?** State the agent, the trigger (cron, diff --git a/infrastructure-update.prose.md b/infrastructure-update.prose.md index ff991d5..0ecbf40 100644 --- a/infrastructure-update.prose.md +++ b/infrastructure-update.prose.md @@ -160,7 +160,7 @@ Before Wave 1, snapshot these files: /opt/home_stack/docker-compose.yml (VM 109 .7) /opt/audiobookshelf/docker-compose.yml (VM 109 .7) /root/.pi/agent/extensions/config.yaml (CT 100 .24) -/etc/systemd/system/ornith-server.service (amdpve .15 — strix-moe) +/etc/systemd/system/strix-server.service (amdpve .15 — strix-moe) /etc/systemd/system/llama-server.service (VM 101 .8, VM 103 .110) # Hermes agent configs (key enforcement — 2026-07-10) /root/.hermes/config.yaml (Mumuni CT 114, Tanko CT 112, etc.)