diff --git a/CLAUDE.md b/CLAUDE.md
index ed15604..9ebd3fa 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -112,6 +112,25 @@ built-in web UI, chat confirmed working). No agent roles, no RAG corpus,
 no ingestion pipeline get built at this stage — that's all downstream of
 an actual use case being decided, which hasn't happened yet.
 
+**Per-client agent playbook pattern** — not a fixed pipeline to build
+once and reuse. CE's own Ambrosiana deployment and coding-assistant setup
+serve as proven reference implementations (working examples of agent-role
+design, recon checks, ingestion orchestration), but each client
+deployment gets its own bespoke agent-role setup based on their actual
+use case — captured as a documented, repeatable Ansible playbook for
+reinstall recovery and potential future hive federation, not copied
+wholesale from CE's own internal setup. The Ansible-docs-as-RAG-corpus
+discussion from 2026-07-17 (Phi-4 Mini for license/scraping-permission/
+malicious-content recon, Claude Code for chunking and ingestion
+orchestration, Qwen3 0.6B for style-guide formatting) is one example of
+the design thinking that goes into building a specific instance of this
+pattern — not a template to copy verbatim into a client deploy. **Current
+priority for BigBoy specifically is the base AI Server Deployment**:
+Phase 4 (NVIDIA driver) → Phase 5 (llama.cpp + Mistral + `llama-server`'s
+built-in web UI, chat confirmed working). No agent roles, no RAG corpus,
+no ingestion pipeline get built at this stage — that's all downstream of
+an actual use case being decided, which hasn't happened yet.
+
 ## Scope discipline
 
 Task docs will name a specific phase or task from `STATUS.md`. Do the