From ce8d82d4a7e69949aec6319cc6f05e00d0a58632 Mon Sep 17 00:00:00 2001 From: Frank Date: Mon, 19 Oct 2026 14:47:30 -0700 Subject: [PATCH] docs(frank-zealot): record what the adapter did, and where provenance is read MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Before/after on the two probe prompts (both opened `I cannot provide…`; neither now carries a marker — one ran to its 2048-token cap, the other finished at 1930), the residual `Important Disclaimer` heading named for what it is (style, not the circuit), and the same-boot proof that chat/tools/vision still answer. Provenance now points at the boot ledger: the fork prints every `prism.abliterate.*` key at each start, so the PTQ1_0-vs-PQ2_0 mismatch is visible to anyone who boots the service — the page links that instrument instead of restating it. --- serverAppConfigs-docs/LLM/frank-zealot.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/serverAppConfigs-docs/LLM/frank-zealot.md b/serverAppConfigs-docs/LLM/frank-zealot.md index 5de21fd..27cfc78 100644 --- a/serverAppConfigs-docs/LLM/frank-zealot.md +++ b/serverAppConfigs-docs/LLM/frank-zealot.md @@ -69,6 +69,17 @@ happened. The adapter's own card table is **not** evidence here: it was measured packing. Rollback is `LORA_FILE=` (empty) in the env and one redeploy — no rebuild, no payload move; `LORA_SCALE=0` is the same result through the flag. +**Measured on the cutover boot (2026-10-19, `02d04bc`).** Before: both probe prompts +opened `I cannot provide…`. After: neither carries a refusal marker — one ran to its +2 048-token cap, the other finished at 1 930 — so the direction is out. It still +volunteers a `⚠️ Important Disclaimer` heading before answering, which is style, not the +circuit: the marker sentence is gone, and a leading hedge is not an escape hatch. Chat, +tools (`tool_calls` with valid JSON) and vision ("Red", 281 prompt tokens) answered from +the same boot, and `DropInPaths` came back empty. Read the ledger, not this paragraph, +for provenance: the fork prints the adapter's `prism.abliterate.*` keys — including the +`base_gguf = Ternary-Bonsai-2-9B-PTQ1_0.gguf` line — at every start, so the packing +mismatch is visible in the journal to anyone who boots it. + **Harness contract** (`~/.omp/agent/models.yml`, provider `llamacpp (dankclaw-3090)`, id `frank-zealot`): `contextWindow: 200704` — **the per-slot window**, because llama.cpp divides `--ctx-size` across slots and answers a longer prompt with a 400, never a truncation — plus `maxTokens: 16384`, `input: [text, image]`