Update CLAUDE.md

CLAUDE.md

@@ -32,8 +32,14 @@ don't leave it stale.
   underneath on NVIDIA/Linux anyway, so switching back would add a layer
   of indirection without avoiding the dependency.
 - **GPU target**: `-DCMAKE_CUDA_ARCHITECTURES=120` (Blackwell / sm_120).
-  Requires NVIDIA driver ≥570; target driver is `595.84` (see
-  `group_vars/bigboy.yml`).
+  Requires NVIDIA driver ≥570. **Do not treat any specific driver version
+  number as a fixed target** — an earlier planning estimate of `595.84`
+  in `group_vars/bigboy.yml` was just that, an estimate. Phase 4 uses
+  AlmaLinux's precompiled open-kmod path (`dnf install
+  almalinux-release-nvidia-driver` then `nvidia-driver-cuda
+  nvidia-open-kmod`), which installs whatever AlmaLinux's own NVIDIA
+  driver repo currently ships — record the *actual* installed version
+  (from `nvidia-smi`) back into `group_vars/bigboy.yml` once confirmed.
 - **Known hazard**: MXFP4-quantized models have open compilation issues on
   sm_120 as of mid-2026. Stick to standard GGUF quants — Q4_K_M or Q5_K_M —
   from established quantizers (Bartowski, Unsloth namespaces on Hugging
@@ -87,6 +93,25 @@ representing current repo state — they're a reference for later, not a
 task in progress. Bringing BigBoy up and running is the current priority;
 this gets picked up afterward.
 
+**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