SLM operationalization plan
fix(reference): add dated Correction callouts to 9 of 23 reference/ articles, verified against canonical origin/main — stale repo-rename references, Do-Not-Use vocabulary, wrong license claim + unbuilt service-search presented as complete, fabricated hardware specifics, sibling-article RAM-figure conflation, wrong LoRA training framework/rank/precision/GPU tier, compliance-relevant deployed-vs-planned overclaim (escalated), retired research category still listed; 14 verified clean
@@ -47,6 +47,8 @@ This property has a practical implication for quality management: a somewhat low ## LoRA training framework **Correction (2026-08-02, verified against canonical `origin/main`):** four specific claims below don't match the real training script (`service-slm/scripts/run-dpo-training.py`). (1) No Axolotl anywhere in the codebase — the real pipeline calls Hugging Face `peft`/`trl`/`transformers` directly (`LoraConfig`, `DPOTrainer`, `SFTTrainer`). (2) The real rank is `LORA_R = 32`, not 16 (comment: "r=32/alpha=64: a sound default"). (3) The model loads 4-bit quantized (`BitsAndBytesConfig(load_in_4bit=True, ...)`, i.e. QLoRA), not "full-precision." (4) The real Tier B "trainer" node is documented (`app-orchestration-slm/CLAUDE.md`) as an L4 with 24GB, not an A100 with 80GB — the 80GB H100 node is a *different* node ("graph," running Llama 3.3 70B for grammar, not the LoRA trainer). Minor: this article's "OLMo 3.1 32B Think" should be "OLMo 3 32B-Think" (no ".1"). **Flagged, not resolved.** [[yo-yo-lora-training-pipeline|Adapter training]] uses the Axolotl framework, which supports the OLMo 3.1 32B Think model via the standard Hugging Face `AutoModel` interface. A per-tenant adapter trains with low-rank adaptation at rank 16, using the full-precision training path on an A100 GPU with 80 gigabytes of memory. The Axolotl configuration is parameterised by tenant-specific corpus path and output adapter path, so the same training driver handles all tenants by providing different input and output paths. The intended training cadence is quarterly, timed to when each tenant's corpus has accumulated sufficient volume to produce a meaningful signal. An initial training run costs approximately ten to twenty USD in GPU compute at the planned instance class and window length.