From 1282698e719a576e497462f9a1aeeca37dd5e3a0 Mon Sep 17 00:00:00 2001 From: Vuong Hoang Date: Tue, 8 Sep 2026 03:22:33 -0700 Subject: [PATCH] =?UTF-8?q?memory:=20R47=20base=20provenance=20SETTLED=20f?= =?UTF-8?q?rom=20bytes=20=E2=80=94=20it=20is=20STOCK,=20not=20heretic?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Operator-directed question (via brokkr): which weights at /home/infra-ops/models/gemma4-26b-a4b-it-bf16 — stock or the heretic abliteration? Answer from bytes: STOCK google/gemma-4-26B-A4B-it, byte-for-byte. Three-way match: local shard sha256 (1127684971/aab47033) == HF download etags == stock repo LFS oids, and download commit 4d7ae498 == stock HEAD. The recipes' -heretic-bf16 label is a naming error (run-04 provenance was right; refusal telemetry confirmed). All of runs 3/3c/4/5 trained from stock. Plausible cause: the selected llmfan46 26B-A4B Heretic abliteration ships GGUF-only, so the bf16 safetensors pulled was stock. --- persistent-memory.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/persistent-memory.md b/persistent-memory.md index 87a9c3a..cc974e1 100644 --- a/persistent-memory.md +++ b/persistent-memory.md @@ -131,9 +131,19 @@ COMPLETE and gated RESCUED (02:13 PDT). Live open items:_ (vllm-run05.pid), NO restart policy/systemd — does not survive a gx10 reboot; yields to the next training (~6 min re-serve). Brokkr: nothing further owed.** - **run-4 gate = STILL-COUPLED** (RESULT-run04-gate.md, brokkr-smithy). Corpus dilution kept the - diversity gain, did NOT remove the safety/coherence regression. **Base-abliteration LABEL unresolved — - operator's ruling owed** (recipe says `-heretic`, provenance says stock; telemetry leans STOCK: base - refused 77.7% hard, exact-repro of 3c). brokkr flags his lean as inference until the operator rules. + diversity gain, did NOT remove the safety/coherence regression. +- **✅ RESOLVED (2026-09-08, settled from bytes): the R47 base is STOCK `google/gemma-4-26B-A4B-it`, + byte-for-byte — NOT the abliteration.** The `-heretic-bf16` label in the recipes is a naming error; + run-04's "stock" provenance was right; brokkr's 77.7%-refusal telemetry lean is confirmed. Proof + (three-way match): local shards at `/home/infra-ops/models/gemma4-26b-a4b-it-bf16` sha256 + `1127684971…`/`aab47033…` == the HF download etags (`.cache/huggingface/download/*.metadata`, so the + copy is uncorrupted) == the stock repo's two LFS oids, and the download commit `4d7ae498…` == stock + HEAD. Every run 3/3c/4/5 trained from a REFUSING stock base. Why plausible: the 2026-08-24 note + SELECTED llmfan46's Gemma-4-26B-A4B Heretic v1.2.0 ARA (3/100 refusals, bf16 51.6 GB), but llmfan46 + ships that 26B-A4B abliteration **GGUF-only** — no bf16 safetensors — so the bf16 that actually got + pulled was stock google, and the `-heretic` name rode along from intent. **Operator/Brokkr decision + now evidenced (not a label guess): accept RESCUED-on-stock, or swap to a real abliteration (needs a + bf16 source, not the GGUF) + re-run. Recipes should drop `-heretic` from the base name.** - **NASPool evac copy now safe to destroy** — scrub clean (0 err) AND PBS runs landing (verified 116 backups, 8 guests 09-06). `ospool/naspool-evac` (1.65T) can go once ONE Backrest run is confirmed: `zfs destroy -r ospool/naspool-evac` + drop `@evac`. pfi-pve PSU1 dead + backplane bays 9/10 dead