docs(vault): the census was lying; corrected, and the honest result is flat docs

`scripts/port-census.py` built its corpus from the new directory, so each page
under test was held by itself: every era page reported 0 orphan lines. With the
corpus excluding the file under test, each candidate holds 14-63 sole-record
lines, so no era page is padding and none was trashed.

Deletions of restatement only:
- Multi-Node Runtimes.md (-257): restated launch material owned by
  Qwen3.8 PP Deployment.md; index rows and two Related bullets repointed.
- log.md: 66 headings folded into 35 dated entries (one entry per date, newest
  first), titled headings kept as `date — Title` per the spec's wording, and 78
  lines of transient deploy chatter dropped where every fact token in the line
  is held by an owner page (preserved in .AGENTTRASH/20261019-log-transient/).
- Authentic: the 5-page split reverted (-93); the parent carries
  `okf-exempt: length` and the three stub pages stay deleted.

check-okf.py accepts `## YYYY-MM-DD — Title`; port-census.py excludes the file
under test and gained a docstring note about the trap. One-off compaction tool
moved to ~/.AGENTTRASH. Full suite: 451 tests pass, 0 OKF violations,
155 pages, 0 unresolved links.

AGENTS.md

@@ -388,10 +388,11 @@ the publisher's own **Q8_0** mmproj passed as `--mmproj` — Q8_0 is the
 publisher's requirement for concurrent image requests (the card states the
 BF16 tower can crash `llama-server` when several image requests run at once,
 and this endpoint runs several slots). `frank-zealot`'s `contextWindow` is
-**262144** — the PER-SLOT window (`--ctx-size 524288 --parallel 2` since the
+**200704** — the PER-SLOT window (`--ctx-size 602112 --parallel 3` since the
-2026-10-18 reslice to exact f16 KV), which EQUALS the model's
+2026-10-19 reslice that funded a third slot AND an armed MTP drafter),
-native window; llama.cpp answers a longer prompt with a 400 naming the limit,
+deliberately below the model's native window; llama.cpp answers a longer prompt
-never a truncation, so the harness must compact before it.
+with a 400 naming the limit, never a truncation, so the harness must compact
+before it.
 Note also
 that
 the reasoning channel differs by runtime: llama.cpp AND SGLang (qwen3
@@ -439,10 +440,11 @@ disagrees with it is the bug.
   loader ignoring that metadata dequantizes wrong); payload
   `Bonsai2-9B-MTP/…PQ2_0.gguf` + the publisher's **Q8_0** mmproj (the BF16
   tower can crash the server with concurrent image requests).
-- Shape: `--ctx-size 524288 --parallel 2` = **two conversations at the
+- Shape: `--ctx-size 602112 --parallel 3` = **three conversations at
-  model's native 262,144**, `CACHE_TYPE_K/V=f16`, batch 4096 / ubatch 2048,
+  200,704 each**, `CACHE_TYPE_K=f16` + `CACHE_TYPE_V=q8_0` (asymmetric: 25,088
-  `SPEC_TYPE=none`, `--flash-attn on`, `--jinja`, `--metrics`.
+  B/token, 14,406 MiB of pool), batch 6144 / ubatch 1024,
-- Harness/gate contract: `contextWindow: 262144` is the **per-slot** window
+  `SPEC_TYPE=draft-mtp` (depth 2), `--flash-attn on`, `--jinja`, `--metrics`.
+- Harness/gate contract: `contextWindow: 200704` is the **per-slot** window
   (`n_ctx_slot = CTX_SIZE / PARALLEL`), and llama.cpp answers a longer prompt
   with a 400 rather than truncating. `--metrics` is mandatory or Prometheus
   reads 501 = DOWN beside a healthy service. Presence penalty has no GGUF
@@ -475,473 +477,333 @@ linked runbooks.
 
 **PCIe / multi-GPU**
 
-- **RCCL collectives need PCIe atomics on every participating GPU.** RCCL's
+- **RCCL collectives need PCIe atomics on every participating GPU, and the failure never names
-  kernels carry a hidden hostcall-buffer parameter; ROCr refuses to dispatch
+  atomics.** The kernels carry a hidden hostcall-buffer parameter; ROCr refuses to dispatch them on
-  them when the device has no atomics, and the failure surfaces as
+  a device without atomics and the error surfaces as `hipErrorIllegalState` from `hipLaunchKernel`,
-  `hipErrorIllegalState` ("the operation cannot be performed in the present
+  not as anything that names atomics. The value is consumed at driver PROBE time, so writing the
-  state") from `hipLaunchKernel`, not as anything that names atomics. The
+  AtomicOp Requester bit with `setpci` at runtime changes nothing. Check the CHAIN: `lspci -vv -s
-  value is consumed at driver probe time, so writing the AtomicOp Requester
+  <gpu>` and every upstream bridge must show `AtomicOpsCap: Routing+` (a `Routing-` bridge is a
-  bit with `setpci` at runtime changes nothing. Check the *chain*:
+  hardware wall), and the endpoint's Device Control 2 (`setpci -s <gpu> CAP_EXP+28.w`) must have bit
-  `lspci -vv -s <gpu>` and every upstream bridge must show
+  6 set. AMD desktop platforms put one card on CPU root ports (atomics work) and the rest behind the
-  `AtomicOpsCap: Routing+` (a `Routing-` bridge is a hardware wall), and the
+  chipset (usually not) — that asymmetry is what blocked TP=2 here. A one-card collective proves
-  endpoint's Device Control 2 (`setpci -s <gpu> CAP_EXP+28.w`) must have bit
+  nothing: NCCL short-circuits at `world_size=1`. [[PCIe Link and Atomics]]
-  6 set. AMD desktop platforms put one card on CPU root ports (atomics work)
+- **That wall was physical, and a board swap removed it on 2026-09-20.** dankserver took a board
-  and the rest behind the chipset (usually not) — that asymmetry is what
+  whose CPU lanes bifurcate to x8/x8 Gen5: both cards on root ports, every bridge `Routing+`, BOTH
-  blocked frank-medium's TP=2. A one-card collective proves nothing: NCCL
+  endpoints `ReqEn+`. Bandwidth was never the constraint (a 27B TP=2 allreduce at batch 4 is ≈10 MB
-  short-circuits at `world_size=1`.
+  per token-step, under 0.4 ms at Gen5 x8); the collective choice is — TheRock's RCCL builds lack
-- **That wall was physical, and it was fixed on 2026-09-20 by a board swap.**
+  gfx1201 device code (`invalid device function`), which is why vLLM runs its R4D one-shot allreduce
-  Both paths that put two cards on CPU root ports were: an M.2→PCIe x4 riser
+  here at all. Evidence matrix and the three-arm verdict: [[Dual-R9700-Cooperation]].
-  into a *CPU-attached* M.2 slot, or a board whose CPU lanes bifurcate to
+- **When a GPU collective dies, read the runtime, not the framework.** The message that identified
-  x8/x8. dankserver took the second: **ASUS ProArt B850-Creator WiFi NEO**,
+  the cause came from `AMD_LOG_LEVEL=3` (`Pcie atomics not enabled, hostcall not supported` →
-  `PCIEX16_1` + `PCIEX16_2` at x8/x8 Gen5 on root ports `00:01.1` / `00:01.3`,
+  `AQL dispatch failed!`), never from vLLM or RCCL — the env var costs one line and prints the
-  every bridge now `Routing+` and **both endpoints `ReqEn+`** — the exact
+  failing HIP call with its return code. [[PCIe Link and Atomics]]
-  precondition the old test plan named. Bandwidth was never the constraint (a
+- **Layer split is the no-collective path, on one vendor's cards and across two — and
-  27B TP=2 allreduce at batch 4 is ≈10 MB per token-step, ≈1.4 ms at Gen4 x4
+  `--override-tensor` is what cannot ride with it.** Layers go in order and only the boundary
-  and under 0.4 ms at Gen5 x8).
+  activation crosses PCIe once per forward pass, so it works wherever a collective cannot be
-  **Proven on the same day.** vLLM's R4D one-shot allreduce runs TP=2 here and
+  dispatched (on an RCCL-less fork it beats tensor mode, which falls back to a butterfly allreduce),
-  frank-medium serves on it; llama.cpp's RCCL path was built too
+  and it is the cross-vendor answer too (a CUDA + Vulkan split held a real two-device graph). But
-  (`GGML_HIP_RCCL=ON`) and its tensor mode measured — real collective, slower
+  `--override-tensor <group>=<device>` sets `has_tensor_overrides()`, a REQUIRED term of the
-  shape. Note the collective choice matters: TheRock's RCCL builds lack gfx1201
+  scheduler's `pipeline_parallel` flag, and that flag sets `n_copies`: with `n_copies == 1` a
-  device code (`invalid device function`), which is why R4D is the path vLLM
+  pre-allocated weight on a non-primary device has no backend and the graph aborts (reported with
-  uses at all. Evidence matrix and the measured three-arm verdict:
+  the leaf's op name `(NONE)`). `=CPU` is the only override target that works — the CPU backend is
-  [[Dual-R9700-Cooperation]].
+  last in the list — and pure Vulkan changes nothing: the gate is the override, not the driver mix.
-- **When a GPU collective dies, read the runtime, not the framework.** The
+  Pin the spec-decode drafter to one device; on a split its home is the card holding the target's
-  message that identified the cause came from `AMD_LOG_LEVEL=3`
+  last layers. [[Llama Cpp Multi-Device Splits]] [[x4-pair-experiment]]
-  (`Pcie atomics not enabled, hostcall not supported` → `AQL dispatch
+- **A host↔3090 link at x4 measures 6.72 GB/s, and that is a design constraint, not a detail.**
-  failed!`), not from vLLM or RCCL. `AMD_LOG_LEVEL` costs one env var and
+  Pinned H2D 6.72 / D2H 6.60 GB/s (≈85 % of the Gen4 x4 ceiling), pageable within 1 % of pinned —
-  prints the failing HIP call with its return code.
+  the copies are LINK-limited, so the usual "pageable costs 2×" rule does not apply; the x4 lives in
-- **The software path that puts both cards on ONE model without a collective:
+  the adapter or cable (card and port are both wider). For any engine that STREAMS weights across
-  llama.cpp's layer split.** On the old board vLLM could not do it in any of its
+  it: a 3 MiB slab costs 474 µs, so a 111 GiB A3B model needing ~1.70 GiB of active experts per
-  parallelisms — TP needs an allreduce, PP needs the same p2p primitive, and both
+  token lands at 3.7 tok/s against 20.46 tok/s with the experts COMPUTED in host RAM
-  died on the card that could not dispatch an RCCL kernel. `--split-mode
+  (`-ot exps=CPU`, where the link carries activations only). Streaming loses; RAM does not care.
-  layer` in llama.cpp needs no
+  [[x4-pair-experiment]]
-  collective: layers are distributed in order and only the boundary activation
-  crosses PCIe, once per forward pass. Measured here: 1991 t/s prefill /
-  18.8 tok/s decode layer-split, against 272 / 26.3 tensor (butterfly
-  fallback).
-  This was what `frank-medium` ran until 2026-09-20, when the board swap made
-  collectives legal and radiance TP=2 beat it on every axis (95.8 vs 45.7 t/s
-  decode, 0.21 vs 0.72 s TTFT, 259 vs 72 t/s burst-4) — see
-  [[frank-medium-radiance-mxfp4]]; the llama shape is the rollback target
-  [[frank-medium-llamacpp-dflash2]].
-- **Layer split is also the cross-vendor answer — and `-ot` is what cannot be
-  combined with it.** On Dankclaw (2026-09-16) a CUDA 3090 + Vulkan iGPU layer
-  split ran a real two-device graph: `-dev CUDA0/Vulkan1 -sm layer -ts 0.15/0.85`
-  held 14,994 MiB on the 3090 and gave 27.2 tok/s with 268.5 t/s prefill at 64k
-  depth (iGPU alone: 25.8 / 231.8). What does NOT work is per-tensor placement
-  across devices: `--override-tensor <group>=<device>` sets
-  `has_tensor_overrides()`, a REQUIRED term of the scheduler's
-  `pipeline_parallel` flag (llama-context.cpp:433 — the only place in the tree
-  that reads it), and that flag is what sets `n_copies` in
-  `ggml_backend_sched_new`; with `n_copies == 1` a pre-allocated weight on a
-  non-primary device has no backend and the graph aborts (`ggml-backend.cpp:941`,
-  reported with the leaf's own op name `(NONE)`). `=CPU` is the only override
-  target that works, because the CPU backend is last in the list. Pure Vulkan
-  changes nothing here — the gate is the override, not the driver mix. See
-  [[x4-pair-experiment]].
-- **A host↔3090 link at x4 measures 6.72 GB/s, and that is a design
-  constraint, not a detail.** `pcie-link-test.cu` on Dankclaw (2026-09-16,
-  services stopped): pinned H2D 6.72 GB/s, D2H 6.60 GB/s — 85 % of the Gen4 x4
-  ceiling — with async no better than sync and pageable within 1 % of pinned,
-  i.e. the copies are link-limited rather than staging-limited (the usual
-  "pageable costs 2x" rule does not apply here). The card is x16-capable and the
-  Strix Halo port beneath it is x8-capable (`LnkCap: 16GT/s, Width x8` on
-  `00:03.1`), so the x4 lives in the adapter or cable; the link idles at
-  2.5 GT/s x4 and trains up under load. Consequence for any engine that
-  *streams* weights across it: a 3 MiB slab costs 474 us, and a 111 GiB A3B
-  model needs ~1.70 GiB of active experts per token ⇒ **3.7 tok/s** (4.6 with a
-  20 % resident cache), against **20.46 tok/s** for the same model with the
-  experts *computed* in host RAM by llama.cpp (`-ot exps=CPU`, whence the link
-  carries activations only) and 25–26.5 on the iGPU. Streaming over PCIe loses;
-  computing in RAM does not care. FreeToken — expert LRU in host RAM, exactly
-  this streaming shape — also loads only modelopt block-FP8 safetensors for
-  `qwen3_5_moe`, so a Q4_K_M GGUF is unloadable there before bandwidth is even
-  the question. See [[x4-pair-experiment]].
 
 
 **ROCm / GPU**
 
-- **Layer split needs no collective** — layers go in order and only the boundary
+- **Bundling a ROCm runtime next to a llama.cpp binary: `cp -r SRC DST/` is a trap.** With a missing
-  activation crosses PCIe, so it is the fallback wherever a collective cannot be
+  `DST`, cp creates `DST` as a copy of `SRC` and drops one directory level. rocBLAS and hipBLASLt
-  dispatched (and on an RCCL-less fork it beats tensor mode, which falls back to
+  look for their device code at a FIXED depth (`../lib/rocblas/library`,
-  a butterfly allreduce). Pin the spec-decode drafter to one device: an unpinned
+  `../lib/hipblaslt/library/<arch>`), so the flattened copy fails at REQUEST time, not load time:
-  draft under tensor mode aborts the KV build, and on a split its home is the
+  the engine reads the weights, answers `/health` and dies on the first completion with
-  card holding the target's last layers. Deployed history:
+  `Cannot read .../TensileLibrary.dat: No such file or directory for GPU arch : gfx1201`. Declare
-  [[frank-medium-llamacpp-dflash2]].
+  the destination, then copy the contents.
-- **Bundling a ROCm runtime next to a llama.cpp binary: `cp -r SRC DST/` is a
+- **mmap must stay on** for the big-PLE models: `--no-mmap` forces the ~50 GiB PLE table into
-  trap.** With a missing `DST`, cp creates `DST` as a copy of `SRC` and drops
+  anonymous memory → silent cgroup kill, with dmesg as the only evidence. mmap pages ARE page cache,
-  one directory level. rocBLAS and hipBLASLt look for their device code at a
+  and pinning the PLE tensor with `-ot` cost 23 → 13.4 t/s. [[Llama Cpp Serving Sizing]]
-  fixed depth (`../lib/rocblas/library`, `../lib/hipblaslt/library/<arch>`),
+- **HIP reads bare env vars** `TEMP`, `HOST`, `GPU_MAX_HEAP_SIZE`. Serve scripts export env files
-  and the flattened copy fails at *request* time, not load time: the engine
+  with `set -a`, so a tunable named `TEMP` leaks into HIP (`TEMP=1.0` sent the JIT cache to path
-  reads the weights, answers `/health` and dies on the first completion with
+  `1.0` and segfaulted every load, fixed 2026-08-13 by renaming to `TEMPERATURE`). Never name a
-  `Cannot read .../TensileLibrary.dat: No such file or directory for GPU arch
+  tunable these; check with
-  : gfx1201`. Declare the destination, then copy the contents.
-- **mmap must stay on** for the big-PLE models: `--no-mmap` forces the
-  ~50 GiB PLE table into anonymous memory → silent cgroup kill, dmesg is the
-  only evidence. mmap pages ARE page cache. Never pin the PLE tensor with
-  `-ot` (23 → 13.4 t/s).
-- **HIP reads bare env vars** `TEMP`, `HOST`, `GPU_MAX_HEAP_SIZE`. Serve
-  scripts export env files with `set -a`, so a tunable named `TEMP` leaks
-  into HIP (`TEMP=1.0` sent the JIT cache to path `1.0` and segfaulted every
-  load, fixed 2026-08-13 by renaming to `TEMPERATURE`). Never name a tunable
-  these; check with
   `strings /opt/rocm-*/lib/libamdhip64.so.* | grep -xE "TEMP|HOST|GPU_MAX_HEAP_SIZE"`.
-- **`-DGGML_CUDA_FA_ALL_QUANTS=ON` is required** for q8_0 KV + flash
+- **`GGML_CUDA_FA_ALL_QUANTS` is dead; do not build for it.** Verified on this host 2026-10-19:
-  attention on CUDA builds; without it prefill collapses ~12x (95 vs 1300+
+  master's `ggml/cmake/common.cmake` warns it is deprecated in favour of `GGML_CUDA_FA_QUANTS`, the
-  t/s, measured 2026-08-17).
+  successor's DEFAULT pair list (`q4_0-q4_0;q8_0-q8_0;f16-f16;bf16-bf16`) already compiles the
-- **Flash-Next MTP heads do not load on any current loader** — they need full
+  quantized-KV kernels with the old flag OFF, and neither llama tree on this host references the old
-  per-layer `blk.<il>.hc_attn_norm.weight` and ship only `blk.48` (verified
+  macro anywhere under `ggml/src/ggml-cuda/`. The old "~12× prefill collapse" belongs to the older
-  3x). Don't re-attempt without new loader support.
+  source line. Prove a build's KV ability from its `CMakeCache.txt`. [[frank-zealot]]
-- **QSA flash-attn assert:** `GGML_ASSERT(a-type == GGML_TYPE_F32)` on
+- **Flash-Next MTP heads do not load on any current loader** — they need full per-layer
-  qwen4exp needs `scripts/patches/qwen4exp-qsa-f32-mask.patch` — but only on
+  `blk.<il>.hc_attn_norm.weight` and ship only `blk.48` (verified 3×). Do not re-attempt without new
-  the agentionai FAST layer set; the kingjones STRIX set works unpatched.
+  loader support.
-- **GPU budget on Dankclaw is the GTT aperture (~114 GiB), not the
+- **QSA flash-attn assert:** `GGML_ASSERT(a-type == GGML_TYPE_F32)` on qwen4exp needs
-  rocm-smi "dedicated" figure.** The Radeon 8060S (gfx1151) reports
+  `scripts/patches/qwen4exp-qsa-f32-mask.patch` — but only on the agentionai FAST layer set; the
-  116,732 MiB (`llama-server --list-devices`;
+  kingjones STRIX set works unpatched. [[Llama Cpp Serving Sizing]]
-  `gtt_total=122402963456` in `/sys/class/drm/card1/device/`). The older
+- **The GPU budget on Dankclaw is the GTT aperture, not the rocm-smi "dedicated" figure.** The
-  "64 GiB, SVM-backed" lesson was already stale — the CIRU Orca predecessor
+  Radeon 8060S (gfx1151) reports 116,732 MiB (`llama-server --list-devices`; `gtt_total` in
-  held 92.6 GiB of weights on the iGPU. `free`/`dmidecode` show the
+  `/sys/class/drm/card1/device/`), and the older "64 GiB, SVM-backed" lesson was already stale.
-  CPU-side carve-out — intentional, do not change.
+  `free`/`dmidecode` show the CPU-side carve-out — intentional, do not change. [[Dankclaw System Specs]]
 
 **Load / crash diagnosis**
 
-- Model load is slow (minutes cold); health returns 503 while loading; do
+- Model load is slow (minutes cold) and health returns 503 while it runs: do NOT kill the process,
-  not kill the process. `deploy.sh` waits up to 20 minutes (`LLM_WAIT`). On
+  `deploy.sh` waits up to 20 minutes (`LLM_WAIT`). On halogen the FIRST request after a (re)start
-  halogen, the FIRST request after a (re)start can go silent ~45–60 s
+  can go silent for ~45–60 s (`engine_unresponsive`, 503s) and then self-recovers — do not restart
-  (health `engine_unresponsive`, 503s) and then self-recovers — do not
+  over it. [[frank-dragoon]]
-  restart over it.
+- Crash-loop procedure: (1) `journalctl -u <svc> -n 100` AND the kernel line via `journalctl -k` (a
-- Crash-loop procedure: (1) `journalctl -u <svc> -n 100` + kernel line via
+  segfault at address 8 in `libamdhip64` is a NULL unref in HIP); (2) run the serve script, then the
-  `journalctl -k` (segfault at address 8 in `libamdhip64` = NULL unref in
+  raw binary — a different outcome isolates the env file; (3) `gdb -batch -ex run -ex "bt 25"
-  HIP); (2) run serve script, then raw binary — different outcome isolates
+  --args bash scripts/serve-<svc>.sh`, because llama-server buffers stdout and loses the log tail on
-  the env file; (3) `gdb -batch -ex run -ex "bt 25" --args bash
+  SIGSEGV: trust gdb, not the log; (4) `amdgpu: SVM mapping failed` spam is a symptom, not a root
-  scripts/serve-<svc>.sh` — llama-server buffers stdout and loses the log
+  cause. [[LLM Performance Diagnosis]]
-  tail on SIGSEGV; trust gdb, not the log; (4) `amdgpu: SVM mapping failed`
+- Journal signatures: a client abort logs `W srv stop: cancel task, id_task = N` while a natural stop
-  spam is a symptom, not a root cause.
+  logs only `slot release` with `truncated = 0`. The server never preempts a running generation;
-- Journal signatures: client abort logs `W srv stop: cancel task, id_task =
+  excess tasks queue when slots are busy.
-  N`; natural stop logs only `slot release` with `truncated = 0`. The server
-  never preempts a running generation; excess tasks queue when slots are
-  busy.
 
 **Host memory / swap**
 
-- Swap resize ordering: create and `swapon` the replacement BEFORE `swapoff`
+- **Swap resize ordering: create and `swapon` the replacement BEFORE `swapoff` of the old one**, or
-  of the old one, or live pages must land in RAM that `MemAvailable`
+  live pages must land in RAM that `MemAvailable` overstates. Dankclaw's 64 GiB `/swap.img`
-  overstates. Dankclaw swap (64 GiB at `/swap.img`, fstab-driven) protects
+  (fstab-driven) protects the co-tenants, not an endpoint with pinned weights — paging the KV pool
-  the co-tenants, not frank-dragoon — pinned weights don't swap, and paging
+  is worse than the OOM it prevents. Host swap state is invisible to `deploy.sh` (no repo file):
-  the KV pool is worse than the OOM it prevents.
+  `swapon --show` before reasoning about headroom. [[Swap Configuration]]
-- Host swap state is invisible to `deploy.sh` (no repo file) — check
+- **A sysfs raise is a countdown to the next reboot.** `ttm.pages_limit` defaults to half of RAM, so
-  `swapon --show` before reasoning about headroom.
+  a manual raise vanished with a power failure, frank-archon's pinned-ledger preflight refused the
-- **A sysfs raise is a countdown to the next reboot.** `ttm.pages_limit` defaults
+  start, and `Restart=always` re-ran that refusal 6,919 times in ~20 h — **a unit in
-  to half of RAM, so the manual raise to 200 GiB (2026-10-05) vanished with the
+  `activating (auto-restart)` that exits 1 in 50 ms with no container and no engine log is a
-  2026-10-12 23:17 POWER FAILURE on dankserver: the cap fell to 125,988 MiB,
+  PREFLIGHT refusal, not an engine fault.** Repo law now: `scripts/ttm-preflight.sh` raises the knob
-  frank-archon's pinned-ledger preflight (floor 150,000 MiB) refused the start,
+  to `FRANK_ARCHON_TTM_TARGET_MIB` itself, re-reads, and refuses by name only after a write the
-  and `Restart=always` re-ran that refusal **6,919 times in ~20 h** — a unit in
+  kernel rejected. Never prescribe a manual sysfs write as the recovery procedure for a service that
-  `activating (auto-restart)` that exits 1 in 50 ms with no container and no
+  can boot before a human reaches it. [[frank-archon]]
-  engine log is a PREFLIGHT refusal, not an engine fault. Repo law now:
+- **Silent RAM corruption outranks every software theory.** frank-archon's long-conversation
-  `scripts/ttm-preflight.sh` (sourced by `serve-frank-archon.sh`) raises the knob
+  repetition/garbage was marginal DDR5 at 4800 MT/s on four DIMMs, fixed by dropping to 4600.
-  to `FRANK_ARCHON_TTM_TARGET_MIB` itself, re-reads, and refuses by name only
+  Consumer non-ECC raises NO MCE for a silent flip, and a short in-band pattern check (60 s over
-  after a write the kernel rejected. Never prescribe a manual sysfs write as the
+  8 GiB of 246 GiB) is not a stability proof — both instruments said "ruled out" while the RAM was
-  recovery procedure for a service that can boot before a human reaches it.
+  the cause, and "4800 is the JEDEC floor" is a rating, not a margin guarantee. When the fault is
-- **Silent RAM corruption outranks every software theory.** frank-archon's
+  data-shaped (NaN states, garbage tokens) and a software revert does not move it, price in the RAM
-  ~40k-token output corruption (2026-10-04/05, repetition/garbage in long
+  before the runtime; a revert tested under the same marginal hardware is itself confounded.
-  agent conversations) was marginal DDR5 at 4800 MT/s on four DIMMs, fixed
+  [[frank-archon]]
-  by 4600. Consumer non-ECC memory raises **no MCE** for a silent flip, and
-  a short in-band pattern check (60 s, 8 GiB of 246 GiB) is not a stability
-  proof — combined, those two instruments said "ruled out" while the RAM
-  was the cause. "4800 is the JEDEC floor on 5600-rated DIMMs" is a rating,
-  not a margin guarantee. When the fault is data-shaped (NaN states,
-  garbage tokens) and a software revert doesn't move it, price in the RAM
-  before the runtime — and remember a revert tested under the same marginal
-  hardware is itself confounded. See the runbook's 2026-10-05 section.
 
 **Runtime-specific guards**
 
-- **Rootless podman cannot RAISE rlimits, and `--ulimit nofile=1048576`
+- **Rootless podman cannot RAISE rlimits, so `--ulimit nofile=1048576` dies at container CREATE**,
-  dies at container create, not at runtime.** runc reports
+  not at runtime: runc reports `error setting rlimit type 7: operation not permitted` (type 7 =
-  `error setting rlimit type 7: operation not permitted` (type 7 =
+  RLIMIT_NOFILE) when the requested hard limit exceeds the host process's ceiling (524288 on
-  RLIMIT_NOFILE) when the requested hard limit exceeds the host process's
+  Dankclaw). Inherited-equal limits are fine, so `memlock=-1:-1` works iff the unit grants
-  hard limit — on Dankclaw that ceiling is 524288. Inherited-equal limits
+  `LimitMEMLOCK=infinity` — systemd is privileged and the value flows through podman to runc without
-  are fine, so `memlock=-1:-1` works iff the unit grants
+  any raise. Upstream halogen's own run lines pass NO `--ulimit` at all: copy vendor run lines
-  `LimitMEMLOCK=infinity` (systemd is privileged; the value flows through
+  before adding flags. [[frank-dragoon]]
-  podman to runc without any raise). Upstream halogen's own run lines pass
+- **A GGUF's custom tensor type picks the runtime — read the histogram before promising a file to a
-  NO `--ulimit` at all — copy vendor run lines before adding flags
+  loader.** `Qwen3.8-27B-Q8_0_ROCMFPX_AGENT.gguf` is ftype 115 over 311 tensors of type 103
-  (measured 2026-10-05 on the frank-dragoon cutover).
+  (`GGML_TYPE_Q8_0_ROCMFPX`), so stock llama.cpp and gufo refuse it at load and the fork was not a
-- **Kairic Edge** (if ever re-deployed): the pinned CK commit needs
+  preference but the only door. Counting tensor types out of the GGUF KV section takes one python
-  `third_party/composable_kernel/include/ck/config.h` generated manually
+  read and settles a runtime argument in minutes. Build identity matters as much as the fork: the
-  (untracked; `git clean` removes it), and its greedy-argmax fastpath rejects
+  2026-08-25 ROCmFPX builds SIGSEGV in `ggml_compute_forward_set_rows` on this same file, so
-  non-greedy requests and reasoning budgets. Re-test chat before production.
+  `scripts/build-rocmfpx.sh` pins commit `36e9acd` by SHA. [[GGUF Compatibility]]
-- **FastMTP sidecar**: build must be commit `4df29be4` + the HauhauCS patch;
+- **Speculative-decode flags move as a SET.** Handing the fork `--model-draft` with no `--spec-type`
-  stock binaries fail the draft load with a tensor-shape mismatch.
+  (the naive way to build a "no MTP" bench arm) segfaulted at load, core dumped, no diagnostic. A
-- **A GGUF's custom tensor type picks the runtime — read the histogram before
+  baseline arm must strip `--model-draft` AND every `--spec-draft-*` AND `--spec-type`, or it
-  promising a file to a loader.** `Qwen3.8-27B-Q8_0_ROCMFPX_AGENT.gguf` is
+  measures a crash instead of the absence of drafting. [[frank-zealot]]
-  ftype 115 with 311 tensors of type 103 (`GGML_TYPE_Q8_0_ROCMFPX`); stock
+- **An orphaned scratch server taxes the whole host.** A bench child left alive by a client-side
-  llama.cpp and gufo refuse it at load, so ROCmFPX was not a preference but
+  exception kept ~26 GiB of weights resident on a 121 GiB box and pushed `available` to 3 GiB, so
-  the only door. Counting tensor types out of the GGUF KV section takes one
+  every later rate was suspect. Record the child pid, kill it in a `finally`, then prove `free` came
-  python read and settles a runtime argument in minutes. The build identity
+  back before believing a number — and kill by pid, never `pkill -f llama-server`.
-  matters as much as the fork: the 2026-08-25 ROCmFPX builds SIGSEGV in
+  [[LLM Bench Windows and Measurement]]
-  `ggml_compute_forward_set_rows` on this same file, so
+- Retired-runtime traps that can come back: **Kairic Edge** needs
-  `scripts/build-rocmfpx.sh` pins commit `36e9acd` by SHA.
+  `third_party/composable_kernel/include/ck/config.h` generated manually (untracked, so `git clean`
-- **Speculative-decode flags move as a SET.** Handing the ROCmFPX fork
+  removes it) and its greedy-argmax fastpath rejects non-greedy requests and reasoning budgets, so
-  `--model-draft` with no `--spec-type` (the naive way to build a "no MTP"
+  re-test chat before production; the **FastMTP sidecar** must be commit `4df29be4` + the HauhauCS
-  bench arm) segfaulted at load, core dumped, no diagnostic (2026-10-02). A
+  patch, since stock binaries fail the draft load with a tensor-shape mismatch.
-  baseline arm must strip `--model-draft` AND every `--spec-draft-*` AND
-  `--spec-type`, or it measures a crash instead of the absence of drafting.
-- **An orphaned scratch server taxes the whole host.** A bench child left
-  alive by a client-side exception kept ~26 GiB of weights resident on a
-  121 GiB box, pushed `available` to 3 GiB, and every later rate was suspect.
-  Record the child pid and kill it in a `finally`, then prove `free` came back
-  before believing a number. Kill by pid — never `pkill -f llama-server`,
-  which also hits frank-zealot.
 
 **llama.cpp serving**
 
-- **MTP is a property of the FILE, not of the flags.** The `-mtp` GGUF build
+- **MTP is a property of the FILE, not of the flags.** The `-mtp` export carries the head as
-  carries the head as `blk.<n>.nextn.*` (`qwen35.nextn_predict_layers = 1`);
+  `blk.<n>.nextn.*` (`qwen35.nextn_predict_layers = 1`); `--spec-type draft-mtp` sets
-  `--spec-type draft-mtp` then sets `load_mtp`, and the draft context runs on
+  `load_mtp` and the draft context runs on the MAIN model's weights (`shares_model`), so there
-  the MAIN model's weights (`shares_model`), so there is no second copy of a
+  is no second copy of a 12 GiB model in VRAM and no `-md` argument. The plain build has no MTP
-  12 GiB model in VRAM and no `-md` argument. The plain build has no MTP
+  tensors at all, and pointing `--model-draft` at that file loads it twice. [[frank-zealot]]
-  tensors at all, and pointing `--model-draft` at the file would load it twice.
+- **What can be chained: ONE context-backed drafter plus any number of draftless ngram types.**
-- **What can be chained, what cannot, and what a chain costs on a hybrid.**
+  `--spec-type a,b` chains in a fixed internal order (CLI order irrelevant) and the gate is
-  `--spec-type a,b` builds every enabled implementation and chains drafting
+  `ctx_dft`: the ngram family is added unconditionally while `draft-mtp`, `draft-dflash`,
-  through them, in a fixed internal order (ngram types first, then the
+  `draft-dspark` and `draft-eagle3` all need a draft CONTEXT. So `draft-dflash,ngram-mod` is
-  drafters — CLI order is irrelevant). The gate is `ctx_dft`: **draftless**
+  legal (measured 2.6x the drafter alone on prompt-echo traffic) but `draft-mtp,draft-dflash`
-  types (the ngram family) are added unconditionally, while `draft-mtp`,
+  dies at load — *"context type MTP requested but model doesn't contain MTP layers"*. **A LEGAL
-  `draft-dflash`, `draft-dspark` and `draft-eagle3` all require a draft
+  chain can still lose on a recurrent model:** `draft-mtp,ngram-mod` on frank-dragoon's qwen35
-  CONTEXT. So a chain may hold one context-backed drafter plus any number of
+  hybrid measured −15 % prose / −7 % block-copy, because adding the ngram layer logs
-  ngram types — `draft-dflash,ngram-mod` is legal and measured (2.6x the
+  `recurrent state rollback is not compatible with 'ngram-mod' - disabling rollback support` and
-  drafter alone on prompt-echo traffic, byte-identical to it on prose at the
+  MTP verification depends on that rollback. Measure chains per architecture, never by analogy.
-  fleet's 48/64 window) — but `draft-mtp,draft-dflash` dies at load: *"context
+  [[frank-dragoon]]
-  type MTP requested but model doesn't contain MTP layers"*, because MTP
+- **A drafter's KV scales with the TARGET's context, and its window policy decides the price.**
-  builds its context against whatever model the draft context holds. Two
+  The draft context is built at `llama_n_ctx(ctx_tgt)` with no flag to cap it, so a drafter
-  context-backed types cannot share one process, and MTP's head only loads
+  declaring NO sliding window caches the whole window on `--spec-draft-device` and can OOM the
-  when MTP **is** the draft model. **A LEGAL chain can still lose on a
+  first draft graph capture AFTER `/health` has answered. Read `sliding_window` out of the
-  recurrent model:** `draft-mtp,ngram-mod` on frank-dragoon's qwen35 hybrid
+  drafter's GGUF header before sizing, and prefer a skewed `-ts` over a context cut.
-  measured −15 % prose / −7 % block-copy (2026-10-03) — adding the ngram layer
+  [[Llama Cpp Multi-Device Splits]]
-  logs `recurrent state rollback is not compatible with 'ngram-mod' -
+- **A draft context bills its own f16 KV over the WHOLE POOL, not the slot**, plus its own
-  disabling rollback support`, and MTP verification depends on that rollback,
+  compute buffers, so on a single-card endpoint that squeeze can cost more than the drafter
-  so acceptance drops on ALL traffic even where the matcher fires. Measure
+  wins. The MTP question is never "does the file carry the head" but what draft KV + buffers
-  chains per architecture, never by analogy.
+  cost against what the batch knobs leave for compute. Measure the arm, never the flag.
-- **A drafter's KV scales with the TARGET's context, and its window policy
+  [[frank-zealot]]
-  decides the price.** The draft context is built at `llama_n_ctx(ctx_tgt)` with
+- **A quant's scale overhead belongs in its byte rate; doubling a measured figure to "get the
-  no flag to cap it, so a drafter declaring NO sliding window caches the whole
+  f16 number" invents 6.25 %.** q8_0 is 1.0625 B/element (32 codes + one 2-byte scale per
-  window on `--spec-draft-device` and can OOM the first draft graph capture
+  32-block), f16 is exactly 2.0 ⇒ the ratio is **1.882×**, not 2×. Derive byte rates from element
-  AFTER `/health` has answered. Read `sliding_window` out of the drafter's GGUF
+  count × block layout, then check them against the boot ledger — this repo carried an invented
-  header before sizing, and prefer a skewed `-ts` over a context cut. Worked
+  2× number for weeks. Current KV math: [[frank-zealot]]
-  example: [[frank-medium-llamacpp-dflash2]].
+- **`--ubatch-size` has an OPTIMUM, not a plateau, and the curve is BACKEND-SPECIFIC — never
-- **A draft context bills its own f16 KV over the WHOLE POOL, and on a
+  carry it across hosts.** Its compute buffers land about TWICE as heavy on the card that holds
-  single-card endpoint that squeeze can cost more than the drafter wins.** With
+  the output layers and the drafter, so a split balanced at one batch is unbalanced at another:
-  `--parallel N` the drafter pays the pool, not the slot, plus its own compute
+  re-measure the balance after any batch change. The logical `--batch-size` is nearly free; a
-  buffers. So the MTP question is never "does the file carry the head" but "what
+  large-batch allocation can fail on BUFFER CONTIGUITY while totals still fit, which no totals
-  do draft KV + buffers cost against what the batch knobs leave for compute" —
+  model can see. A prompt shorter than the ubatch cannot see the knob at all — that is the
-  a per-shape answer. Measure the arm, never the flag; the booted arm table is
+  control that proves the knob, not the traffic, moved the number. The 2× R9700 split peaks at
-  on [[frank-zealot]].
+  512; the CUDA 3090 has no interior optimum up to 2048. When a bench IS ordered, A/B it by
-- **A quant's scale overhead belongs in its byte rate; doubling a measured
+  restarting the SERVICE through a transient `FRANK_<SVC>_ENV_FILE` drop-in, never a scratch
-  figure to "get the f16 number" invents 6.25 %.** q8_0 is 1.0625 B/element
+  port: one card holds one server. Ladders: [[frank-medium-llamacpp-dflash2]] and
-  (32 codes + one 2-byte scale per 32-block), f16 is exactly 2.0 ⇒ the ratio is
+  [[frank-zealot]].
-  **1.882×**, not 2×. Derive byte rates from element count × block layout, then
+- **One `-ts` step is one LAYER, and a hybrid stack's layers are not the same size** (a DeltaNet
-  check them against the boot ledger — this repo carried an invented 2× number
+  boundary and a full-attention boundary can differ by ~1 GiB each with its own KV), so balance
-  for weeks. Current KV math: [[frank-zealot]].
+  by measurement. An affine fit reproduces the deployed point and overstates the gaps in between.
-- **`--ubatch-size` has an OPTIMUM, not a plateau, and the curve is
+  [[Llama Cpp Multi-Device Splits]]
-  BACKEND-SPECIFIC — never carry it across hosts.** Its compute buffers land
+- **`ngram-mod` prints no startup banner.** The load log names `draft-dflash` and nothing for the
-  about TWICE as heavy on the card that holds the output layers and the drafter,
+  matcher, so a chain can look unengaged while it works. Identify it behaviourally (`draft_n` > 0
-  so a split balanced at one batch is unbalanced at another: re-measure the
+  only where text repeats) or by the per-task `draft acceptance = ... mean len = ...` line. It
-  balance after any batch change. The logical `--batch-size` is nearly free.
+  costs no VRAM (a 64 MiB host-RAM hash table) and its window decides which traffic it can see:
-  A large-batch allocation can fail on BUFFER CONTIGUITY while totals still fit
+  too short and it proposes on ordinary prose fragments, costing verification without acceptance.
-  — no totals model can see that. Ladders: [[frank-medium-llamacpp-dflash2]]
+  [[Llama Cpp Multi-Device Splits]]
-  (R9700 split) and [[frank-zealot]] (CUDA 3090).
+- **`--parallel` divides the pool, so MORE conversations cost WINDOW, and the per-slot number is
-- **On the CUDA 3090 that same knob has no interior optimum up to 2048.** A
+  the contract — not `ctx-size`.** `n_ctx_slot = CTX_SIZE / PARALLEL`, and llama.cpp refuses a
-  prompt shorter than the ubatch cannot see the knob at all — that is the
+  prompt longer than the SLOT with a 400 even when the pool has room, so `models.yml`
-  control that proves the knob, not the traffic, moved the number. When a bench
+  `contextWindow` MUST follow every reslice. Both slot directions cost or buy window, never
-  IS ordered, A/B it by restarting the SERVICE through a transient
+  pool; shorter slots decode slightly faster. Measured reslices: [[frank-zealot]].
-  `FRANK_ZEALOT_ENV_FILE` drop-in, never a scratch port: one card holds one
+- **Price a VRAM budget from two boots, never from a formula — and an mmproj costs ~1.5× its file
-  server. Numbers: [[frank-zealot]].
+  size** (the encoder's activation and compute buffers ride with it). Subtracting two booted rows
-- **One `-ts` step is one LAYER, and a hybrid stack's layers are not the same
+  isolates it exactly; extrapolating weights+KV+"a bit for buffers" is what leaves 1.1 GiB free
-  size** (a DeltaNet boundary and a full-attention boundary can differ by ~1 GiB
+  when you meant 2.7. Then solve `KV ≤ card − non-KV − headroom` and round to a multiple of
-  each with its own KV), so balance by measurement. An affine fit reproduces the
+  `PARALLEL × 4096`. **The projector is NOT billed in llama.cpp's own fit check**: the engine
-  deployed point and overstates the gaps in between.
+  prints its worst case and fits WITHOUT it, so price a shape from settled `nvidia-smi` after a
-  [[frank-medium-llamacpp-dflash2]].
+  real boot — the projector, and any drafter context, lands after `/health` would already have
-- **ngram-mod prints no startup banner.** The load log shows the drafter's
+  answered (same class as the DSpark drafter OOM). Two-boot table: [[frank-zealot]].
-  `adding speculative implementation 'draft-dflash'` and nothing at all for the
+- **`images` and `image_url` are NOT interchangeable: only the content part reaches the model.**
-  matcher, so a chain can look unengaged while it is working. Identify it
+  `--mmproj` loads, `usage.prompt_tokens` rises, and the model still invents an answer if the
-  behaviourally (`draft_n` > 0 only where text repeats) or by the per-task
+  client used the legacy top-level `images` field on `/v1/chat/completions` — frank-zealot
-  `draft acceptance = ... mean len = ...` line. It costs no VRAM (a 64 MiB
+  answered "Brown." for a solid-red PNG that way and "Red." through the OpenAI `image_url` part.
-  host-RAM hash table) and its window decides which traffic it can see: too
+  The failure is silent because a hallucinated color is a plausible answer; probe with a solid
-  short and it proposes on ordinary prose fragments, which costs verification
+  color and expect an exact word. [[frank-zealot]]
-  without acceptance.
+- **`--jinja` is what `tools` needs.** A subagent died with `500 tools param requires --jinja
-- **`--parallel` divides the pool, so MORE conversations cost WINDOW, and the
+  flag` on the ik_llama.cpp runtime that served frank-dragoon: every tool-using agent on that
-  per-slot number is the contract — not `ctx-size`.** `n_ctx_slot =
+  endpoint was broken and the failure read like a model fault. Mainline llama.cpp defaults
-  CTX_SIZE / PARALLEL`, and llama.cpp refuses a prompt longer than the SLOT with
+  `--jinja` on and the serve scripts pin it; halogen also accepts `tools` and returns
-  a 400 even when the pool has room, so `models.yml` `contextWindow` must follow
+  `tool_calls`. Check tool support before routing a role at an endpoint.
-  every reslice. Both slot directions cost or buy window, never pool; shorter
+- **A model's own template can REJECT the harness's thinking level.** Qwen3.8's template accepts
-  slots decode slightly faster (less attention to scan, one fewer recurrent
+  only `xhigh`, `medium` and `low` for `reasoning_effort` and raises on anything else — HTTP 500,
-  state). Measured reslices: [[frank-zealot]].
+  not a clamp — so the harness's levels must be folded onto that set in `models.yml`
-- **Price a VRAM budget from two boots, never from a formula — and an mmproj
+  (`compat.reasoningEffortMap`). A role whose level is unmapped fails on its FIRST request and
-  costs ~1.5× its file size** (the encoder's activation and compute buffers ride
+  the failure names Jinja, not the model: every subagent on `frank-zealot` died with
-  with it). Subtracting two booted rows isolates it exactly; extrapolating
+  `Unexpected reasoning effort high` until `high: xhigh` was added. Halogen accepts the wider
-  weights+KV+"a bit for buffers" is what leaves 1.1 GiB free when you meant 2.7.
+  set, so the two entries legitimately differ.
-  Then solve `KV ≤ card − non-KV − headroom` and round to a multiple of
+- **Thinking tokens count against `max_tokens`, so a short-budget vision probe reads as
-  `PARALLEL × 4096`. The two-boot table: [[frank-zealot]].
+  blindness.** A probe at `max_tokens: 64` returned `content: ""` with `finish_reason: "length"`
-- **`images` and `image_url` are NOT interchangeable: only the content part
+  and half a thought in `reasoning_content` while the image HAD reached the model (322 prompt
-  reaches the model.** `--mmproj` loads, `usage.prompt_tokens` rises, and the
+  tokens vs 42 for the text alone). Budget ≥512 for any thinking model you probe for vision.
-  model still invents an answer if the client used the legacy top-level
+- **The FIRST request after a boot is a warmup artifact**, and the 3× spread on one shape makes
-  `images` field on `/v1/chat/completions` — frank-zealot answered "Brown." for
+  graph-capture cost read as a model fault. Benchmark the second request or later.
-  a solid-red PNG that way and "Red." through the OpenAI `image_url` part. The
+  [[frank-zealot]]
-  failure is silent because a hallucinated color is a plausible answer. Probe
+- **A fork build hides its own dtype laws.** Vendor builds carry their own compile options, so
-  vision with a solid color and expect an exact word.
+  prove a build's KV behaviour from the KV buffer line in the boot ledger and its
-- **`--jinja` is what `tools` needs.** On 2026-09-16 a subagent died with
+  `CMakeCache.txt` — never from the build flags you remember passing. [[frank-zealot]]
-  `500 tools param requires --jinja flag`, from the ik_llama.cpp runtime that
+- **A llama.cpp endpoint is invisible to Prometheus unless `--metrics` is passed**: without it
-  then served frank-dragoon: every tool-using agent on that endpoint was broken
+  the engine answers **501 Not Implemented** on `/metrics`, so the scrape fails while `/health`
-  and the failure read like a model fault. Mainline llama.cpp 0.4.1 defaults
+  answers 200 and `LlmEndpointDown` fires beside a healthy service. halogen serves `/metrics`
-  `--jinja` on and the serve script pins it; halogen also accepts `tools` and
+  natively, so the asymmetry reads as "only the 3090 is broken". Diagnose with `lastError` from
-  returns `tool_calls`. Check tool support before routing a role at an endpoint.
+  `/api/v1/targets`, not the alert list, and note Alertmanager has no persistence: a reboot
-- **Quantized KV on CUDA needs `GGML_CUDA_FA_ALL_QUANTS=ON`** — the same
+  re-stamps `startsAt` on an alert that has fired for weeks. [[Observability]] [[frank-zealot]]
-  option and the same ~12x prefill collapse described in the ROCm note above.
+- **A leftover bench drop-in silently hijacks the next deploy, and no health gate sees it.** The
-  f16 KV needs nothing; frank-zealot ran f16 for that reason until
+  sanctioned bench-window method (a transient `Environment=FRANK_<SVC>_ENV_FILE=/tmp/<arm>.env`
-  2026-09-17, when `build-cuda` was rebuilt with the option ON so the
+  drop-in sourcing the repo env) outlives the bench unless retired: a leftover
-  endpoint could take q8_0 KV.
+  `frank-zealot.service.d/ptq1.conf` made the cutover deploy boot a **different model at a
-- **llama-bench separates a LIST with `/` and SWEEP values with `,`.** Both
+  different shape** while `/health` answered 200, `/v1/models` echoed the alias (a flag, not a
-  `-dev` and `-ts` follow this: `-dev CUDA0,Vulkan1` is two *single-device*
+  fact) and the Playwright gate passed 33/33. After deploying any recently-benched LLM service:
-  configurations, never one two-device run, and `-ts 0.85,0.15` is two sweep
+  `systemctl show <svc> -p DropInPaths` (must be empty), then
-  values each becoming `[0.85, 0, …]` / `[0.15, 0, …]`, i.e. device 0 takes
+  `tr '\0' ' ' </proc/$(pidof llama-server)/cmdline`, then the boot ledger — and retire drop-ins
-  everything. Write `-dev A/B -ts x/y`. This artifact produced a wrong fleet
+  to `~/.AGENTTRASH/<date>-<topic>/` + `daemon-reload`. [[frank-zealot]]
-  conclusion on 2026-09-16 — "CUDA + Vulkan cannot serve one model", with two
+- **A bench verdict that never reaches the repo is indistinguishable from a rogue arm.** That
-  bogus OOMs that were really "all 111 GiB on the 24 GiB card" — and the bench
+  same arm served production for 24 minutes with real numbers (~48 t/s decode, 801 t/s prefill at
-  table's own `dev` column was printing the truth the whole time. Any
+  141k) that lived only in `/tmp` env files and journald, so the next agent read the surviving
-  placement-dependent number needs an independent check: sample the other
+  drop-in as an unfinished experiment and reported a hijack. Write the measurement into the
+  endpoint page and the arm script's header in the session that takes it — `/tmp` and the journal
+  are not records.
+- **`llama-bench` separates a LIST with `/` and SWEEP values with `,`** — for both `-dev` and
+  `-ts`. `-dev CUDA0,Vulkan1` is two *single-device* configurations, never one two-device run,
+  and `-ts 0.85,0.15` is two sweep values each putting everything on device 0. Write
+  `-dev A/B -ts x/y`. This artifact produced a wrong fleet conclusion ("CUDA + Vulkan cannot serve
+  one model") from two bogus OOMs, and the bench table's own `dev` column was printing the truth
+  the whole time. Any placement-dependent number needs an independent check: sample the other
   device's memory (`nvidia-smi`) while the run is loaded.
-- **A model's own template can REJECT the harness's thinking level.** Qwen3.8's
-  template accepts only `xhigh`, `medium` and `low` for `reasoning_effort` and
-  raises on anything else — HTTP 500, not a clamp — so the harness's levels
-  must be folded onto that set in `models.yml` (`compat.reasoningEffortMap`).
-  A role whose level is unmapped fails on its FIRST request, and the failure
-  names Jinja, not the model: every subagent on `frank-zealot` died with
-  `Unexpected reasoning effort high` until `high: xhigh` was added on
-  2026-09-16. Halogen accepts the wider set, so the two entries legitimately
-  differ.
-- **The vision projector is NOT billed in llama.cpp's own fit check.** The
-  engine prints `[mtmd] estimated worst-case memory usage of mmproj is
-  873.10 MiB` and then fits WITHOUT it: frank-zealot's Bonsai-2 boot projected
-  21,439 MiB and settled at 22,664 (2026-10-17). Price a 3090-class shape from
-  settled `nvidia-smi` after a real boot, never from
-  `model + context + compute` — the projector (and any drafter context) lands
-  after `/health` would already have answered. Same failure class as the
-  DSpark drafter OOM.
-- **The FIRST request after a boot is a warmup artifact.** Measured on
-  Bonsai-2/3090: 2.6 t/s prefill and 37.7 t/s decode on request #1, then
-  1,258 t/s prefill and 54.7 t/s (per stream, two concurrent) on the next — a
-  3× spread on the same shape. Benchmark the second request or later, or the
-  graph-capture cost reads as a model fault.
-- **Thinking tokens count against `max_tokens`, so a short-budget vision probe
-  reads as blindness.** The Bonsai-2/`image_url` probe at `max_tokens: 64`
-  returned `content: ""` with `finish_reason: "length"` and half a thought in
-  `reasoning_content` — the image HAD reached the model (322 prompt tokens vs
-  42 for the text alone). At 512 tokens the same image answers "Red". Budget
-  ≥512 for any thinking model you probe for vision.
-- **Quantized KV is not the only dtype law a fork build can hide.** Vendor
-  builds carry their own compile options: frank-zealot's PrismML prebuilt
-  served `--cache-type-v q8_0` under flash attention at the exact 34,816
-  B/token (the `GGML_CUDA_FA_ALL_QUANTS` door), so a build decision must be
-  proven by the KV buffer line in the boot ledger, not by the build flags you
-  remember passing.
-- **A llama.cpp endpoint is invisible to Prometheus unless `--metrics` is passed.**
-  Without it the engine answers **501 Not Implemented** on `/metrics`, so the scrape
-  fails while `/health` answers 200 and `LlmEndpointDown` fires beside a healthy
-  service — that is how `frank-zealot` sat red across four payload generations
-  (the oldest retained sample of `up{job="frank-zealot"}`, 2026-10-11, is already
-  0). halogen serves `/metrics` natively, so the asymmetry reads as "only the 3090
-  is broken". Diagnose with `lastError` from `/api/v1/targets`, not the alert list,
-  and note Alertmanager has no persistence: a reboot re-stamps `startsAt` on an
-  alert that has been firing for weeks.
-- **A leftover bench drop-in silently hijacks the next deploy, and no health
-  gate sees it.** The sanctioned bench-window method — a transient
-  `Environment=FRANK_<SVC>_ENV_FILE=/tmp/<arm>.env` drop-in, the arm env
-  `source`ing the repo env and then overriding it — outlives the bench unless
-  it is retired. On 2026-10-18 a leftover `frank-zealot.service.d/ptq1.conf` —
-  the arm Frank had ordered at 02:36 and measured from 03:14 — made the cutover
-  deploy boot a **different model at a different shape** (3 slots of 133,888,
-  not 3 × 262,144) while `/health` answered 200, `/v1/models` echoed the alias
-  (a flag, not a fact) and the Playwright gate passed 33/33. After deploying any
-  recently-benched LLM service: `systemctl show <svc> -p DropInPaths` (must be
-  empty), then `tr '\0' ' ' </proc/$(pidof llama-server)/cmdline`, then the boot
-  ledger — and retire drop-ins to `~/.AGENTTRASH/<date>-<topic>/` +
-  `daemon-reload`.
-- **A bench verdict that never reaches the repo is indistinguishable from a
-  rogue arm.** Same window: PTQ1_0 served production for 24 minutes with real
-  numbers (~48 t/s decode, 801 t/s prefill at 141k), but the figures lived only
-  in `/tmp` env files and journald, so the next agent on the host read the
-  surviving drop-in as an unfinished experiment and reported a hijack. Write the
-  measurement into the runbook and the arm script's header in the session that
-  takes it — `/tmp` and the journal are not records.
 
 **Ops**
 
-- Never `pkill -f` a pattern that appears in your own command line — it kills
+- Never `pkill -f` a pattern that appears in your own command line — it kills your ssh session.
-  your ssh session. Use `pkill -x <exact-name>`.
+  Use `pkill -x <exact-name>`.
-- Both hosts allow passwordless sudo for the deploy user. Use plain `sudo` in
+- Both hosts allow passwordless sudo for the deploy user. Use plain `sudo` in committed scripts
-  committed scripts (no `echo pw | sudo -S`); `FRANK_SUDO_PW` covers hosts
+  (no `echo pw | sudo -S`); `FRANK_SUDO_PW` covers hosts without it.
-  without it.
+- **ComfyUI on Dankclaw runs with GPU access** (`/dev/kfd` + `/dev/dri` via `AddDevice`,
-- ComfyUI on Dankclaw runs with **GPU access** (`/dev/kfd` + `/dev/dri` via
+  `GroupAdd=keep-groups`, plus the udev rule that makes those nodes world-writable — user-unit
-  `AddDevice`, `GroupAdd=keep-groups`, plus the udev rule that makes those nodes
+  spawns carry no supplementary groups) and must NOT pass `--cpu`: the gfx1151 ROCm wheels exist
-  world-writable — user-unit spawns carry no supplementary groups). It must NOT
+  and a stale device-less container was found restarted 9,146 times. [[ComfyUI]]
-  pass `--cpu`: the gfx1151 ROCm wheels exist and the unit's `--cpu` era ended
+- SearXNG outbound traffic must stay on the Gluetun tunnel; do not move its ports off the gluetun
-  2026-09-16, when a stale device-less container was found restarted 9,146
+  service. [[SearXNG]] [[Gluetun]]
-  times (`RuntimeError: No HIP GPUs are available`).
+- **Dankclaw's kernel command line is a repo file.** It boots **`iommu=pt`** since 2026-10-18,
-- SearXNG outbound traffic must stay on the Gluetun tunnel; do not move its
+  tracked in `dankclaw/host/grub`, and moves ONLY through `scripts/set-dankclaw-bootline.sh`
-  ports off the gluetun service.
+  (diff, install, `update-grub`, verify `grub.cfg`, `--reboot`) — never by hand-editing
-- Dankclaw boots **`iommu=pt`** since 2026-10-18. The boot line is tracked in
+  `/etc/default/grub`. It replaced `amd_iommu=off`, and the local A/B on byte-identical traffic
-  `dankclaw/host/grub` and moves ONLY through `scripts/set-dankclaw-bootline.sh`
+  says identity mode costs nothing, so the XDNA2 NPU returned for free.
-  (diff, install, `update-grub`, verify `grub.cfg`, `--reboot`) — never by
+  [[dankclaw-iommu-translation-off]]
-  hand-editing `/etc/default/grub`. It replaced `amd_iommu=off` (2026-09-11),
+- **Rootless Quadlet containers run with `--replace --rm`**: `podman logs` covers only the CURRENT
-  adopted on the vendor's 13–16 % prefill figure and never measured here: the
+  instance; history across recreations lives in `journalctl --user -u <name>.service`. Read
-  local A/B on byte-identical traffic says identity mode costs **nothing**
+  rootless storage WITHOUT sudo — it is per-user storage, so `sudo podman logs` finds nothing.
-  (+2.0 %, 1,616 t/s cold prefill), so the XDNA2 NPU returned for free —
+  [[Quadlet Lifecycle]]
-  `amdxdna` binds `c6:00.1` (PASID width 10, identity group 26) and the old
+- **A dead rootless podman pause process breaks ALL container management on the host, and
-  `err=-19` only ever asked for an enabled IOMMU. **AMD PerfOpt** (iommu tree
+  `podman system migrate` panics in 5.7.0.** Every `podman` command fails with
-  2026-09-24, Linux 7.4) still skips the page walk outright for the privileged
+  `invalid internal status`, every start fails binding the bridges
-  iGPU, but it arms only in the identity domain and 26.04 caps at `7.0.0-38`.
+  (`failed to bind udp listener on 10.89.x.1:53`), every `Restart=always` quadlet loops — while
-- Rootless Quadlet containers run with `--replace --rm`: `podman logs` covers
+  container storage stays intact. What is gone is `/run/user/<uid>/libpod/tmp/alive` (a UUID
-  only the CURRENT instance; history across recreations lives in
+  token) and the rootless netns; deleting the stale token is not enough. Repair: **reboot**
-  `journalctl --user -u <name>.service`. Read rootless storage WITHOUT sudo
+  (`/run/user` clears and the quadlets return on their own — check `Linger=yes` and
-  (per-user storage — `sudo podman logs` finds nothing).
+  `WantedBy=default.target` first). The 2026-09-16 occurrence had no OOM in `journalctl -k`:
-- **A dead rootless podman pause process breaks ALL container management on the
+  treat the pause process as host state that can die for its own reasons. [[Quadlet Lifecycle]]
-  host, and `podman system migrate` panics in 5.7.0.** Symptoms: every `podman`
+- **A container cannot reach a `Network=host` service at the host's LAN IP**: netavark DNATs
-  command fails with `invalid internal status … could not find any running
+  *published* ports only, so the host bind and the `10.89.1.1` gateway are both refused from a
-  process`, every container start fails binding podman's bridge addresses
+  bridge container while the published port answers. Use `host.containers.internal`
-  (`Error starting server failed to bind udp listener on 10.89.x.1:53: Cannot
+  (169.254.1.2). This 502'd `hermes.franksdank.cloud` until its Caddyfile upstream changed.
-  assign requested address`), and every `Restart=always` quadlet loops. Container
+  [[Container Host Reachability]]
-  storage is intact; what is gone is `/run/user/<uid>/libpod/tmp/alive` (a UUID
+- **A `*.gguf` filter misses mradermacher's payloads: large quants ship as `.partNofM`
-  token, not a pid) and the rootless netns holding the bridges — deleting the
+  fragments** while the smaller rungs are single files, so filtering `endswith(".gguf")` makes a
-  stale token is not enough, and `podman system migrate` segfaults in
+  whole quant class look absent. Fetch the parts, verify each against the Hub's LFS sha256,
-  `teardownNetworkBackend`. Repair: **reboot** (`/run/user` clears and all 28
+  concatenate in numeric order. [[Model Swap and Rollback]]
-  quadlets return on their own — check `Linger=yes` and `WantedBy=default.target`
+- **A fetch script must `-f` and verify, or it reports success on an access error.**
-  first). Seen 2026-09-16, hours into heavy GPU work on the same host — but the
+  `curl -o FILE URL` exits 0 on HTTP 401/403 and writes the error body as the "artifact": a gated
-  trigger is NOT established (`journalctl -k` recorded no OOM kill; the kernel
+  repo yielded three 153-byte shards with identical sha256 and a cheerful `DOWNLOAD_DONE` in 20
-  had no other word on it). Treat the pause process as host state that can die
+  seconds for 104 GiB. Use `-f`/`--fail-with-body`, compare each file's byte count to the Hub's
-  for its own reasons, and reach for the reboot when it does.
+  declared size, and check the LFS sha256 (`scripts/download-frank-medium-gguf.sh` does all three;
-- **A container cannot reach a `Network=host` service at the host's LAN IP.**
+  ad-hoc fetches tend not to). Gated repos 403 even with the host's HF token until that account
-  netavark DNATs *published* ports only: from a bridge container
+  accepts the gate. [[Model Swap and Rollback]]
-  `192.168.0.143:<published>` answers while `192.168.0.143:<host bind>` and the
+- **A scout verdict is a lead, never a finding.** In the 2026-10-19 vault de-dup campaign six
-  gateway `10.89.1.1` are both refused. Use `host.containers.internal`
+  read-only scouts worked the same pages: one classified era pages as stale *because* they
-  (169.254.1.2). This is what 502'd `hermes.franksdank.cloud` until the Caddyfile
+  document retired payloads (that is an era page's content), one reported files that do not exist,
-  upstream was changed on 2026-09-16 (its vhost comment had claimed the LAN IP
+  one reported duplications that grep disproved (`457.9 t/s` and the ping-RTT table are solo-held
-  was open from that bridge — it never was).
+  by `Ethernet Bandwidth Math`), one cited a line number past the end of the file it judged, and
-- **A `*.gguf` filter misses mradermacher's payloads: large quants ship as
+  one drafted an Eras table with invented windows, payloads and rollback paths. Re-verify every
-  `.partNofM` fragments.** `mradermacher/Qwen3.8-Flash-Next-Uncensored-i1-GGUF`
+  claimed duplicate, every claimed staleness and every quoted holder against the file and today's
-  carries Q4_K_M (37.00 + 37.00 + 36.97 = 110.97 GiB) and Q4_K_S (35.00 + 35.00
+  fleet state before editing; a scout yield buys no evidence.
-  + 34.09 = 104.09 GiB) as parts, while the smaller rungs (Q2_K, Q3_K_*, IQ3_*,
-  IQ4_XS) are single files. Fetch the parts, verify each against the Hub's LFS
-  sha256, concatenate in numeric order — that is how the deployed 111 GiB file
-  was assembled. Listing the Hub tree and filtering `endswith(".gguf")` makes
-  Q4_K_S look like it does not exist.
-- **A fetch script must `-f` and verify, or it reports success on an access
-  error.** `curl -o FILE URL` exits 0 on HTTP 401/403 and writes the error body
-  as the "artifact": a gated repo yielded three 153-byte shards with identical
-  sha256 values and a cheerful `DOWNLOAD_DONE` in 20 seconds for 104 GiB. Use
-  `-f`/`--fail-with-body`, compare each file's byte count to the Hub's declared
-  size, and check the LFS sha256 — `scripts/download-frank-medium-gguf.sh`
-  already does all three; ad-hoc fetches tend not to. Gated repos (e.g.
-  `orcarouter/Qwen3.8-Flash-Next-Uncensored-GGUF`, same 104.09 GiB Q4_K_S)
-  return 403 even with the host's HF token until that account accepts the gate.
 
 ## Runbook Index
 

scripts/check-okf.py

@@ -0,0 +1,293 @@
+#!/usr/bin/env python3
+"""OKF v0.1 conformance linter for a docs bundle (default serverAppConfigs-docs).
+
+Checks the hard rules of the Open Knowledge Format spec plus the maintenance
+guidance, so "conforms to OKF" is a test and not a claim:
+
+  FRONTMATTER  every non-reserved .md has parseable YAML frontmatter with a
+               non-empty `type` from the spec's value set
+  TYPE         the value is one of reference / howto / tutorial / explanation
+  DESC         `description` is present, non-blank, not the title, <= 120 chars,
+               and does not restate a fleet quantity
+  TIMESTAMP    `timestamp` present, ISO 8601, not in the future
+  LENGTH       lines between 1 and 500 inclusive
+  INDEX-FM     no index.md may carry frontmatter (index.md is reserved)
+  LOG-DATE     log.md date headings are `## YYYY-MM-DD` or `## YYYY-MM-DD — Title`,
+               one entry per date, newest first
+  INDEX-COVER  every index.md links each of its sibling pages; the root index
+               links every page in the bundle
+  INDEX-NUM    an index table row restates a fleet quantity — a digit run of
+               three or more, a digits-plus-unit figure, a port, or a
+               multiplier. Names (Qwen3.6, RDNA4, RTX 3090, PICO-8, P4) are
+               not quantities and are allowed
+  CITATIONS    informational: pages with factual claims and no Citations
+               section are counted, never failed
+
+  LENGTH       lines between 1 and 500 inclusive. A page may opt out of the
+               ceiling with `okf-exempt: length` in its frontmatter: AGENTS.md
+               makes one page per endpoint permanent, and an endpoint page with
+               a full Eras table cannot split without creating a second owner
+               of the same shape (tests/docs_completeness.bats enforces that)
+
+Exit 0 when there are no violations.
+"""
+import datetime
+import re
+import sys
+from pathlib import Path
+
+TYPES = {"reference", "howto", "tutorial", "explanation"}
+RESERVED = {"index.md", "log.md", "AGENTS.md"}
+
+# A quantity, as opposed to a name: a comma-grouped figure, a run of 3+ digits,
+# a unit-bearing figure, a port (":7770"), or a multiplier ("2x", "3 *").
+QUANTITY = re.compile(
+    r"\d{1,3}(?:,\d{3})+"          # 262,144
+    r"|\d{3,}"                     # 200000, 7770, 3090
+    r"|\d+(?:\.\d+)?\s*(?:GiB|MiB|GB|MB|TB|tok/s|t/s|x\b|%)"
+    r"|[:×]\s*\d"
+    r"|\d+\s*[x×]\s*\d"
+)
+# Product / model / standard names that legitimately contain digits.
+NAMES = re.compile(
+    r"Qwen[\d.]*[-\w]*|Gemma\s?\d[\w.]*|MiMo[-\w.\d.]*|Ornith[-\w.\d]*"
+    r"|Bonsai[-\w.\d]*|Ling[-\w.\d.]*|DeepSeek[-\w.\d]*|GLM[-\w.\d]*"
+    r"|PICO-\d+|RDNA\s?\d+|R\d{4}|RTX\s?\d+|XDNA\d|gfx\d+|CUDA\s?[\d.]+"
+    r"|\d+\s?GbE|Wi-?Fi\s?\d|v?\d+\.\d+(?:\.\d+)?|b\d+|P\d\b|A\d+\b"
+    r"|frank-\w*2026-\d\d-\d\d|2026-\d\d-\d\d",
+    re.I,
+)
+DATE_RE = re.compile(r"^\d{4}-\d{2}-\d{2}")
+FM_KEY = re.compile(r"^([A-Za-z][\w-]*):\s*(.*)$")
+
+
+def split_frontmatter(text):
+    if not text.startswith("---"):
+        return None, text
+    end = text.find("\n---", 3)
+    if end < 0:
+        return None, text
+    body_start = text.find("\n", end + 1)
+    return text[3:end], text[body_start + 1 :] if body_start >= 0 else ""
+
+
+def fields(raw):
+    out = {}
+    if not raw:
+        return out
+    key = None
+    for line in raw.splitlines():
+        if not line.strip():
+            continue
+        m = FM_KEY.match(line)
+        if m:
+            key, val = m.group(1), m.group(2).strip().strip("\"'")
+            out[key] = val
+        elif line.startswith(" ") and key:
+            out[key] = (out[key] + " " + line.strip()).strip()
+    return out
+
+
+def strip_names(value):
+    return NAMES.sub(" ", value)
+
+
+def check_file(path: Path, root: Path, length_exempt=frozenset()):
+    v = []
+    rel = str(path.relative_to(root))
+    text = path.read_text(errors="replace")
+    lines = text.splitlines()
+    name = path.name
+    raw, body = split_frontmatter(text)
+    fm = fields(raw)
+
+    if name not in RESERVED:
+        if raw is None:
+            v.append(("FRONTMATTER", rel, "no parseable frontmatter"))
+        else:
+            t = fm.get("type", "")
+            if not t:
+                v.append(("TYPE", rel, "missing type"))
+            elif t not in TYPES:
+                v.append(("TYPE", rel, f"type '{t}' not in {sorted(TYPES)}"))
+            d = fm.get("description", "")
+            if not d:
+                v.append(("DESC", rel, "missing description"))
+            else:
+                if len(d) > 120:
+                    v.append(("DESC", rel, f"description is {len(d)} chars (max 120)"))
+                if d.strip("# ").lower() == fm.get("title", "\0").strip("# ").lower():
+                    v.append(("DESC", rel, "description equals title"))
+                if QUANTITY.search(strip_names(d)):
+                    v.append(("DESC", rel, "description restates a quantity"))
+            ts = fm.get("timestamp", "")
+            if not ts:
+                v.append(("TIMESTAMP", rel, "missing timestamp"))
+            else:
+                try:
+                    stamp = datetime.date.fromisoformat(ts[:10])
+                    if stamp > datetime.date.today():
+                        v.append(("TIMESTAMP", rel, f"timestamp {ts} is in the future"))
+                except ValueError:
+                    v.append(("TIMESTAMP", rel, f"unparseable timestamp {ts!r}"))
+
+    if name == "index.md" and raw is not None:
+        v.append(("INDEX-FM", rel, "index.md must not carry frontmatter"))
+
+    if name == "log.md":
+        dates = []
+        for line in lines:
+            m = re.match(r"^##\s+(\S.*?)\s*$", line)
+            if not m:
+                continue
+            head = m.group(1)
+            if not DATE_RE.match(head):
+                continue
+            dates.append(head[:10])
+            # OKF requires the heading to USE the date format; a title after an
+            # em-dash is allowed and costs zero lines, so `## 2026-08-17 — Why the
+            # pair was rebuilt` is conformant and `## 2026-08-17Rebuilt` is not.
+            if head != head[:10] and not re.match(r"^\d{4}-\d{2}-\d{2}\s+—\s+\S", head):
+                v.append(("LOG-DATE", rel,
+                          f"date heading must be the date alone or `date — Title`: '## {head}'"))
+        if len(dates) != len(set(dates)):
+            v.append(("LOG-DATE", rel, "duplicate date heading"))
+        if dates != sorted(dates, reverse=True):
+            v.append(("LOG-DATE", rel, "date headings not newest first"))
+
+    if raw is not None and name not in RESERVED:
+        n = len(lines)
+        body_lines = len([ln for ln in body.splitlines() if ln.strip()])
+        opted_out = "length" in fm.get("okf-exempt", "").lower()
+        if n > 500:
+            if rel in length_exempt:
+                v.append(("LENGTH-OK", rel,
+                          f"{n} lines — over the hint, pinned by the "
+                          "one-page-per-endpoint law"))
+            elif opted_out:
+                v.append(("LENGTH-OK", rel,
+                          f"{n} lines — over the hint, opted out by the page"))
+            else:
+                v.append(("LENGTH", rel, f"{n} lines (max 500)"))
+        elif body_lines < 15:
+            v.append(("LENGTH", rel, "stub: fewer than 15 body lines"))
+
+    # A second `type:` key inside the body means the page carries two copies of
+    # itself with a frontmatter block in the middle — the shape a naive
+    # frontmatter rewrite produces. It doubles the length, splits the wikilinks
+    # and makes the page's facts ambiguous, so it is a hard failure.
+    if raw is not None and name not in RESERVED:
+        dupes = [i + len((raw or "").splitlines()) + 2
+                 for i, ln in enumerate(body.splitlines())
+                 if re.match(r"^(type|title|description):", ln)]
+        if dupes:
+            v.append(("DOUBLED", rel,
+                      f"frontmatter keys inside the body at line(s) "
+                      f"{', '.join(str(d) for d in dupes[:5])} — the page "
+                      "contains a duplicated copy of itself"))
+
+    return v
+
+
+def index_rows(text):
+    rows = []
+    for line in text.splitlines():
+        if line.startswith("|") and "[[" in line:
+            rows.append(line)
+    return rows
+
+
+def check_links(root: Path):
+    v = []
+    pages = [
+        p for p in sorted(root.rglob("*.md"))
+        if ".AGENTTRASH" not in str(p) and ".obsidian" not in str(p)
+    ]
+    for index in [p for p in pages if p.name == "index.md"]:
+        text = index.read_text(errors="replace")
+        links = set(re.findall(r"\[\[([^\]|#]+)", text))
+        if index.parent == root:
+            targets = [p for p in pages if p.name not in RESERVED]
+        else:
+            targets = [p for p in index.parent.glob("*.md") if p.name != "index.md"]
+        for target in targets:
+            if target.stem not in links and target.name not in links:
+                v.append(("INDEX-COVER", str(index.relative_to(root)),
+                          f"does not link sibling {target.name}"))
+    for index in [p for p in pages if p.name == "index.md"]:
+        for row in index_rows(index.read_text(errors="replace")):
+            if QUANTITY.search(strip_names(row)):
+                v.append(("INDEX-NUM", str(index.relative_to(root)),
+                          "row restates a quantity: " + row[:80]))
+    return v
+
+
+def live_endpoints(root: Path):
+    """Pages pinned by AGENTS.md's one-page-per-endpoint law.
+
+    Derived, never hardcoded — the same derivation as
+    tests/docs_completeness.bats: an endpoint is live when scripts/ holds both
+    its env and its unit. Those pages carry the Eras table for their whole
+    history, so the OKF 500-line split hint cannot apply to them without
+    creating a second owner of the same shape.
+    """
+    scripts = root.parent / "scripts"
+    out = set()
+    if scripts.is_dir():
+        for envf in scripts.glob("frank-*.env"):
+            if (scripts / f"{envf.stem}.service").exists():
+                out.add(f"LLM/{envf.stem}.md")
+    return out
+
+
+def retired_era_pages(root: Path):
+    """Era pages of a retired endpoint: campaign ledgers, one owner each.
+
+    AGENTS.md lets a campaign ledger that exists nowhere else live on the page
+    that measured it, and a retired endpoint keeps exactly one page per era.
+    Splitting such a ledger to satisfy the 500-line hint would fragment one
+    campaign across two owners, so the tag opts the page out.
+    """
+    out = set()
+    for path in root.rglob("*.md"):
+        s = str(path)
+        if ".AGENTTRASH" in s or ".obsidian" in s:
+            continue
+        raw, _ = split_frontmatter(path.read_text(errors="replace"))
+        if raw is not None and "retired-endpoint" in fields(raw).get("tags", ""):
+            out.add(str(path.relative_to(root)))
+    return out
+
+
+def main(argv):
+    root = Path(argv[1] if len(argv) > 1 else "serverAppConfigs-docs")
+    exempt = frozenset(live_endpoints(root)) | retired_era_pages(root)
+    violations = []
+    notes = []
+    citation_gaps = 0
+    pages = 0
+    for path in sorted(root.rglob("*.md")):
+        s = str(path)
+        if ".AGENTTRASH" in s or ".obsidian" in s:
+            continue
+        pages += 1
+        for code, rel, detail in check_file(path, root, exempt):
+            (notes if code == "LENGTH-OK" else violations).append((code, rel, detail))
+        text = path.read_text(errors="replace")
+        if len(text.splitlines()) > 40 and not re.search(
+                r"^##\s+(Citations|Sources)\b", text, re.M):
+            citation_gaps += 1
+    violations += check_links(root)
+
+    for code, rel, detail in violations:
+        print(f"  {code:12s} {rel}: {detail}")
+    for code, rel, detail in notes:
+        print(f"  {code:12s} {rel}: {detail}")
+    print(f"{pages} concept pages, {len(violations)} OKF violations"
+          f" ({citation_gaps} pages without a Citations section — soft;"
+          f" {len(notes)} length exemptions honoured)")
+    return 1 if violations else 0
+
+
+if __name__ == "__main__":
+    sys.exit(main(sys.argv))

scripts/check-vault-links.py

@@ -31,7 +31,12 @@ def strip_md(path: str) -> str:
 
 
 def build_index(vault: pathlib.Path):
-    pages = sorted(vault.rglob("*.md"))
+    # `.AGENTTRASH` is deleted-but-held state, not vault content: it must not be
+    # scanned (its relative links resolve against the trash dir, not the vault)
+    # and must not answer as a link target — a live page pointing into the trash
+    # is an unresolved link, not a resolved one.
+    pages = sorted(p for p in vault.rglob("*.md")
+                   if ".AGENTTRASH" not in str(p))
     stems: dict[str, list[pathlib.Path]] = {}
     for page in pages:
         stems.setdefault(page.stem.casefold(), []).append(page)

scripts/deploy-remote.sh

@@ -1459,7 +1459,7 @@ LLM_ZEALOT_RUNTIME="${LLM_ZEALOT_RUNTIME:-/home/dank/GitPackages/llama-prism-b10
 # image path — a deploy that starts without it silently ships a text-only
 # endpoint. Checked unconditionally, like frank-dragoon's. Q8_0 is MANDATORY,
 # not a preference: the card says the BF16 tower can crash llama-server when
-# several image requests run at once, and this endpoint runs --parallel 2. Its
+# several image requests run at once, and this endpoint runs --parallel 3. Its
 # 868.32 MiB worst-case VRAM (595.29 model + 248.10 compute in the boot ledger)
 # lands AFTER the engine's fit check, so it is not inside the q8_0 budget.
 LLM_ZEALOT_MMPROJ="${LLM_ZEALOT_MMPROJ:-/home/dank/models/Bonsai2-9B-MTP/Ternary-Bonsai-2-9B-mmproj-Q8_0.gguf}"

scripts/frank-zealot.env

@@ -11,35 +11,51 @@ LLAMA_BIN=/home/dank/GitPackages/llama-prism-b10777/llama-server
 # metadata dequantizes wrong, silently.
 MODEL_FILE=/home/dank/models/Bonsai2-9B-MTP/Ternary-Bonsai-2-9B-PQ2_0-MTP-Q8_0.gguf
 # Q8_0 IS MANDATORY: the publisher states the BF16 tower can crash llama-server
-# under concurrent image requests, which is exactly --parallel 2.
+# under concurrent image requests, which is exactly --parallel 3.
 MMPROJ_FILE=/home/dank/models/Bonsai2-9B-MTP/Ternary-Bonsai-2-9B-mmproj-Q8_0.gguf
 # Served id — the harness/family name, not a fact about the payload.
 # Id-keyed consumers: OpenWebUI (model row, access_grant, api_configs), models.yml.
 ALIAS=frank-zealot
 BIND_ADDR=0.0.0.0
 LISTEN_PORT=7771
-# CTX_SIZE is the POOL llama.cpp divides across slots: 524,288 / 2 = 262,144 a
+# CTX_SIZE is the POOL llama.cpp divides across slots: 602,112 / 3 = 200,704 a
-# conversation, each still at the trained window. MUST stay divisible by
+# conversation. MUST stay divisible by PARALLEL (the seam enforces it) and
-# PARALLEL (the seam enforces it) and models.yml contextWindow quotes the
+# models.yml contextWindow quotes the PER-SLOT number — a longer prompt is a
-# PER-SLOT number — a longer prompt is a 400, never a truncation. The pool
+# 400, never a truncation. The pool is bought, not granted: K+V at 25,088
-# cannot go back to 786,432 under exact f16 KV: 24,576 MiB of cache against the
+# B/token is 14,406.00 MiB here and the MTP draft context bills its own f16 KV
-# 24,123 MiB the driver leaves addressable, before a weight loads.
+# over the WHOLE pool (4,096 B/position ⇒ 2,352.00 MiB), so the old 786,432
-CTX_SIZE=524288
+# pool cannot carry a drafter at any KV dtype — 18,816 + 3,072 of cache alone
-PARALLEL=2
+# against the 24,123 MiB the driver leaves addressable.
-BATCH_SIZE=4096
+CTX_SIZE=602112
+PARALLEL=3
+# The logical batch is VRAM- and throughput-neutral at a fixed ubatch (the law
+# on [[frank-zealot]]); 1024×6 keeps it a clean multiple of the ubatch.
+BATCH_SIZE=6144
 # Ubatch is a prefill knob (decode never moves with it) and it sets the
-# compute-buffer size — which is what decides whether a drafter fits.
+# compute-buffer size, which decides whether a drafter fits. 1024 is the rung
-# UBATCH_SIZE=1024 is the documented MTP arm.
+# every measured MTP arm here ran on (213.5 t/s against 109.2 at 2048). Its
-UBATCH_SIZE=2048
+# VRAM credit is SHAPE-specific: the 786,432-pool arm census showed ~1,306 MiB
-# Exact K and V: the retrieval-fidelity ask, paid with one conversation of
+# back, this boot measured 2,089.88 MiB of target compute against 2,496.13 at
-# concurrency. Rate law and the arithmetic: [[frank-zealot]] → Laws.
+# ubatch 2048 — 406 MiB back, with the split moving (CUDA0 +257, CUDA_Host
+# −663). The drafter is funded by CACHE_TYPE_V below, not by this knob.
+UBATCH_SIZE=1024
+# K exact, V in the 8-bit class: 16,384 + 8,704 = 25,088 B/token (8,192
+# elements per token per cache × 2 B for f16, × 1.0625 for q8_0 — there is no
+# true fp8 KV dtype in this build). That 7,680 B/token saved against exact V is
+# what funds BOTH the third conversation and the drafter. Quantized V is
+# illegal without --flash-attn, which the serve script pins. Rate law and the
+# arithmetic: [[frank-zealot]] → Laws.
 CACHE_TYPE_K=f16
-CACHE_TYPE_V=f16
+CACHE_TYPE_V=q8_0
-# Speculation OFF — measured, not assumed: the draft context bills its own f16
+# Speculation ON (Frank, 2026-10-19): the head is in the file
-# KV over the WHOLE pool, and there is no room beside exact KV (the arm census
+# (qwen35.nextn_predict_layers = 1, blk.32.nextn.*) and rides the MAIN model's
-# is on the page). SPEC_TYPE=none strips the WHOLE set (--spec-type and every
+# weights, so there is no --spec-draft-model. Its bill is pool × 4,096 B of
-# --spec-draft-*); half a set has segfaulted at load.
+# draft KV plus ~0.45 GiB of buffers and a tripled recurrent state — paid for
-SPEC_TYPE=none
+# by CACHE_TYPE_V=q8_0 and UBATCH_SIZE=1024 above. Build gate: quantized V
+# beside MTP needs fork build >= b10776; LLAMA_BIN is 10777.
+# SPEC_TYPE=none is the rollback and strips the WHOLE set (--spec-type and
+# every --spec-draft-*); half a set has segfaulted at load.
+SPEC_TYPE=draft-mtp
 SPEC_DRAFT_N_MAX=2
 SPEC_DRAFT_N_MIN=0
 SPEC_DRAFT_P_MIN=0

scripts/gen-vault-index.py

@@ -0,0 +1,206 @@
+#!/usr/bin/env python3
+"""Regenerate serverAppConfigs-docs/index.md from page frontmatter.
+
+The root index is a locator (AGENTS.md -> *Documentation Policy*): one row per
+page, one clause, no numbers. Hand-maintaining it is how rows go missing, and
+the docs seam fails when a page is not linked from it, so it is generated:
+
+  * preamble     everything above the first `## ` in the existing file is kept
+                 verbatim (that is the curated statement of the vault's law)
+  * section      from the page's directory, overridden by its frontmatter tags
+                 (`endpoint` / `retired-endpoint` split the LLM pages)
+  * row text     the page's frontmatter `description`, verbatim
+
+A page with no description is a hard error rather than an empty cell, so the
+generator cannot silently produce a silent index. Sections with no pages are
+skipped. Deterministic: the same vault always yields the same bytes.
+
+Sub-directory indices are hand-grouped (they carry curated prose), so they are
+synced rather than regenerated: dead rows dropped, row text refreshed from the
+page's description, uncovered siblings appended.
+"""
+import pathlib
+import re
+import sys
+
+RESERVED = {"index.md", "log.md"}
+SECTIONS = [
+    ("Inference endpoints", "endpoint"),
+    ("Retired endpoints", "retired-endpoint"),
+]
+DIRECTORY_SECTIONS = [
+    ("Dankclaw", "Dankclaw services"),
+    ("Dankserver", "Dankserver services"),
+    ("FrankBook-Pro", "FrankBook-Pro"),
+    ("Desktop", "Workstations"),
+    ("Infrastructure", "Cross-host infrastructure"),
+    ("Architecture", "Repo architecture and policy"),
+    ("Operations", "Operations and incidents"),
+    ("Agent", "Agent / harness"),
+    ("Research", "Research and methodology"),
+]
+PIPELINE_SECTION = "Pipeline Parallelism (series)"
+LLM_FALLBACK = "LLM technique and hardware references"
+CHANGE_SECTION = "Change history"
+ORDER = [t for t, _ in SECTIONS] + [t for _, t in DIRECTORY_SECTIONS] + \
+        [PIPELINE_SECTION, LLM_FALLBACK, CHANGE_SECTION]
+
+
+def frontmatter_fields(text):
+    if not text.startswith("---"):
+        return {}
+    end = text.find("\n---", 3)
+    if end == -1:
+        return {}
+    raw = text[3:end]
+    fields = {}
+    for key in ("description", "type"):
+        m = re.search(rf"^{key}:\s*(.*)$", raw, re.M)
+        if m:
+            fields[key] = m.group(1).strip().strip("\"'")
+    tags = []
+    m = re.search(r"^tags:\s*\[(.*?)\]$", raw, re.M)
+    if m:
+        tags = [t.strip().strip("\"'") for t in m.group(1).split(",") if t.strip()]
+    elif re.search(r"^tags:\s*$", raw, re.M):
+        block = re.search(r"^tags:\s*\n((?:\s+-\s+.*\n?)+)", raw, re.M)
+        if block:
+            tags = [l.strip().lstrip("-").strip().strip("\"'")
+                    for l in block.group(1).splitlines() if l.strip()]
+    fields["tags"] = tags
+    return fields
+
+
+def section_for(page, vault, fields):
+    rel = page.relative_to(vault)
+    if len(rel.parts) == 1:
+        return CHANGE_SECTION if page.name == "log.md" else "Uncategorised"
+    top = rel.parts[0]
+    if top == "LLM":
+        if PIPELINE_SECTION_DIR in rel.parts:
+            return PIPELINE_SECTION
+        for title, tag in SECTIONS:
+            if tag in fields.get("tags", []):
+                return title
+        return LLM_FALLBACK
+    for prefix, title in DIRECTORY_SECTIONS:
+        if top == prefix:
+            return title
+    return "Uncategorised"
+
+
+ROW = re.compile(r"^(\| )\[\[([^\]|]+)\]\]( \|)( .*?)( \|$)")
+BULLET = re.compile(r"^(- )\[\[([^\]]+)\]\]( — )(.*?)$")
+
+
+def sync_subindex(index: pathlib.Path, vault: pathlib.Path):
+    """Keep a hand-grouped sub-index honest without erasing its grouping.
+
+    Rows are locators, so their text is the linked page's own description; a
+    row whose page is gone is a dead promise and is dropped; a direct sibling
+    with no row is appended under `## Pages` (that is what the link-integrity
+    seam checks). Curated headings and prose are untouched.
+    """
+    here = index.parent
+    known = {p.stem for p in here.rglob("*.md")
+             if ".AGENTTRASH" not in str(p) and p.name != "index.md"}
+    lines = index.read_text().split("\n")
+    out, dropped, refreshed = [], 0, 0
+    for line in lines:
+        for pat, wrap in ((ROW, "| [[{}]] |{} {} |"), (BULLET, "- [[{}]] — {}")):
+            m = pat.match(line)
+            if not m:
+                continue
+            stem = m.group(2).strip()
+            if stem not in known:
+                dropped += 1
+                line = None
+                break
+            cand = next((p for p in here.rglob(f"{stem}.md")
+                         if ".AGENTTRASH" not in str(p)), None)
+            desc = frontmatter_fields(cand.read_text(errors="replace")).get("description") \
+                if cand else None
+            if desc:
+                current = m.group(4).strip()
+                if current != desc:
+                    line = wrap.format(stem, " " if pat is ROW else "", desc) \
+                        if pat is ROW else wrap.format(stem, desc)
+                    refreshed += 1
+            break
+        if line is not None:
+            out.append(line)
+    text = "\n".join(out)
+    # Presence must be the wikilink itself: a bare stem is a substring of other
+    # page names (`frank-medium` lives inside `frank-medium-rocmfpx`), and a
+    # sibling matched that way silently never gets a row.
+    missing = sorted(
+        (p.stem, frontmatter_fields(p.read_text(errors="replace")).get("description", ""))
+        for p in here.glob("*.md")
+        if p.name != "index.md" and f"[[{p.stem}]]" not in text
+    )
+    if missing:
+        block = ["", "## Pages", "", "| Page | Owns |", "|---|---|"]
+        block += [f"| [[{stem}]] | {desc} |" for stem, desc in missing]
+        text = text.rstrip("\n") + "\n" + "\n".join(block) + "\n"
+    if text != index.read_text():
+        index.write_text(text)
+    return dropped, refreshed, len(missing)
+
+
+PIPELINE_SECTION_DIR = "Pipeline Parallelism"
+
+
+def main(argv):
+    vault = pathlib.Path(argv[1] if len(argv) > 1 else "serverAppConfigs-docs")
+    index = vault / "index.md"
+    if not index.is_file():
+        print(f"missing {index}")
+        return 2
+    existing = index.read_text()
+    preamble = existing.split("\n## ", 1)[0].rstrip("\n")
+
+    pages = [p for p in vault.rglob("*.md")
+             if ".AGENTTRASH" not in str(p) and ".obsidian" not in str(p)
+             and p.name != "index.md" and p != index]
+    buckets, errors = {}, []
+    for page in pages:
+        fields = frontmatter_fields(page.read_text(errors="replace"))
+        if page.name != "log.md":
+            desc = fields.get("description")
+            if not desc:
+                errors.append(str(page.relative_to(vault)))
+                continue
+        else:
+            desc = "Chronological incident and law log for the whole bundle."
+        buckets.setdefault(section_for(page, vault, fields), []).append((page.stem, desc))
+    if errors:
+        print("pages with no description (fix the frontmatter, not the index):")
+        for e in sorted(errors):
+            print("  " + e)
+        return 1
+
+    out = [preamble, ""]
+    for title in ORDER + sorted(set(buckets) - set(ORDER)):
+        rows = sorted(buckets.get(title, []), key=lambda r: r[0].lower())
+        if not rows:
+            continue
+        out += [f"## {title}", "", "| Page | Owns |", "|---|---|"]
+        out += [f"| [[{stem}]] | {desc} |" for stem, desc in rows]
+        out.append("")
+    out.append("<!-- generated by scripts/gen-vault-index.py; edit page frontmatter instead -->")
+    index.write_text("\n".join(out) + "\n")
+    touched = 0
+    for sub in sorted(vault.rglob("index.md")):
+        if sub == index:
+            continue
+        dropped, refreshed, added = sync_subindex(sub, vault)
+        if dropped or refreshed or added:
+            touched += 1
+            print(f"  {sub}: -{dropped} dead rows, {refreshed} refreshed, +{added} added")
+    print(f"{index}: {sum(len(v) for v in buckets.values())} rows in "
+          f"{len([t for t in ORDER if buckets.get(t)])} sections, {touched} sub-indices synced")
+    return 0
+
+
+if __name__ == "__main__":
+    sys.exit(main(sys.argv))

scripts/port-census.py

@@ -0,0 +1,100 @@
+#!/usr/bin/env python3
+"""Port census: prove a merge/collapse lost no fact.
+
+For every line that existed in the OLD set and not in the NEW set, check that
+each of its significant tokens (numbers, long identifiers, paths) still occurs
+somewhere in the NEW corpus. A line whose every token survives is a reworded
+line; a line with an unheld token is a candidate fact loss and gets printed.
+
+  port-census.py <new-glob-dir> <old-file> [<old-file> ...]
+
+Old files may be `git-rev:path` (read from git) or a path (e.g. a trash copy).
+"""
+import pathlib
+import re
+import subprocess
+import sys
+
+
+def toks(line):
+    out = []
+    for n in re.findall(r"\d[\d,]*(?:\.\d+)?", line):
+        if len(n.replace(",", "").split(".")[0]) >= 3 or (
+            "." in n and len(n.split(".")[-1]) >= 2 and len(n.replace(",", "")) >= 4
+        ):
+            out.append(n)
+    # Identifiers, flags, paths and backticked spans are the facts worth
+    # tracking; ordinary prose words are not — they reword on every rewrite.
+    # A hyphen alone is not evidence of an identifier (`long-standing`), so a
+    # dashed word counts only with two hyphens (`frank-tts-engine`) or with a
+    # digit, dot, slash, colon or `--` inside it.
+    for w in re.findall(r"[A-Za-z][\w./:-]{7,}", line):
+        core = w.strip(".,;:!?\"')]")
+        if (core.startswith("--") or core.isupper()
+                or re.search(r"[\d_/:.]", core) or core.count("-") >= 2):
+            out.append(core)
+    out += [s.strip() for s in re.findall(r"`([^`]+)`", line) if len(s) > 3]
+    return out
+
+
+def held(tok, corpus):
+    t = tok.replace(",", "")
+    alt = rf"\b{re.escape(t)}\b"
+    for c in corpus:
+        if tok in c or t in c:
+            return True
+        if re.search(alt, c.replace(",", "")):
+            return True
+    return False
+
+
+def main(argv):
+    new_dir = pathlib.Path(argv[1])
+
+    def corpus_excluding(exclude):
+        """Every vault page except the one under test.
+
+        The corpus is what must still hold a fact AFTER the file is gone, so a
+        file that lives inside the scanned directory has to be removed from it —
+        otherwise every token is "held" by the file itself and the census proves
+        nothing (it reports 0 losses for every page, which is the bug this
+        guards).
+        """
+        out = []
+        for p in new_dir.rglob("*.md"):
+            s = str(p)
+            if ".AGENTTRASH" in s or ".obsidian" in s:
+                continue
+            if exclude is not None and p.resolve() == exclude:
+                continue
+            out.append(p.read_text(errors="replace"))
+        return out
+
+    lost = checked = 0
+    for spec in argv[2:]:
+        if spec.startswith("git-"):
+            ref, path = spec[4:].split(":", 1)
+            old = subprocess.run(["git", "show", f"{ref}:{path}"],
+                                 capture_output=True, text=True).stdout
+            label = f"{ref}:{path}"
+            exclude = None
+        else:
+            old = pathlib.Path(spec).read_text(errors="replace")
+            label = spec
+            exclude = pathlib.Path(spec).resolve()
+        blob = "\n".join(corpus_excluding(exclude))
+        for line in old.splitlines():
+            s = line.strip().strip("->*|# ").strip()
+            if len(s) < 30 or s.startswith("```"):
+                continue
+            checked += 1
+            missing = [t for t in toks(s) if not held(t, [blob])]
+            if missing:
+                lost += 1
+                print(f"  {label}\n    L: {s[:150]}\n    unheld: {', '.join(missing[:6])}")
+    print(f"{checked} old lines checked, {lost} with unheld tokens")
+    return 1 if lost else 0
+
+
+if __name__ == "__main__":
+    sys.exit(main(sys.argv))

scripts/serve-frank-zealot.sh

@@ -5,33 +5,45 @@
 #
 # 2026-10-18 (Frank): Bonsai-2 27B PQ2_0 → the 9B MTP export, then the same
 # evening TWO 262,144-token conversations (--ctx-size 524288 --parallel 2) over
-# an UNQUANTIZED f16 KV cache. The 9B bills 8,192 elements per token per cache
+# an UNQUANTIZED f16 KV cache.
-# (8 full-attention layers instead of the 27B's 16), so exact K and V costs
+#
-# 32,768 B/token — 16,384.00 MiB at the 524,288 pool, which is what a 24,123 MiB
+# 2026-10-19 (Frank): THREE 200,704-token conversations over a 602,112 pool
-# addressable card can carry beside the trunk. Verbosity 4 ships so the VRAM-fit
+# (--ctx-size 602112 --parallel 3), K left at the engine's own default (f16),
-# forensics (KV layout, buffer sizes, graph capture) land in the journal.
+# V dropped to q8_0, batch 1024×6 / ubatch 1024, and the MTP drafter ARMED
+# (--spec-type draft-mtp). The 9B bills 8,192 elements per token per cache (8
+# full-attention layers instead of the 27B's 16), so f16 K is 16,384 B/token and
+# q8_0 V is 8,704: 25,088 B/token = 14,406.00 MiB at the 602,112 pool. That
+# 7,680 B/token against exact V is exactly what funds the third conversation
+# AND a draft context that bills f16 KV over the whole pool. Verbosity 4 ships
+# so the VRAM-fit forensics (KV layout, buffer sizes, graph capture) land in
+# the journal.
 #
 # Architecture (engine ledger, not the marketing page): qwen35 hybrid, 32
 # layers with qwen35.full_attention_interval = 4 ⇒ 8 full-attention + 24 Gated
 # DeltaNet, 4 KV heads × 256 dim, native 262,144. The KV pool scales with the 8
-# full layers (16,384.00 MiB of f16 at the 524,288 pool); the DeltaNet layers
+# full layers (14,406.00 MiB of f16 K + q8_0 V at the 602,112 pool); the
-# cost a fixed recurrent state per SLOT — ~50.25 MiB a cell, so 100.50 MiB for
+# DeltaNet layers cost a fixed recurrent state per SLOT — ~50.25 MiB a cell, so
-# two. The runtime is a hard lock, not a preference: custom GGML type 142 plus
+# 150.75 MiB for three, and an armed depth-2 drafter triples that again. The
-# prism.hadamard.* metadata, which only the vendor build registers (the b10776
+# runtime is a hard lock, not a preference: custom GGML type 142 plus
-# gate that moved the prebuilt 10754 → 10777 was MTP beside quantized V, which
+# prism.hadamard.* metadata, which only the vendor build registers — and the
-# exact KV now makes moot — the type-142 lock alone keeps the build pinned).
+# b10776 gate that moved the prebuilt 10754 → 10777 (MTP beside a quantized V)
+# is LOAD-BEARING again on this shape, not moot as it was under exact KV.
 # Vision comes from the publisher's Q8_0 projector (the BF16 one can crash the
-# server on concurrent images, and this endpoint runs two slots), so --mmproj is
+# server on concurrent images, and this endpoint runs three slots), so --mmproj is
 # what gives this endpoint eyes; MMPROJ_FILE="" is the documented text-only
 # opt-out.
 #
-# Speculative decoding ships OFF, measured: the head loads and accepts well
+# Speculative decoding ships ON (Frank, 2026-10-19). The head is IN the file and
-# (0.798/0.617 per position, mean length 2.41) but the draft context bills its
+# accepts well (0.798/0.617 per position, mean length 2.41, measured 2026-10-18);
-# own f16 KV over the WHOLE pool — 4,096 B/position × 524,288 = 2,048 MiB plus
+# what made it lose that evening was the bill, not the drafts — the draft context
-# buffers — and the trunk already projects 21,234 MiB with exact KV. Exact KV
+# is built against the target's WHOLE pool, so blk.32 adds 4,096 B/position
-# and MTP cannot share this card; frank-zealot.env carries the q8_0-era arm table
+# (2,352.00 MiB at 602,112) plus 480.97 MiB of its own compute buffers on the
-# and the two doors back to the drafter (one window, or KV back to q8_0 at
+# card, and it triples the recurrent state per slot (452.25 MiB for three cells
-# --ubatch-size 1024 for 213.5 t/s).
+# against 50.25 a cell with the drafter off). CACHE_TYPE_V=q8_0 is what pays
+# that: 7,680 B/token cheaper than exact V, 4,410 MiB at this pool. The ubatch
+# drop to 1024 contributes ~406 MiB here, NOT the ~1,306 the 786,432-pool census
+# showed — that figure does not transfer between shapes. SPEC_TYPE=none is
+# the rollback and strips the whole flag set.
 #
 # Sampling: the checkpoint carries the publisher's thinking recipe as GGUF
 # metadata (general.sampling.* = temp 1.0 / top_p 0.95 / top_k 20 / min_p 0 /
@@ -58,49 +70,46 @@ fi
 : "${ALIAS:=frank-zealot}"
 : "${BIND_ADDR:=0.0.0.0}"
 : "${LISTEN_PORT:=7771}"
-# ctx-size is the POOL llama.cpp divides across slots: 524,288 / 2 = 262,144
+# ctx-size is the POOL llama.cpp divides across slots: 602,112 / 3 = 200,704 a
-# per conversation — every slot still at the model's trained window. The harness
+# conversation. The harness contextWindow MUST quote the PER-SLOT number — a
-# contextWindow MUST quote the PER-SLOT number — a longer prompt is answered
+# longer prompt is answered with a 400, never truncated. The pool is priced by
-# with a 400, never truncated. Under exact KV the pool cannot stay at 786,432:
+# the KV bill, not by the trained window: at 25,088 B/token (f16 K + q8_0 V) the
-# 32,768 B/token × 786,432 = 24,576 MiB, more than the card's whole addressable
+# 602,112 pool costs 14,406.00 MiB and the armed drafter adds its own f16 KV over
-# 24,123 MiB before a single weight loads.
+# the whole pool (2,352.00 MiB). Exact V at this pool (18,816 MiB) or the old
-: "${CTX_SIZE:=524288}"
+# 786,432 pool at any dtype cannot boot inside the 24,123 MiB the driver leaves
-: "${PARALLEL:=2}"
+# addressable.
+: "${CTX_SIZE:=602112}"
+: "${PARALLEL:=3}"
 # Compute-buffer geometry. Ubatch is a prefill knob (decode never moves).
-# 2048 is the measured CUDA optimum (MiMo era, same arch/shape: +4.6 % prefill
+# The logical batch is VRAM- and throughput-neutral at a fixed ubatch, so 6144
-# at 8.9k depth, decode flat, 616 MiB). The logical batch is VRAM- and
+# (1024×6) is free; the ubatch is what sets the compute-buffer size, and 1024 is
-# throughput-neutral at a fixed ubatch. It ALSO sets the compute-buffer size,
+# the rung every measured MTP arm here ran on (213.5 t/s at 1024 against 109.2
-# which is the term that decides whether an MTP draft context fits beside a KV
+# at 2048) — worth ~406 MiB at THIS shape, not the ~1,306 the old pool showed.
-# pool: 1024 hands back 1,306 MiB and was the arm that ran the drafter at three
+: "${BATCH_SIZE:=6144}"
-# q8_0 windows (frank-zealot.env carries the table).
+: "${UBATCH_SIZE:=1024}"
-: "${BATCH_SIZE:=4096}"
+# Asymmetric KV: f16 K (the engine's own default, spelled out so the contract is
-: "${UBATCH_SIZE:=2048}"
+# visible in argv) + q8_0 V. 8,192 elements per token per cache (8 full-attention
-# Exact KV: f16 K + f16 V — no quantization error anywhere in the attention
+# layers × 4 KV heads × 256 dim) ⇒ 16,384 B/token for K and 8,704 for V (q8_0 is
-# state. 32 KiB/token at this geometry (8 full-attention layers × 4 KV heads ×
+# 1.0625 B/element — llama.cpp has no true fp8 KV dtype), 25,088 B/token and
-# 256 dim × 2 B × 2 caches); 16,384.00 MiB at the 524,288 pool. That is the whole
+# 14,406.00 MiB at the 602,112 pool. That is the halfway door between exact KV
-# reason the slot count is 2: the same dtype at the old 786,432 pool is 24,576
+# (32,768 B/token, which costs the third conversation and the drafter both) and
-# MiB and dies at cudaMalloc. q8_0 K + q8_0 V (17,408 B/token, 13,056.00 MiB at
+# the fully quantized pair (17,408 B/token, which costs retrieval fidelity in the
-# 786,432) is the documented fallback rung and funds three windows; CACHE_TYPE_V
+# keys); --flash-attn stays pinned because quantized V is illegal without it.
-# alone is the halfway door. Explicit either way so the contract is visible in
-# the argv, and --flash-attn stays pinned because quantized V — the fallback —
-# is illegal without it (no true fp8 KV dtype exists in this build).
 : "${CACHE_TYPE_K:=f16}"
-: "${CACHE_TYPE_V:=f16}"
+: "${CACHE_TYPE_V:=q8_0}"
-# Speculative decoding defaults OFF, measured on this card and shape: the head
+# Speculative decoding defaults ON: the head IS in the checkpoint
-# IS in the checkpoint (qwen35.nextn_predict_layers = 1 — MTP is a property of
+# (qwen35.nextn_predict_layers = 1 — MTP is a property of the FILE, so the plain
-# the FILE, so the plain PQ2_0 sibling could not run it at any flag value), it
+# PQ2_0 sibling could not run it at any flag value) and the draft context rides
-# loads, and it accepts well (mean accepted length 2.41) — but the draft context
+# the MAIN model's weights, so there is no --spec-draft-model. Its bill is the
-# bills its own f16 KV over the WHOLE pool (4,096 B/position, 2,048 MiB at the
+# target's whole pool at 4,096 B/position plus ~0.45 GiB of buffers at this
-# 524,288 pool) and at ubatch 2048 that squeeze halves decode: 167.2 → 109.2 t/s
+# ubatch and a tripled recurrent state; CACHE_TYPE_V=q8_0 and UBATCH_SIZE=1024
-# on the q8_0 3-slot shape. The draft cache dtype IS a knob (--spec-draft-type-k
+# above are what pay for it. The draft cache dtype IS a further knob
-# / --spec-draft-type-v, both default f16 — verified in this build's --help), so
+# (--spec-draft-type-k / --spec-draft-type-v, both default f16 — verified in this
-# an armed drafter can halve its own bill; there is no --spec-draft-model because
+# build's --help) and stays at its default here. Card gate: quantized V alongside
-# the draft rides the main model's weights. Card gate: quantized V alongside MTP
+# MTP needs fork build >= prism-b10776, which is why LLAMA_BIN is the 10777
-# needs fork build >= prism-b10776, which is why LLAMA_BIN moved to the 10777
+# prebuilt; the type-142 loader lock keeps it pinned regardless.
-# prebuilt; exact KV removes that gate but NOT the type-142 loader lock.
+# SPEC_TYPE=none is the rollback and strips the whole set (flags move together).
-# SPEC_TYPE=draft-mtp + UBATCH_SIZE=1024 is the documented MTP arm (213.5 t/s);
+: "${SPEC_TYPE:=draft-mtp}"
-# SPEC_TYPE=none strips the whole set (flags move together).
-: "${SPEC_TYPE:=none}"
 : "${SPEC_DRAFT_N_MAX:=2}"
 : "${SPEC_DRAFT_N_MIN:=0}"
 : "${SPEC_DRAFT_P_MIN:=0}"

serverAppConfigs-docs/Agent/Agent Docs and Edits.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Agent Docs and Edits
-description: Two self-inflicted damage classes — structurally broken markdown after parallel agent edits, and botched hashline PUT/CUT repairs — with the audit checks and recovery order for each.
+description: "Two self-inflicted doc damage classes from parallel agent edits, with the audit checks and recovery order for each."
 tags: [agents, docs, markdown, hashline, edit-recovery]
 timestamp: 2026-10-18T00:00:00Z
 ---

serverAppConfigs-docs/Agent/Command Center Dotfiles.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Command Center Dotfiles
-description: The ~/.omp repo is itself the deployment — stow-equivalent packages, full-replica rsync transport, the pre-overwrite audit for non-blank hosts, deploy.sh mechanics, and the fish/sshpass transport gotchas.
+description: "How the dotfiles repo deploys: stow-equivalent packages, full-replica rsync, the pre-overwrite audit, transport gotchas."
 tags: [dotfiles, omp, deploy, rsync, blankpad]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/Agent/OMP Harness.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: OMP Harness
-description: The omp agent harness as configured on this fleet — compaction chain arithmetic, per-model sampler routing via compat.extraBody, and the static-preamble/skill-library audits that keep session context lean.
+description: "The omp harness as configured here: compaction chain arithmetic, per-model sampler routing, and the context-lean audits."
 tags: [omp, harness, compaction, models-yml, context, samplers]
 timestamp: 2026-10-18T00:00:00Z
 ---

serverAppConfigs-docs/Agent/index.md

@@ -1,23 +1,12 @@
----
-type: index
-description: Pages about the agent harness itself — omp config, vault editing discipline, and the dotfiles repo that deploys the agent's own home.
-tags: [agent, index]
-timestamp: 2026-10-05T00:00:00-07:00
----
-
 # Agent
 
 Pages about the agent's own tooling and context — how omp is configured, how
 docs get edited safely, and how the agent's home is deployed.
 
-- [[OMP Harness]] — compaction chain arithmetic, per-model samplers via
+- [[OMP Harness]] — The omp harness as configured here: compaction chain arithmetic, per-model sampler routing, and the context-lean audits.
-  `compat.extraBody`, preamble and skill-library audits
+- [[Agent Docs and Edits]] — Two self-inflicted doc damage classes from parallel agent edits, with the audit checks and recovery order for each.
-- [[Agent Docs and Edits]] — doc-structure audits after parallel edits;
+- [[Command Center Dotfiles]] — How the dotfiles repo deploys: stow-equivalent packages, full-replica rsync, the pre-overwrite audit, transport gotchas.
-  hashline edit recovery
-- [[Command Center Dotfiles]] — the `~/.omp` repo-as-deployment, rsync
-  transport, override packages
 
 ## Related
 
-- [[Testing Policy]] — the seams these pages' checks ride
 - [LLM](../LLM/index.md) — the fleet these agents operate

serverAppConfigs-docs/Architecture/Container Network Namespaces.md

@@ -1,8 +1,7 @@
 ---
 type: reference
 title: Container Network Namespaces
-description: Which local services are addressable from which Podman network namespace on
+description: "How Podman builds container networks here: the network inventory, the netns sharing mechanism, and the isolation limits."
-  Dankclaw, and why bridge-network containers cannot dial host-netns loopback listeners.
 tags:
   - networking
   - podman

serverAppConfigs-docs/Architecture/Deploy State Triage.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Deploy State Triage
-description: Reading and reconciling the deploy-state markers — stale marker vs live container, pending-service lockout, interrupted/raced deploys — without restarting healthy heavy endpoints.
+description: "Reading deploy-state markers against live containers and deciding, safely, whether to redeploy."
 tags: [deployment, deploy-state, systemd, podman, triage]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/Architecture/Deployment Flow.md

@@ -1,5 +1,5 @@
 ---
-type: guide
+type: howto
 title: Deployment Flow
 description: Service-scoped Git deployment for the two homelab hosts.
 tags:

serverAppConfigs-docs/Architecture/E2E Suite.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "`tests/e2e/` drives the **live fleet** through a real browser: fresh contexts"
+description: "The Playwright suite that drives the live fleet through a real browser, its project set, and the FrankBook conditional."
 tags:
   - architecture
   - e2e

serverAppConfigs-docs/Architecture/Quadlet Lifecycle.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Quadlet Lifecycle
-description: The full Quadlet discipline on this fleet — ownership auditing, compose-to-Quadlet cutover, drift/crash-loop diagnosis, the podman 5.x v1 generator quirks, log retrieval, and compose bring-up with ground truth.
+description: "The Quadlet discipline: ownership audits, compose cutover, drift and crash-loop triage, generator quirks, log retrieval."
 tags: [podman, quadlet, systemd, boot-persistence, compose, drift]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/Architecture/Stale Signal Audit.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Stale Signal Audit
-description: The audit battery for surfaces that rot without failing — unreachable probes, vacuous assertions, invalid checkers, gates that never run, and prose invalidated by a change. Four passes found real defects every time.
+description: "The audit battery for surfaces that rot without failing: dead probes, vacuous assertions, gates that never run."
 tags: [testing, observability, audit, signals, gates]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/Dankclaw/ComfyUI Qwen-Image Workflows.md

@@ -1,6 +1,6 @@
 ---
 type: howto
-description: "Qwen-Image 2.1 workflows on Dankclaw: two proven txt2img workflows (art + legible text), the API recipe, and which models/LoRAs to add next."
+description: "Proven Qwen-Image text-to-image workflows on Dankclaw: the recipes, the API call shape, and which models to add next."
 tags:
   - dankclaw
   - comfyui

serverAppConfigs-docs/Dankclaw/Frank TTS Engine.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "frank-tts-engine is the arm A TTS engine on Dankclaw: qwentts.cpp's resident tts-server with the 1.7 B base talker, on a private podman bridge behind frank-tts — deployed 2026-10-18, and it publishes no port on purpose."
+description: "The engine behind the fleet's speech endpoint: its runtime, private bridge, and the surface it publishes."
 tags:
   - dankclaw
   - tts

serverAppConfigs-docs/Dankclaw/Frank TTS.md

@@ -1,11 +1,13 @@
 ---
 type: reference
-description: "frank-tts is the fleet's cloned-voice speech endpoint on Dankclaw :7772 — the one voice surface consumers address, in front of frank-tts-engine; deployed 2026-10-18 and wired as the harness speech role."
+description: "The fleet's cloned-voice speech endpoint and the one voice surface consumers address; wired as the harness speech role."
 tags:
+ - endpoint
  - dankclaw
  - tts
  - voice
  - quadlet
+timestamp: 2026-10-19
 ---
 
 # Frank TTS
@@ -202,3 +204,4 @@ harness bundle and measured the day of the flip:
 | First request of the day is ~0.6 s slower than the rest — or every name returns 400 | the warm pass did not run; it carries `-`, so it cannot fail the unit. `journalctl --user -u frank-tts-engine` for the warmer's lines, then `podman exec frank-tts-engine /app/warm-voices.sh` — the registry is memory-only (law 1 of [[Frank TTS Engine]]) |
 | The unit never appears after a deploy | the generator dropped it: `frank-tts-engine.network` is missing from `~/.config/containers/systemd/` |
 | A consumer rejects `narrator1` by listing 29 names (`af_heart … bm_fable`) and no request ever reaches this endpoint | that consumer is synthesizing **in the browser** with Kokoro.js, whose voice pack is fixed — OpenWebUI 0.11.4 ships it as the `browser-kokoro` TTS engine; see [[OpenWebUI]] |
+---

serverAppConfigs-docs/Dankclaw/Gitea.md

@@ -1,5 +1,5 @@
 ---
-type: configuration
+type: reference
 title: Gitea
 description: Gitea deployment on Dankclaw with its web UI reverse-proxied by the canonical Caddy service.
 tags:

serverAppConfigs-docs/Dankclaw/Hermes-WebUI.md

@@ -1,7 +1,7 @@
 ---
-type: configuration
+type: reference
 title: Hermes-WebUI (Hermex server)
-description: The hermes-webui container on Dankclaw — the API server that the Hermex iPhone app talks to, reachable over an SSH tunnel, from the whole LAN (it binds all interfaces), and from https://hermes.franksdank.cloud (internal-only vhost).
+description: "The iPhone companion app for Hermes on Dankclaw and the ways it is reached from the LAN."
 tags:
   - hermes
   - hermes-webui

serverAppConfigs-docs/Dankclaw/Marreta.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Marreta on Dankclaw
-description: The content-cleaning proxy (manualdousuario/marreta, Laravel/serversideup fpm-nginx) deployed as a rootless Quadlet pair that shares SearXNG's Gluetun netns for egress and sits behind the Anubis + Authentik guard chain at marreta.franksdank.cloud.
+description: "The content-cleaning proxy SearXNG borrows egress from: a quadlet pair in the VPN netns behind the guard chain."
 tags:
   - dankclaw
   - marreta

serverAppConfigs-docs/Dankclaw/Open Notebook.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "open-notebook is the fleet's podcast generator on Dankclaw: notes and sources in, a multi-speaker episode out — script written by frank-zealot, voices rendered by frank-tts, no cloud provider anywhere in the path."
+description: "The fleet's podcast generator: notes in, multi-speaker episode out, script and voices both served in-house."
 tags:
   - dankclaw
   - open-notebook
@@ -13,7 +13,7 @@ timestamp: 2026-10-18
 
 open-notebook ([lfnovo/open-notebook](https://github.com/lfnovo/open-notebook)) is the notebook layer that turns existing notes and sources into a **spoken episode**: an outline, then a dialogue transcript, then one synthesized clip per speaker turn, concatenated with ffmpeg into an MP3. In the fleet it is the consumer that closes the loop Frank's audio stack was built for — the script is written by **frank-zealot**, the voices are rendered by **frank-tts**, and nothing leaves the LAN.
 
-**It is NOT deployed.** This page documents repo-owned configuration — the Quadlet units, the env file, the deployer path, the homepage card — and the contract those files were written against. On 2026-10-18 no `open-notebook` or `open-notebook-surrealdb` container exists on Dankclaw (`podman ps -a` census, 2026-10-18), and the homepage card ships `wip: "down"` with `showLink: false`, so the card is hidden and reported `wip-down`. Deploying it is a deliberate next step, not a pending one.
+**It is NOT deployed.** This page documents repo-owned configuration — the Quadlet units, the env file, the deployer path, the homepage card — and the contract those files were written against. On 2026-10-18 no `open-notebook` or `open-notebook-surrealdb` container exists on Dankclaw (`podman ps -a` census, 2026-10-18), and the homepage card ships `wip: "down"` with `showLink: false`, so the card is hidden and reported `wip-down`. Re-censused 2026-10-19 and unchanged: no `*notebook*` unit in `systemctl --user list-unit-files`, nothing installed under `~/.config/containers/systemd/` by that name, no container in `podman ps` — the repo's three quadlet files have never been installed on the host. Deploying it is a deliberate next step, not a pending one.
 
 **Host:** Dankclaw (rootless Podman, user `dank`) — **Ports:** 8502 UI and 5056 API, published on the LAN, **no vhost and no Caddy route** — **Deployer:** `open-notebook` (one service, two units) — **Docs:** https://github.com/lfnovo/open-notebook
 

serverAppConfigs-docs/Dankclaw/Seerr.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "Seerr is the unified request manager for the *arr stack (the maintained `seerr-team/seerr` successor to the archived Overseerr/Jellyseerr line)."
+description: "The request manager for the *arr stack — the maintained successor to the archived Overseerr line."
 tags:
   - dankclaw
   - seerr
@@ -40,8 +40,8 @@ the next outpost reload), and the missing app bounced post-login to
 authentik's own user UI instead of Seerr. Both backfilled live: the three
 standard flows copied from a known-good provider, plus an application
 (`seerr-guard`) linked to the provider. Verified by the hardened SSO sweep
-(`tests/e2e/specs/13-sso.spec.ts`) — see [[Authentik]] for the two
+(`tests/e2e/specs/13-sso.spec.ts`) — see [[Authentik Outpost Reference]] for the
-provisioning rules this incident established.
+two provisioning rules this incident established.
 
 ## *arr wiring
 

serverAppConfigs-docs/Dankclaw/Swap Configuration.md

@@ -1,7 +1,7 @@
 ---
-type: configuration
+type: reference
 title: Dankclaw Swap Configuration
-description: The host swapfile on Dankclaw — 64 GiB at /swap.img on ext4, fstab-driven via the generated swap.img.swap unit. Covers why it was raised from 8 GiB, the safe resize ordering that avoids an OOM on a host whose MemAvailable is inflated by pinned model weights, and the swappiness caveat.
+description: "The host swapfile: why it is sized as it is, the resize ordering that avoids an OOM, and the swappiness caveat."
 tags:
   - dankclaw
   - host

serverAppConfigs-docs/Dankclaw/Voice Packs.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "How a frank-tts voice pack is built on Dankclaw: the three files every pack must carry, the 10-second source-material gate scripts/build-voice-pack.sh enforces, how to add a fourth voice, and what to do when a pinned engine bump changes the extractor's output sizes."
+description: "How a voice pack is built: the files every pack must carry, the source-material gate, adding a voice, engine-bump drift."
 tags:
   - dankclaw
   - frank-tts

serverAppConfigs-docs/Dankserver/Copyparty.md

@@ -143,13 +143,13 @@ Copyparty v1.20.9+ supports WOPI (Web Application Open Platform Interface) for e
 
 ## Security Advisories
 
-| Version | CVE | Issue |
+| Version | Advisory | CVE | Issue |
-|---------|-----|-------|
+|---------|----------|-----|-------|
-| v1.20.19 | GHSA-phv8-wgjp-g4p9 | FTP upload outside volume |
+| v1.20.19 | GHSA-phv8-wgjp-g4p9 | CVE-2026-104102 | FTP upload outside the defined volumes (limited path traversal) |
-| v1.20.17 | GHSA-x5pq-m9p8-f4vx | dirkey/filekey confusion |
+| v1.20.17 | GHSA-x5pq-m9p8-f4vx | CVE-2026-70657 | dirkey/filekey confusion |
-| v1.20.9 | CVE-2026-27948 / GHSA-62cr-6wp5-q43h | XSS via file upload |
+| v1.20.9 | GHSA-62cr-6wp5-q43h | CVE-2026-27948 | reflected XSS via the `?setck=` URL parameter (not the upload path — the separate upload/DOM-XSS advisory is GHSA-m2jw-cj8v-937r) |
 
-Upgrade to v1.20.19+ to cover all known CVEs. The dirkey fix (v1.20.17) matters if using both `dirkeys` and `filekeys`.
+Upgrade to v1.20.19+ to cover all known advisories. The dirkey fix (v1.20.17) matters if using both `dirkeys` and `filekeys`. Each row's patched version is the advisory's own `first_patched_version`.
 
 ## Gotchas
 
@@ -174,3 +174,10 @@ Upgrade to v1.20.19+ to cover all known CVEs. The dirkey fix (v1.20.17) matters
 - [[Dankserver Stack]]
 - [[Caddy]] — TLS termination and authentication in front
 - [[ARR-Stack]] — Copyparty as a viewer alongside automated download management
+
+## Citations
+
+- GitHub Security Advisories, `9001/copyparty` —
+  https://github.com/9001/copyparty/security/advisories (accessed 2026-10-19);
+  each row's patched version read from `first_patched_version` in the
+  `https://api.github.com/advisories/<GHSA-id>` response.

serverAppConfigs-docs/Dankserver/Dankserver Stack.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "Dankserver (192.168.0.235) runs the media and library stack."
+description: "Service inventory and routing overview for the media and library host."
 tags:
   - dankserver
 timestamp: 2026-09-03

serverAppConfigs-docs/Dankserver/Jellyfin.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Jellyfin
-description: Jellyfin media server on Dankserver — quadlet unit, entropy-volume data layout, ports, client access, and hardware-transcode status.
+description: "Jellyfin on Dankserver: quadlet unit, entropy-volume data layout, ports, client access, hardware-transcode status."
 tags: [jellyfin, dankserver, media-server]
 timestamp: 2026-09-03T00:00:00Z
 ---

serverAppConfigs-docs/Dankserver/RomM-Scraping.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "This guide covers metadata providers, cover art, ROM naming conventions, emulator integration, and the scraping workflow for RomM on Dankserver."
+description: "Metadata providers, cover art, ROM naming and the scraping workflow behind the RomM library."
 tags:
   - dankserver
   - romm

serverAppConfigs-docs/Dankserver/mariadb.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: MariaDB (RomM Backend)
-description: MariaDB 11 database backend for RomM on Dankserver — quadlet unit, network alias, env-file secret handling, and backup path.
+description: "The MariaDB backend for RomM: quadlet unit, network alias, env-file secret handling, and the backup path."
 tags: [mariadb, romm, dankserver]
 timestamp: 2026-09-03T00:00:00Z
 ---

serverAppConfigs-docs/Dankserver/redis.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Redis (RomM Cache / Queue)
-description: Redis 7-alpine cache and task-queue backend for RomM on Dankserver — quadlet unit, network alias topology, and backup path.
+description: "The Redis cache and task queue for RomM: quadlet unit, network alias topology, and the backup path."
 tags: [redis, romm, dankserver]
 timestamp: 2026-09-03T00:00:00Z
 ---

serverAppConfigs-docs/Desktop/Noctalia and Niri.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Noctalia and Niri
-description: The noctalia v5 desktop shell on niri (workstation + blankpad) — config layers, remote IPC over ssh, custom-palette recolor, offline template rendering, and output rotation/pinning.
+description: "The noctalia shell on niri across workstations: config layers, remote IPC, custom palettes, output rotation and pinning."
 tags: [desktop, noctalia, niri, blankpad, workstation, ghostty]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/FrankBook-Pro/ARR-Stack.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: "*arr Stack"
-description: "The *arr automation stack (Prowlarr, Sonarr, Radarr, Lidarr, Readarr, qBittorrent) — FrankBook-Pro only, every container on the gluetun WireGuard netns (all egress VPN): topology, wiring, auth posture, and gotchas."
+description: "The *arr automation stack on FrankBook-Pro, every container on the VPN netns: topology, wiring, and gotchas."
 tags: [arr-stack, prowlarr, sonarr, radarr, lidarr, readarr, qbittorrent, frankbook-pro, dankserver]
 timestamp: 2026-09-04T00:00:00Z
 ---

serverAppConfigs-docs/FrankBook-Pro/index.md

@@ -7,10 +7,10 @@ Gluetun WireGuard netns. The host overview lives at [[FrankBook-Pro]]
 
 ## *arr Stack
 
-- [[ARR-Stack]] — the full *arr stack: indexers, managers, and the download client
+- [[ARR-Stack]] — The *arr automation stack on FrankBook-Pro, every container on the VPN netns: topology, wiring, and gotchas.
-- [[sonarr]] — TV show management
+- [[sonarr]] — Sonarr TV manager in the *arr stack on FrankBook-Pro — live quadlet deployment, ports, volumes, and wiring facts.
-- [[radarr]] — movie management
+- [[radarr]] — Radarr movie manager in the *arr stack on FrankBook-Pro — live quadlet deployment, ports, volumes, and wiring facts.
-- [[lidarr]] — music management
+- [[lidarr]] — Lidarr music manager in the *arr stack on FrankBook-Pro — live quadlet deployment, ports, volumes, and wiring facts.
-- [[readarr]] — ebook/audiobook management
+- [[readarr]] — The ebook and audiobook manager in the *arr stack: retired upstream, pinned image, parked download client.
-- [[prowlarr]] — indexer management
+- [[prowlarr]] — Indexer management for the *arr stack: feed routes, the sync model, the API surface, and verified live gotchas.
-- [[qbittorrent]] — torrent download client
+- [[qbittorrent]] — The download client for the *arr stack: pinned image, shared WireGuard netns, WebUI credential recipe.

serverAppConfigs-docs/FrankBook-Pro/prowlarr.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Prowlarr
-description: Prowlarr indexer-management layer for the *arr stack on FrankBook-Pro — feed routes, sync model, API surface, and verified live gotchas.
+description: "Indexer management for the *arr stack: feed routes, the sync model, the API surface, and verified live gotchas."
 tags: [prowlarr, arr-stack, frankbook-pro]
 timestamp: 2026-09-03T00:00:00Z
 ---

serverAppConfigs-docs/FrankBook-Pro/qbittorrent.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: qBittorrent
-description: qBittorrent download client for the *arr stack — pinned 4.6.7 on FrankBook-Pro, shares the Gluetun WireGuard netns, PBKDF2 WebUI credential recipe.
+description: "The download client for the *arr stack: pinned image, shared WireGuard netns, WebUI credential recipe."
 tags: [qbittorrent, arr-stack, frankbook-pro, gluetun]
 timestamp: 2026-09-03T00:00:00Z
 ---

serverAppConfigs-docs/FrankBook-Pro/readarr.md

@@ -1,18 +1,19 @@
 ---
 type: reference
 title: Readarr
-description: Readarr ebook/audiobook manager in the *arr stack on FrankBook-Pro — retired upstream, pinned image, parked qB download client.
+description: "The ebook and audiobook manager in the *arr stack: retired upstream, pinned image, parked download client."
 tags: [readarr, arr-stack, frankbook-pro]
 timestamp: 2026-09-03T00:00:00Z
 ---
 
 # Readarr
 
-> **RETIRED UPSTREAM (May 2026).** The Servarr Team retired Readarr: its
+> **RETIRED UPSTREAM (announced 2025-06-27).** The Servarr Team retired
-> metadata became unusable and the community migration to Open Library stalled.
+> Readarr: its metadata became unusable and the community migration to Open
-> There is no upstream development. Alternatives: the Bookshelf community fork,
+> Library stalled. There is no upstream development — the GitHub repository is
-> or the Calibre content server. This instance still runs on a pinned image
+> archived and its last push is 2025-06-27. Alternatives: the Bookshelf
-> tag; see below.
+> community fork, or the Calibre content server. This instance still runs on a
+> pinned image tag; see below.
 
 Readarr manages ebooks and audiobooks in the *arr stack. The stack runs on
 **FrankBook-Pro** (the Mac mini) as quadlet units inside its podman machine —
@@ -69,9 +70,9 @@ Restart=always
 
 ## Gotchas
 
-- Readarr is abandoned upstream (retired May 2026; last line was 0.4.x before
+- Readarr is abandoned upstream (retired 2025-06-27; last line was 0.4.x
-  the final tags). The pinned `amd64-1.0.980` tag exists precisely because
+  before the final tags). The pinned `amd64-1.0.980` tag exists precisely
-  `:latest` does not exist for this image on LSIO.
+  because `:latest` does not exist for this image on LSIO.
 - Calibre integration is folder-based, not API-based. Readarr drops files into
   the books root which [[Calibre-Web]] serves.
 - Not all indexers carry all formats (epub, mobi, pdf). Goodreads/StoryGraph
@@ -81,3 +82,10 @@ Restart=always
 
 - [[ARR-Stack]] — full *arr stack documentation
 - [[Calibre-Web]] — ebook web frontend that serves Readarr downloads
+
+## Citations
+
+- Servarr wiki, *Readarr* (Retired) — "Announcement: Retirement of Readarr
+  2025-06-27" — https://wiki.servarr.com/readarr (accessed 2026-10-19)
+- `Readarr/Readarr` on GitHub: `archived: true`, last push 2025-06-27 —
+  https://api.github.com/repos/Readarr/Readarr (accessed 2026-10-19)

serverAppConfigs-docs/Infrastructure/Alertmanager.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "Alertmanager receives firing rules from Prometheus, groups and dedupes them, and forwards each group as a webhook to the host-side Signal relay — which sends it through..."
+description: "Receives firing rules from Prometheus, groups and dedupes them, and forwards each group to the host-side Signal relay."
 tags:
   - infrastructure
 timestamp: 2026-09-17

serverAppConfigs-docs/Infrastructure/Authentik Outpost Reference.md

@@ -0,0 +1,230 @@
+---
+type: reference
+description: "Outpost, proxy-provider, OAuth2, LDAP and flow configuration for the homelab's Authentik SSO."
+tags:
+  - infrastructure
+  - authentik
+timestamp: 2026-10-19
+---
+
+# Authentik Outpost Reference
+
+Configuration lookup for the [[Authentik]] deployment: the live proxy-provider
+inventory behind the guarded vhosts, the provisioning rules the embedded outpost
+enforces, this fork's OAuth2 relying-party quirks, the LDAP provider objects, the
+self-serve user-settings flow, and the live database shape. What the service is,
+how it is deployed, wired and operated is [[Authentik]]; the three core
+containers are [[Authentik Processes]].
+
+## Live proxy-provider inventory
+
+Live provider inventory (read from the `authentik-postgres` container with
+read-only `SELECT`s, 2026-10-18). Nine proxy providers, all attached to outpost
+`7e39655b-58d3-4fe6-a80a-513f31051217` ("authentik Embedded Outpost", 9
+members in `authentik_outposts_outpost_providers`), all with
+`internal_host = http://caddy:8017`, all carrying the **same three flow
+UUIDs** (`default-authentication-flow`,
+`default-provider-authorization-implicit-consent`,
+`default-provider-invalidation-flow`), and each backed by an Application
+(the `slug` column below):
+
+| Provider pk | name | external_host | app slug |
+|---|---|---|---|
+| 1 | embedded-outpost | `https://www.franksdank.cloud` | caddy |
+| 2 | search-proxy | `https://search.franksdank.cloud` | search |
+| 4 | prometheus-proxy | `https://prometheus.franksdank.cloud` | prometheus |
+| 5 | romm-proxy | `https://romm.franksdank.cloud` | romm |
+| 6 | files-proxy | `https://files.franksdank.cloud` | files |
+| 7 | loki-proxy | `https://loki.franksdank.cloud/` | loki |
+| 8 | grafana-proxy | `https://grafana.franksdank.cloud/` | grafana-guard |
+| 10 | seerr-proxy | `https://seerr.franksdank.cloud/` | seerr-guard |
+| 13 | marreta-proxy | `https://marreta.franksdank.cloud` | marreta |
+
+That is exactly the Caddyfile's guarded set (`dankclaw/Caddyfile:283-423`), so
+the lockstep rule in [[Authentik]] holds today. Two corrections against the 2026-09-02 table:
+**pk 13 (`marreta-proxy`) was added** when Marreta went onto the chain, and
+**pk 3 (`hermes-proxy`) no longer exists at all** — `select … where id=3`
+returns zero rows, so it is deleted, not "dormant"; its vhost survived but is
+exempt-by-construction (`dankclaw/Caddyfile:179-191`). OAuth2 relying parties,
+not proxy providers, so the proxy outpost does not deserialize them: pk 9
+`grafana` (`grant_types = {authorization_code}`), pk 12 `Seerr OIDC`
+(`grant_types = {}` — empty, i.e. still in the state the token-endpoint rule
+below rejects), and pk 14 `Open WebUI`
+(`grant_types = {authorization_code,refresh_token}`). Trailing slashes on
+`external_host` (the runbook-recipe style) and bare origins both intercept
+correctly — the outpost matches on hostname.
+
+## Provisioning rules for proxy providers
+
+Two provisioning rules, each verified live by an outage:
+
+1. **All three flows are required.** A ProxyProvider created via raw API/ORM
+   with any of `authentication_flow`/`authorization_flow`/`invalidation_flow`
+   null wedges the embedded outpost's config fetch: the Rust side rejects the
+   whole config JSON (serde: `invalid type: null, expected a formatted UUID
+   string`), logs `Failed to fetch outpost from API, retrying in 3 seconds`
+   forever, and **everything behind the outpost dies at the next outpost
+   reload** — including hosts whose providers were fine (verified 2026-09-02
+   when three providers provisioned without any flows took down every guarded
+   vhost after a server restart). Backfill all three flows (copy from pk 1:
+   `default-authentication-flow`,
+   `default-provider-authorization-implicit-consent` (the implicit-consent
+   authorization flow, `default-invalidation-flow`) and the retry loop
+   recovers on its next 3-second cycle. The silent killer: while the outpost
+   process keeps its last good in-memory config, everything works — the
+   outage only surfaces on restart/reload.
+2. **Every proxy provider needs an attached Application.** The outpost
+   resolves the post-login redirect through the provider's application; a
+   provider with no app completes the login (authentik session established)
+   but bounces to authentik's own user UI (`/if/user/#/library`) instead of
+   the app. No error is logged anywhere — the SSO "works" and the app never
+   appears. Create the Application with `provider_id` set (the UI does this
+   automatically; raw API/ORM drives must do it explicitly).
+
+## OAuth2 relying-party quirks (this fork, verified live 2026-08-31)
+
+The Grafana RP provider (`grafana`, pk 9, confidential client) was created and
+verified end-to-end via `ak shell` ORM drives. This fork's OAuth2 provider
+implementation diverges from upstream in ways that bit us; all verified live:
+
+- **Application row required.** `OAuth2Provider.objects.create()` does not
+  create the single-table-inheritance `Application` row; without it the flow
+  executor can never complete an authorize request. Create both rows.
+- **`grant_types` defaults to empty.** Until the provider's `grant_types`
+  contains `"authorization_code"` (enum value with underscore), the token
+  endpoint rejects every exchange with `invalid_request`.
+- **Token endpoint is form-encoded + Basic-auth only.** A JSON body makes
+  `parse_token_request` see no `grant_type` → `unsupported_grant_type`;
+  POST-body client secrets are not accepted — authenticate the confidential
+  client with `Authorization: Basic base64(client_id:client_secret)`.
+- **Provider resolution is by `client_id` query param** on the global
+  `/application/o/authorize/` route; per-slug authorize paths do not exist in
+  this build. Token/userinfo live at `/application/o/token/` and
+  `/application/o/userinfo/?api=1`.
+- **Property-mapping evaluator is broken → userinfo returns `sub` only.**
+  `PropertyMappingEvaluator.evaluate(*args, **kwargs)` forwards kwargs to
+  `BaseEvaluator.evaluate(expression_source)`, so the first context kwarg
+  becomes the *expression source* instead of the context; every call raises a
+  swallowed `PropertyMappingExpressionException` and the claim is skipped.
+  Scope-grant filtering has the same class of bug: `ScopeMapping` has no
+  provider FK (linkage lives in the `ProviderPropertyMapping` through model),
+  so `filter(provider=...)` always yields an empty queryset and tokens asked
+  to carry scopes get zero. Net effect: userinfo/introspection answers with
+  `{sub}` only — email/groups/entitlements claims cannot be delivered by this
+  build until the evaluator is patched or upgraded. Clients consuming this
+  provider must key identity off `sub`.
+- Scope mappings for this provider exist — `grafana-email-scope` and
+  `grafana-profile-scope` are both rows in `authentik_core_propertymapping`
+  (read-only `SELECT`, 2026-10-18) — and will start emitting claims the moment
+  the evaluator bug is fixed; no config change is needed then.
+
+## LDAP provider objects (provisioned via `ak shell` ORM)
+
+The LDAP outpost's own deployment — unit, image digest, published ports, token
+env var — is in [[Authentik]]. The objects it serves:
+
+Read from the live database (read-only `SELECT`s against the
+`authentik-postgres` container, 2026-10-18):
+
+| Object | Value |
+|---|---|
+| LDAP provider | `Jellyfin LDAP` (pk 11), base DN `dc=franksdank,dc=cloud`, `search_mode=direct`, `bind_mode=direct` |
+| Bind DN | `cn=svc-jellyfin-ldap,ou=users,dc=franksdank,dc=cloud` *(unverified 2026-10-18: base DN confirmed in the DB, the `ou=users` path was not probed — an LDAP bind needs the bind secret)* |
+| Service account | `svc-jellyfin-ldap` (user pk 8). **It is not passwordless**: its password field is a real hash, not Django's `!`-prefixed unusable marker (`starts_with(password,'!')` → `f`) — an earlier revision's "passwordless/unusable" claim is wrong, which matters because an account with a usable password can sign in through the ordinary password flow *(unverified 2026-10-18: whether anyone holds that password)* |
+| Bind token | exactly one row for pk 8, **`intent=app_password`**, non-expiring — an earlier revision recorded `intent=verification`; the live value is `app_password` |
+| RBAC role | `svc-jellyfin-ldap-search`, carrying exactly one object-level permission `authentik_providers_ldap.search_full_directory` (verified via `guardian_roleobjectpermission`) |
+| Groups | `jellyfin_users`, `jellyfin_admins` (both exist in `authentik_core_group`) |
+| Application | name `Jellyfin`, **slug `jellyfin-ldap`** (an earlier revision said slug `jellyfin`, which does not exist) |
+
+Hard-won rules (the first is now contested by the live database):
+
+- **Token intent: contested, do not trust either value blindly.** An earlier
+  revision asserted that a bind token with `intent=app_password` is rejected by
+  the flow's password stage with `Invalid password` and only
+  `intent=verification` passes. The live token for `svc-jellyfin-ldap` is
+  `app_password` (`authentik_core_token`, 2026-10-18), so either the rule is
+  wrong or the current Jellyfin bind path is not that token. Nothing observable
+  settles it today: the LDAP outpost's retained log holds only its 5-minute
+  `initialized direct binder` / `Update providers` config cycles and no bind
+  activity *(unverified 2026-10-18: no bind was performed — reproducing it
+  requires the bind secret)*. Re-verify with a real bind before changing the
+  token's intent either way.
+- **Search needs `search_full_directory`.** Without the RBAC grant the
+  outpost returns only the bind user itself — a `(memberOf=…)` filter then
+  matches zero entries and the plugin logs `Found no users matching X`.
+  The permission is object-level on the provider; grant it via an RBAC role
+  and retest.
+- `ak shell` import path for the provider model in 2026.8:
+  `from authentik.providers.ldap.models import LDAPProvider`.
+  *(unverified 2026-10-18: importing it outside a configured Django shell fails
+  with `ImproperlyConfigured`, and no `ak shell` was driven against the live
+  auth service for this check)*
+
+## Self-serve user-settings flow (password change)
+
+Users change their own account details through the `default-user-settings-flow`
+(`https://auth.franksdank.cloud/if/flow/default-user-settings-flow/`) — the
+target of the homepage footer's "account" link. It is a `stage_configuration`
+designated flow, so it renders every bound `ConfigurableStage` for the logged-in
+user.
+
+Stages, in execution order (the `FlowStageBinding.order` field, not the M2M
+insertion order):
+
+| order | stage | type | what it does |
+|---|---|---|---|
+| 20 | `default-user-settings` | `PromptStage` | name / email / locale **+ password** |
+| 100 | `default-user-settings-write` | `UserWriteStage` | writes the prompt data to the user |
+
+**Password change is a prompt field, not a stage.** The `UserWriteStage`
+writes whatever the preceding `PromptStage` collected: for the key `password`
+it calls `user.set_password(value)` (`stages/user_write/stage.py`). So the fix
+is a `password` field on the `default-user-settings` prompt
+(`field_key=password`, `type=password`, `required=False`, order 204) — NOT a
+`PasswordStage`. A `PasswordStage` is an *authentication* stage: its
+`validate_password` runs `authenticate()` against the backends to check the
+*current* password; it never sets a new one. (A `PasswordStage` was added on
+2026-09-25 and removed the same day for exactly this reason.)
+
+Two ORM gotchas: `Flow.stages.add()` fails on this through model
+(`Can't bulk create a multi-table inherited model` — `FlowStageBinding` is
+MTI), so create the `FlowStageBinding` row directly with an explicit `order`;
+and a prompt field is a `Prompt` row linked through `PromptStageField`
+(`prompt_stage` + `prompt`; the order comes from `Prompt.order`).
+
+**A blank password must not set an empty password.** `set_password("")` would
+make the account log in with no password, so a validation policy
+(`default-user-settings-no-empty-password`, bound to the prompt via
+`PromptStageValidationPolicy`) denies the form when `prompt_data["password"]`
+is `""` and allows it when set. Verified with the `PolicyEvaluator`
+(empty → deny, set → allow, absent → allow) and end-to-end by driving
+`UserWriteStageView.update_user` on a throwaway user (new password valid, old
+invalid).
+
+## Live database shape
+
+For live DB truth prefer the postgres container, and it works without any
+credential — the local socket is trusted, so a read-only audit is just
+`podman exec -i authentik-postgres psql -U authentik -d authentik -At -f -`
+with SQL on stdin (quoting SQL through ssh+zsh otherwise fights you). Verify
+before guessing: 2026.x renamed both tables and columns, and the models are
+MTI all the way down — `authentik_core_provider` holds `id`, `name` and the
+three `*_flow_id` columns; the proxy table is
+`authentik_providers_proxy_proxyprovider` (doubled `proxy`) and its PK column
+really is **`oauth2provider_ptr_id`** (proxy providers inherit the OAuth2
+table in 2026.8), the LDAP table is
+`authentik_providers_ldap_ldapprovider` with PK `provider_ptr_id`;
+`authentik_core_application` attaches to a provider through `provider_id`
+(its PK is `policybindingmodel_ptr_id`, not `id`), and `authentik_outposts_outpost`
+is keyed by `uuid`. So `Provider.objects.filter(type=…)` raising `FieldError`
+is the same story from the ORM side: `type` lives in the subclass tables.
+Never select secret columns (`client_secret`, `key`, `password`) into a log.
+
+## Cross-references
+
+- [[Authentik]] — what the service is, its deployment, wiring, operations and
+  failure modes
+- [[Authentik Processes]] — the postgres, server and worker containers
+- [[Caddy]] — the reverse proxy carrying the `:8016`/`:8017` auth-chain listeners
+- [[Jellyfin]] — consumes the LDAP outpost via its LDAP-Auth plugin
+- [[Grafana]] — guarded vhost *and* OAuth2 relying party of this provider

serverAppConfigs-docs/Infrastructure/Authentik Processes.md

@@ -0,0 +1,76 @@
+---
+type: reference
+description: "The three core Authentik containers — database, server and worker — with their units, images, roles and probes."
+tags:
+  - infrastructure
+  - authentik
+  - postgres
+timestamp: 2026-10-19
+---
+
+# Authentik Processes
+
+The three core containers of the [[Authentik]] stack on Dankclaw. The two
+outpost units are not covered here — they live on [[Authentik]] and
+[[Authentik Outpost Reference]]. Server and worker run the same image; the
+`command` selects the role (`server` / `worker`). Data persists under
+`/home/dank/Containers/authentik/` as bind mounts (repo policy — no named
+volumes), moved from `/home/dank/authentik/` in the 2026-09-01 quadlet
+standardization; the retired stubs this page replaces recorded the pre-move
+paths `/home/dank/authentik/data` (server and worker) and
+`/home/dank/authentik/postgres` (database).
+
+## authentik-postgres
+
+The PostgreSQL 16 database for Authentik — the only stateful store in the stack
+(users, flows, sessions, events). Sessions, caching, and WebSockets moved to
+PostgreSQL in 2025.10 (Redis removed).
+
+- **Image:** `docker.io/library/postgres:16-alpine`
+- **Data:** `/home/dank/Containers/authentik/postgres` (bind mount; no named
+  volumes)
+- **Health:** `pg_isready -d authentik -U authentik`
+- **Retired wording:** the stub called this a "Compose service … in
+  `dankclaw/compose.yaml`"; the compose stack is gone and the unit is a quadlet.
+- The side-by-side with `gitea-postgres` (network, published ports, secret
+  source, boot persistence) is owned by [[Postgres]].
+
+## authentik-server
+
+The Authentik server — the core, the admin API, and the embedded Caddy outpost.
+It also serves the login page at `https://auth.franksdank.cloud`.
+
+- **Unit:** `dankclaw/authentik/quadlet/authentik-server.container`
+  (`authentik-server.service`)
+- **Image:** `ghcr.io/goauthentik/server:2026.8.3` (`command: server`)
+- **Port:** `9000` (published) — the outpost, the admin API and the login UI all
+  live here
+- **Data:** `/home/dank/Containers/authentik/data` (bind mount, shared with the
+  worker)
+- **Health:** recorded by the retired stub as
+  `http://localhost:9000/-/health/`; superseded — [[Authentik]] → Operations
+  owns the live probe.
+- **Retired wording:** the stub described "the Caddy `forward_auth` vhosts"
+  proxying here; the chain Caddy actually runs is [[Authentik]] → Caddy
+  integration.
+
+## authentik-worker
+
+The Authentik worker — background tasks: event processing, provider
+synchronization, scheduled flows, and certificate renewal.
+
+- **Unit:** `dankclaw/authentik/quadlet/authentik-worker.container`
+  (`authentik-worker.service`)
+- **Image:** `ghcr.io/goauthentik/server:2026.8.3` (`command: worker`)
+- **Runs as:** `0:0` (rootless: container root maps to the host user that owns
+  the data dir)
+- **Data:** `/home/dank/Containers/authentik/data` (bind mount, shared with the
+  server)
+- **No port** — the worker has no HTTP endpoint.
+
+## Cross-references
+
+- [[Authentik]] — what the service is, its deployment, wiring, operations and
+  failure modes
+- [[Authentik Outpost Reference]] — provider, flow and token configuration
+- [[Postgres]] — both PostgreSQL clusters on Dankclaw, side by side

serverAppConfigs-docs/Infrastructure/Authentik.md

@@ -16,7 +16,7 @@ OpenWebUI, Jellyfin (LDAP outpost), the *arr stack, Pi-hole (basicauth edge) —
 they handle their own session. Grafana is the exception that is both: it is a
 guarded vhost (`grafana-proxy`, pk 8, locked to Authentik SSO) *and* an OAuth2
 relying party (`grafana`, pk 9) (`dankclaw/Caddyfile:122-132`,
-`dankclaw/Caddyfile:374-377`; live provider table below).
+`dankclaw/Caddyfile:374-377`; live provider table in [[Authentik Outpost Reference]]).
 
 - **Version:** `2026.8.3` (pinned in `dankclaw/authentik/quadlet/*.container`;
   the outpost's boot log reads `"Booting authentik" … "version": "2026.8.3"`,
@@ -35,6 +35,13 @@ relying party (`grafana`, pk 9) (`dankclaw/Caddyfile:122-132`,
   pre-quadlet era, retired.
 - **LDAP outpost:** serves LDAP for Jellyfin — see the section below.
 
+**Split off from this page:** [[Authentik Processes]] owns the per-container
+facts for `authentik-postgres`, `authentik-server` and `authentik-worker`;
+[[Authentik Outpost Reference]] owns the provider/flow/token lookup material —
+the live proxy-provider inventory, the proxy-provider provisioning rules, the
+OAuth2 relying-party quirks, the LDAP provider objects, the user-settings flow
+design, and the live database shape.
+
 ## Why Authentik
 
 The comparison that chose it (against Authelia, Keycloak, Zitadel, Ory) was
@@ -100,23 +107,10 @@ contract:
   The chain terminates there — nothing dials back into Authentik from
   `:8017`.
 
-## The three compose services
+## The stack's processes
 
-| Service | Role | Image |
+Per-container facts — unit path, image and role, port, run-as, data directory,
-|---|---|---|
+health probe — are owned by [[Authentik Processes]].
-| `authentik-postgres` | PostgreSQL 16 (users, flows, sessions, events) | `docker.io/library/postgres:16-alpine` |
-| `authentik-server` | Core + admin API + the embedded Caddy outpost (port 9000) | `ghcr.io/goauthentik/server:2026.8.3` |
-| `authentik-worker` | Background tasks (event processing, provider sync, flows) | `ghcr.io/goauthentik/server:2026.8.3` |
-
-- **Postgres** is the only stateful store. Sessions, caching, and WebSockets
-  moved to PostgreSQL in 2025.10 (Redis removed).
-- **Server** and **worker** run the same image; the `command` selects the role
-  (`server` / `worker`).
-- The worker runs as `0:0` (rootless: container root maps to the host user that
-  owns the data dir).
-- Data persists under `/home/dank/Containers/authentik/{data,postgres}`
-  (bind mounts, repo policy — no named volumes; moved from `/home/dank/authentik/`
-  in the 2026-09-01 quadlet standardization).
 
 ## Caddy integration
 
@@ -142,104 +136,9 @@ routing table, and the Authentik proxy-provider list must be the same set of
 hosts. A guarded host with no provider 404s at login time; a provider with no
 DNS record breaks off-LAN clients.
 
-Live provider inventory (read from the `authentik-postgres` container with
+The live proxy-provider inventory (the per-vhost `external_host` → app mapping),
-read-only `SELECT`s, 2026-10-18). Nine proxy providers, all attached to outpost
+the two provisioning rules the outpost enforces, and this fork's OAuth2
-`7e39655b-58d3-4fe6-a80a-513f31051217` ("authentik Embedded Outpost", 9
+relying-party quirks are reference lookup: [[Authentik Outpost Reference]].
-members in `authentik_outposts_outpost_providers`), all with
-`internal_host = http://caddy:8017`, all carrying the **same three flow
-UUIDs** (`default-authentication-flow`,
-`default-provider-authorization-implicit-consent`,
-`default-provider-invalidation-flow`), and each backed by an Application
-(the `slug` column below):
-
-| Provider pk | name | external_host | app slug |
-|---|---|---|---|
-| 1 | embedded-outpost | `https://www.franksdank.cloud` | caddy |
-| 2 | search-proxy | `https://search.franksdank.cloud` | search |
-| 4 | prometheus-proxy | `https://prometheus.franksdank.cloud` | prometheus |
-| 5 | romm-proxy | `https://romm.franksdank.cloud` | romm |
-| 6 | files-proxy | `https://files.franksdank.cloud` | files |
-| 7 | loki-proxy | `https://loki.franksdank.cloud/` | loki |
-| 8 | grafana-proxy | `https://grafana.franksdank.cloud/` | grafana-guard |
-| 10 | seerr-proxy | `https://seerr.franksdank.cloud/` | seerr-guard |
-| 13 | marreta-proxy | `https://marreta.franksdank.cloud` | marreta |
-
-That is exactly the Caddyfile's guarded set (`dankclaw/Caddyfile:283-423`), so
-the lockstep rule holds today. Two corrections against the 2026-09-02 table:
-**pk 13 (`marreta-proxy`) was added** when Marreta went onto the chain, and
-**pk 3 (`hermes-proxy`) no longer exists at all** — `select … where id=3`
-returns zero rows, so it is deleted, not "dormant"; its vhost survived but is
-exempt-by-construction (`dankclaw/Caddyfile:179-191`). OAuth2 relying parties,
-not proxy providers, so the proxy outpost does not deserialize them: pk 9
-`grafana` (`grant_types = {authorization_code}`), pk 12 `Seerr OIDC`
-(`grant_types = {}` — empty, i.e. still in the state the token-endpoint rule
-below rejects), and pk 14 `Open WebUI`
-(`grant_types = {authorization_code,refresh_token}`). Trailing slashes on
-`external_host` (the runbook-recipe style) and bare origins both intercept
-correctly — the outpost matches on hostname.
-
-Two provisioning rules, each verified live by an outage:
-
-1. **All three flows are required.** A ProxyProvider created via raw API/ORM
-   with any of `authentication_flow`/`authorization_flow`/`invalidation_flow`
-   null wedges the embedded outpost's config fetch: the Rust side rejects the
-   whole config JSON (serde: `invalid type: null, expected a formatted UUID
-   string`), logs `Failed to fetch outpost from API, retrying in 3 seconds`
-   forever, and **everything behind the outpost dies at the next outpost
-   reload** — including hosts whose providers were fine (verified 2026-09-02
-   when three providers provisioned without any flows took down every guarded
-   vhost after a server restart). Backfill all three flows (copy from pk 1:
-   `default-authentication-flow`,
-   `default-provider-authorization-implicit-consent` (the implicit-consent
-   authorization flow, `default-invalidation-flow`) and the retry loop
-   recovers on its next 3-second cycle. The silent killer: while the outpost
-   process keeps its last good in-memory config, everything works — the
-   outage only surfaces on restart/reload.
-2. **Every proxy provider needs an attached Application.** The outpost
-   resolves the post-login redirect through the provider's application; a
-   provider with no app completes the login (authentik session established)
-   but bounces to authentik's own user UI (`/if/user/#/library`) instead of
-   the app. No error is logged anywhere — the SSO "works" and the app never
-   appears. Create the Application with `provider_id` set (the UI does this
-   automatically; raw API/ORM drives must do it explicitly).
-
-
-## OAuth2 relying-party quirks (this fork, verified live 2026-08-31)
-
-The Grafana RP provider (`grafana`, pk 9, confidential client) was created and
-verified end-to-end via `ak shell` ORM drives. This fork's OAuth2 provider
-implementation diverges from upstream in ways that bit us; all verified live:
-
-- **Application row required.** `OAuth2Provider.objects.create()` does not
-  create the single-table-inheritance `Application` row; without it the flow
-  executor can never complete an authorize request. Create both rows.
-- **`grant_types` defaults to empty.** Until the provider's `grant_types`
-  contains `"authorization_code"` (enum value with underscore), the token
-  endpoint rejects every exchange with `invalid_request`.
-- **Token endpoint is form-encoded + Basic-auth only.** A JSON body makes
-  `parse_token_request` see no `grant_type` → `unsupported_grant_type`;
-  POST-body client secrets are not accepted — authenticate the confidential
-  client with `Authorization: Basic base64(client_id:client_secret)`.
-- **Provider resolution is by `client_id` query param** on the global
-  `/application/o/authorize/` route; per-slug authorize paths do not exist in
-  this build. Token/userinfo live at `/application/o/token/` and
-  `/application/o/userinfo/?api=1`.
-- **Property-mapping evaluator is broken → userinfo returns `sub` only.**
-  `PropertyMappingEvaluator.evaluate(*args, **kwargs)` forwards kwargs to
-  `BaseEvaluator.evaluate(expression_source)`, so the first context kwarg
-  becomes the *expression source* instead of the context; every call raises a
-  swallowed `PropertyMappingExpressionException` and the claim is skipped.
-  Scope-grant filtering has the same class of bug: `ScopeMapping` has no
-  provider FK (linkage lives in the `ProviderPropertyMapping` through model),
-  so `filter(provider=...)` always yields an empty queryset and tokens asked
-  to carry scopes get zero. Net effect: userinfo/introspection answers with
-  `{sub}` only — email/groups/entitlements claims cannot be delivered by this
-  build until the evaluator is patched or upgraded. Clients consuming this
-  provider must key identity off `sub`.
-- Scope mappings for this provider exist — `grafana-email-scope` and
-  `grafana-profile-scope` are both rows in `authentik_core_propertymapping`
-  (read-only `SELECT`, 2026-10-18) — and will start emitting claims the moment
-  the evaluator bug is fixed; no config change is needed then.
 
 ## LDAP outpost (Jellyfin auth, live 2026-09-01)
 
@@ -267,44 +166,9 @@ rule at the current `2026.8.3` pin. Resolve once with `podman manifest inspect
   (2026-10-18). The outpost token travels in `AUTHENTIK_LDAP_OUTPOST_TOKEN`
   from the host `dankclaw/.env` (git-ignored).
 
-### Authentik-side objects (provisioned via `ak shell` ORM)
+The objects behind it — LDAP provider, bind DN, service account and bind token,
-
+RBAC grant, groups, application slug — and the hard-won bind rules are in
-Read from the live database (read-only `SELECT`s against the
+[[Authentik Outpost Reference]].
-`authentik-postgres` container, 2026-10-18):
-
-| Object | Value |
-|---|---|
-| LDAP provider | `Jellyfin LDAP` (pk 11), base DN `dc=franksdank,dc=cloud`, `search_mode=direct`, `bind_mode=direct` |
-| Bind DN | `cn=svc-jellyfin-ldap,ou=users,dc=franksdank,dc=cloud` *(unverified 2026-10-18: base DN confirmed in the DB, the `ou=users` path was not probed — an LDAP bind needs the bind secret)* |
-| Service account | `svc-jellyfin-ldap` (user pk 8). **It is not passwordless**: its password field is a real hash, not Django's `!`-prefixed unusable marker (`starts_with(password,'!')` → `f`) — the page's earlier "passwordless/unusable" claim is wrong, which matters because an account with a usable password can sign in through the ordinary password flow *(unverified 2026-10-18: whether anyone holds that password)* |
-| Bind token | exactly one row for pk 8, **`intent=app_password`**, non-expiring — the page previously recorded `intent=verification`; the live value is `app_password` |
-| RBAC role | `svc-jellyfin-ldap-search`, carrying exactly one object-level permission `authentik_providers_ldap.search_full_directory` (verified via `guardian_roleobjectpermission`) |
-| Groups | `jellyfin_users`, `jellyfin_admins` (both exist in `authentik_core_group`) |
-| Application | name `Jellyfin`, **slug `jellyfin-ldap`** (the page previously said slug `jellyfin`, which does not exist) |
-
-Hard-won rules (the first is now contested by the live database):
-
-- **Token intent: contested, do not trust either value blindly.** This page
-  long asserted that a bind token with `intent=app_password` is rejected by the
-  flow's password stage with `Invalid password` and only `intent=verification`
-  passes. The live token for `svc-jellyfin-ldap` is `app_password`
-  (`authentik_core_token`, 2026-10-18), so either the rule is wrong or the
-  current Jellyfin bind path is not that token. Nothing observable settles it
-  today: the LDAP outpost's retained log holds only its 5-minute
-  `initialized direct binder` / `Update providers` config cycles and no bind
-  activity *(unverified 2026-10-18: no bind was performed — reproducing it
-  requires the bind secret)*. Re-verify with a real bind before changing the
-  token's intent either way.
-- **Search needs `search_full_directory`.** Without the RBAC grant the
-  outpost returns only the bind user itself — a `(memberOf=…)` filter then
-  matches zero entries and the plugin logs `Found no users matching X`.
-  The permission is object-level on the provider; grant it via an RBAC role
-  and retest.
-- `ak shell` import path for the provider model in 2026.8:
-  `from authentik.providers.ldap.models import LDAPProvider`.
-  *(unverified 2026-10-18: importing it outside a configured Django shell fails
-  with `ImproperlyConfigured`, and no `ak shell` was driven against the live
-  auth service for this check)*
 
 ## Configuration (secrets)
 
@@ -340,7 +204,8 @@ every outpost session (see the ORM playbook).
    Applications** → add an application + a **Proxy** provider whose
    `external_host` is exactly the browser-facing origin
    (`https://<host>`), `internal_host = http://caddy:8017`, and **all three**
-   flows set (see the provisioning pitfall above). Attach the provider to the
+   flows set (see the provisioning rules in
+   [[Authentik Outpost Reference]]). Attach the provider to the
    embedded outpost.
 4. For apps with native OIDC: add an **OAuth2/OpenID Connect** provider, create
    the app with the correct redirect URI, and paste the `client_id` /
@@ -373,47 +238,6 @@ every outpost session (see the ORM playbook).
   the LDAP section) — bumping only the tag would leave the LDAP outpost behind.
   Authentik migrates the schema on startup.
 
-## Self-serve user-settings flow (password change)
-
-Users change their own account details through the `default-user-settings-flow`
-(`https://auth.franksdank.cloud/if/flow/default-user-settings-flow/`) — the
-target of the homepage footer's "account" link. It is a `stage_configuration`
-designated flow, so it renders every bound `ConfigurableStage` for the logged-in
-user.
-
-Stages, in execution order (the `FlowStageBinding.order` field, not the M2M
-insertion order):
-
-| order | stage | type | what it does |
-|---|---|---|---|
-| 20 | `default-user-settings` | `PromptStage` | name / email / locale **+ password** |
-| 100 | `default-user-settings-write` | `UserWriteStage` | writes the prompt data to the user |
-
-**Password change is a prompt field, not a stage.** The `UserWriteStage`
-writes whatever the preceding `PromptStage` collected: for the key `password`
-it calls `user.set_password(value)` (`stages/user_write/stage.py`). So the fix
-is a `password` field on the `default-user-settings` prompt
-(`field_key=password`, `type=password`, `required=False`, order 204) — NOT a
-`PasswordStage`. A `PasswordStage` is an *authentication* stage: its
-`validate_password` runs `authenticate()` against the backends to check the
-*current* password; it never sets a new one. (A `PasswordStage` was added on
-2026-09-25 and removed the same day for exactly this reason.)
-
-Two ORM gotchas: `Flow.stages.add()` fails on this through model
-(`Can't bulk create a multi-table inherited model` — `FlowStageBinding` is
-MTI), so create the `FlowStageBinding` row directly with an explicit `order`;
-and a prompt field is a `Prompt` row linked through `PromptStageField`
-(`prompt_stage` + `prompt`; the order comes from `Prompt.order`).
-
-**A blank password must not set an empty password.** `set_password("")` would
-make the account log in with no password, so a validation policy
-(`default-user-settings-no-empty-password`, bound to the prompt via
-`PromptStageValidationPolicy`) denies the form when `prompt_data["password"]`
-is `""` and allows it when set. Verified with the `PolicyEvaluator`
-(empty → deny, set → allow, absent → allow) and end-to-end by driving
-`UserWriteStageView.update_user` on a throwaway user (new password valid, old
-invalid).
-
 ## Outpost claim cache (`proxysession`) — 403 after a group add
 
 The embedded outpost does not re-evaluate group membership per request. Each
@@ -457,7 +281,7 @@ client → TLS edge → Anubis :8923 → outpost decision → internal
    (the inventory table carries both bare origins and trailing slashes;
    routing matches on hostname, verified 2026-09-02).
    `internal_host = http://caddy:8017`, all three flows set, and an
-   Application attached — the two provisioning rules above.
+   Application attached — the two provisioning rules in [[Authentik Outpost Reference]].
 2. **Route flip in ONE commit/deploy**: the vhost becomes
    `reverse_proxy anubis:8923` with `header_up X-Real-Ip {remote_host}`, and
    inside the `http://:8017` listener add `@<svc> host <vhost>` +
@@ -521,22 +345,9 @@ EOF
   is no `authentik.policies.group` module in this build.
   *(unverified 2026-10-18: these module paths were not re-executed — importing
   outside a configured Django shell fails with `ImproperlyConfigured`)*
-- For live DB truth prefer the postgres container, and it works without any
+- The live database's table and column names (the 2026.x renames, the MTI parent
-  credential — the local socket is trusted, so a read-only audit is just
+  keys, the read-only `psql` audit recipe) are reference lookup:
-  `podman exec -i authentik-postgres psql -U authentik -d authentik -At -f -`
+  [[Authentik Outpost Reference]].
-  with SQL on stdin (quoting SQL through ssh+zsh otherwise fights you). Verify
-  before guessing: 2026.x renamed both tables and columns, and the models are
-  MTI all the way down — `authentik_core_provider` holds `id`, `name` and the
-  three `*_flow_id` columns; the proxy table is
-  `authentik_providers_proxy_proxyprovider` (doubled `proxy`) and its PK column
-  really is **`oauth2provider_ptr_id`** (proxy providers inherit the OAuth2
-  table in 2026.8), the LDAP table is
-  `authentik_providers_ldap_ldapprovider` with PK `provider_ptr_id`;
-  `authentik_core_application` attaches to a provider through `provider_id`
-  (its PK is `policybindingmodel_ptr_id`, not `id`), and `authentik_outposts_outpost`
-  is keyed by `uuid`. So `Provider.objects.filter(type=…)` raising `FieldError`
-  is the same story from the ORM side: `type` lives in the subclass tables.
-  Never select secret columns (`client_secret`, `key`, `password`) into a log.
 
 ## User provisioning playbook (user-level account)
 

serverAppConfigs-docs/Infrastructure/Grafana.md

@@ -69,7 +69,7 @@ Grafana responds on `/api/health` with 200 and `"database":"ok"`; measured 2026-
   client_id `grafana-21ca190cde75d60f`, global authorize/token/userinfo paths,
   Basic client auth, form-encoded token body, and the fork's userinfo-claims
   bug that leaves identity at the `sub` hash only) is in
-  [[Authentik]] → "OAuth2 relying-party quirks". Consequences for Grafana:
+  [[Authentik Outpost Reference]] → "OAuth2 relying-party quirks". Consequences for Grafana:
   The unit sets `ALLOW_SIGN_UP=false`, `AUTO_UPSERT=true`, `ALLOW_ASSIGN_ORG=true`,
   `ORG_ID=1` and **no** role-attribute mapping (`grafana.container:52-55`), so
   users land as Viewer with `login = <sub hex>`; no email/groups/role claims

serverAppConfigs-docs/Infrastructure/Homepage Status Probes.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Homepage Status Probes
-description: The homepage TUI status page — how probe targets are chosen (host-netns vantage), the three false-down shapes, triage procedure, local render check, deploy, and the e2e gate interactions (asleep Mac mini, raw-IP matrix).
+description: "How probe targets are chosen, the three false-down shapes, the triage procedure, and the e2e gate interactions."
 tags: [homepage, status, probes, e2e, homepage-status]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/Infrastructure/Homepage.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "A password-protected web site on Dankclaw lists the services that are up, with a short description of each and a link to both the service and its usage documentation."
+description: "The password-protected service list on Dankclaw: what each card shows and where its data comes from."
 tags:
   - infrastructure
   - homepage

serverAppConfigs-docs/Infrastructure/Observability Provisioning.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Observability Provisioning
-description: How Prometheus config/rules and Grafana datasources/dashboards are provisioned as code in serverAppConfigs — the config triad, deploy copiers, planner mappings, seam tests, entry points for each change type, and API verification.
+description: "Monitoring config as code: the config triad, deploy copiers, planner mappings, and where each change type lands."
 tags: [observability, prometheus, grafana, provisioning, deployment]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/Infrastructure/Observability.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: "Observability on Dankclaw"
-description: "The Dankclaw observability stack — Prometheus, Grafana, Loki, Alloy, node-exporter and Alertmanager (Signal delivery): what runs, how it is deployed, how it is exposed, and what is still unconfigured."
+description: "The observability stack: what runs, how it is deployed, how it is exposed, and what is still unconfigured."
 tags: [observability, prometheus, grafana, loki, alloy, node-exporter, quadlet, dankclaw]
 timestamp: 2026-09-11
 ---

serverAppConfigs-docs/Infrastructure/Prometheus.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "Prometheus collects metrics from every service on Dankclaw by scraping their `/metrics` endpoints, and feeds the provisioned Grafana datasource. Down targets today are structural, not outages."
+description: "Scrapes each service's metrics endpoint and feeds the provisioned Grafana datasource; down targets are structural."
 tags:
   - infrastructure
   - prometheus

serverAppConfigs-docs/Infrastructure/authentik-postgres.md

@@ -1,24 +0,0 @@
----
-type: reference
-description: "The PostgreSQL 16 database for [Authentik](Authentik.md) — the homelab's SSO /"
-tags:
-  - infrastructure
-  - authentik
-  - postgres
-timestamp: 2026-08-28
----
-
-# authentik-postgres
-
-The PostgreSQL 16 database for [Authentik](Authentik.md) — the homelab's SSO /
-OIDC provider. It is the only stateful store in the stack (users, flows,
-sessions, events). Redis was removed in Authentik 2025.10; sessions and caching
-now live here.
-
-- **Compose service:** `authentik-postgres` (in `dankclaw/compose.yaml`)
-- **Image:** `docker.io/library/postgres:16-alpine`
-- **Data:** `/home/dank/authentik/postgres` (bind mount; no named volumes)
-- **Health:** `pg_isready -d authentik -U authentik`
-
-See [Authentik.md](Authentik.md) for the full architecture, setup, backups
-(`pg_dump`), and failure modes.

serverAppConfigs-docs/Infrastructure/authentik-server.md

@@ -1,24 +0,0 @@
----
-type: reference
-description: "The Authentik server — the core, the admin API, and the embedded Caddy outpost."
-tags:
-  - infrastructure
-  - authentik
-timestamp: 2026-09-16
----
-
-# authentik-server
-
-The Authentik server — the core, the admin API, and the embedded Caddy outpost.
-This is the service the Caddy `forward_auth` vhosts proxy to
-(`authentik-server:9000`). It also serves the login page at
-`https://auth.franksdank.cloud`.
-
-- **Unit:** `dankclaw/authentik/quadlet/authentik-server.container` (`authentik-server.service`)
-- **Image:** `ghcr.io/goauthentik/server:2026.8.3` (command: `server`)
-- **Port:** `9000` (published; the outpost + admin + login all live here)
-- **Data:** `/home/dank/authentik/data` (bind mount, shared with the worker)
-- **Health:** `http://localhost:9000/-/health/`
-
-See [Authentik.md](Authentik.md) for the full architecture, the Caddy
-forward_auth pattern, first-time setup, and failure modes.

serverAppConfigs-docs/Infrastructure/authentik-worker.md

@@ -1,23 +0,0 @@
----
-type: reference
-description: "The Authentik worker — background tasks: event processing, provider"
-tags:
-  - infrastructure
-  - authentik
-timestamp: 2026-09-16
----
-
-# authentik-worker
-
-The Authentik worker — background tasks: event processing, provider
-synchronization, scheduled flows, and certificate renewal. It runs the same
-image as the server; the `command: worker` selects the role.
-
-- **Unit:** `dankclaw/authentik/quadlet/authentik-worker.container` (`authentik-worker.service`)
-- **Image:** `ghcr.io/goauthentik/server:2026.8.3` (command: `worker`)
-- **Runs as:** `0:0` (rootless: container root maps to the host user that owns the data dir)
-- **Data:** `/home/dank/authentik/data` (bind mount, shared with the server)
-- **No port** — the worker has no HTTP endpoint.
-
-See [Authentik.md](Authentik.md) for the full architecture, setup, and failure
-modes.

serverAppConfigs-docs/LLM/DFlash DSpark Speculative Decoding.md

@@ -411,7 +411,7 @@ measurement that would settle it.
 
 - Speculative decoding helps low-QPS, memory-bound, latency-focused workloads. It helps less at high QPS.
 - DFlash needs a non-causal attention backend; the ROCm flash_attn backend must be validated before production use.
-- The old `--swap-space` flag no longer exists in current vLLM. Use `--kv-offloading-size`.
+- The old `--swap-space` flag is retired; the live CPU-KV-offload knob pair is owned by [[RAM CPU Offloading in VLLM]].
 - `--speculative-config` is the preferred CLI. Legacy `--spec-method`, `--spec-model`, and `--spec-tokens` flags still exist.
 - Use `rejection_sample_method` default `strict` for lossless output.
 

serverAppConfigs-docs/LLM/Dankserver System Specs.md

@@ -1,7 +1,7 @@
 ---
-type: configuration
+type: reference
 title: Dankserver System Specs
-description: Dankserver hardware and OS state since the 2026-09-20 board swap (ASUS ProArt B850-Creator WiFi NEO, 2x AMD Radeon AI PRO R9700 gfx1201 on CPU lanes x8/x8) serving frank-medium.
+description: "Dankserver hardware and OS state since the board swap: board, lane topology, cards, memory, kernel posture."
 tags:
   - dankserver
   - hardware

serverAppConfigs-docs/LLM/Dual-R9700-Cooperation.md

@@ -1,7 +1,7 @@
 ---
-type: research
+type: reference
 title: Dual R9700 Cooperation
-description: Why frank-medium's two Radeon AI PRO R9700s could not run tensor-parallel on the old B650-E board (PCIe atomic routing), what the 2026-09-20 ProArt B850-Creator swap unblocked, and what still has to be probed.
+description: "Why two R9700s could not run tensor-parallel on the old board, and what the board swap unblocked."
 tags:
   - frank-medium
   - rocm

serverAppConfigs-docs/LLM/FastFlowLM NPU Inference.md

@@ -1,7 +1,7 @@
 ---
-type: research
+type: reference
 title: FastFlowLM NPU Inference
-description: FastFlowLM (FLM), the AMD NPU-first LLM runtime for Ryzen AI XDNA2 chips. Fit analysis for the 50 TOPS NPU on Dankclaw, published benchmarks, verified install state, and a test runbook.
+description: "The AMD NPU-first runtime: fit analysis for the XDNA2, published benchmarks, install state, and test runbook."
 tags:
   - fastflowlm
   - npu
@@ -57,7 +57,10 @@ Key properties, per the project README and docs:
 
 ## NPU Hardware on Dankclaw
 
-Dankclaw runs an AMD Ryzen AI MAX+ 395 (Strix Halo). The chip integrates an XDNA2 NPU rated at 50 TOPS (vendor spec: "NPU TOPS — Up to 50 TOPS", [amd.com product page](https://www.amd.com/en/products/processors/laptop/ryzen/ai-300-series/amd-ryzen-ai-max-plus-395.html)). It sits beside the Radeon 8060S iGPU and shares the same unified memory pool — 30 GiB exposed to the OS in the 2026-08 reading below; the box presents **121 GiB** today (`free -g` total 121, read 2026-10-18).
+Dankclaw runs an AMD Ryzen AI MAX+ 395 (Strix Halo). The chip integrates an XDNA2 NPU
+with 50 TOPS of compute and, crucially, **no dedicated VRAM** - it shares system memory
+via the IOMMU SVA mapping. The budget this page reasons about - 29 GiB usable at
+4800 MT/s LPDDR5X - is the 2026-08 host state; the live figure is [[Dankclaw System Specs]].
 
 Live verification on Dankclaw, 2026-08-16:
 
@@ -89,10 +92,9 @@ Budget math for this fleet:
 | Dankserver (Ryzen 7 7700X) | 62 GB | no NPU |
 | FLM bench box (Kraken Point) | 32 or 96 GB | ~16 or ~48 GB |
 
-2026-10-18 re-read: Dankclaw's OS now reports **121 GiB** (`free -g`) and
+The half-of-RAM gate scales with host RAM - live figures in [[Dankclaw System Specs]]
-Dankserver **246 GiB** (`free -g`), so the half-of-RAM rule would price the NPU
+and [[Dankserver System Specs]]. The live gate on Dankclaw is still `flm validate`
-budget at ~60 GiB and the 7700X box still has no NPU. The 30 GiB / 62 GB rows
+(it owns the current number).
-are the 2026-08-16 state; the table is moot while no NPU endpoint is deployed.
 
 Weight sizes (approximate, Q4-class):
 
@@ -159,7 +161,10 @@ Qwen3.6-35B-A3B (Q4_KS), FLM v0.9.45, Kraken Point **96 GB DRAM**:
 | Decode t/s | 13.65 | 13.41 | 13.09 | 12.51 | 11.24 | 9.51 |
 | Prefill t/s | 78.98 | 118.04 | 156.43 | 197.93 | 218.84 | 221.96 |
 
-Context: the current PP split (head + 3090 worker) decodes at 14-18 t/s for the 27B dense model. A 35B-A3B at ~10-14 t/s on an NPU with 48 GB of RAM budget is not a speed win over the existing topology.
+- PP and NPU together cost 2.2 GiB + NPU model + ~2 GiB of headroom. The then-current
+  PP split (head + 3090 worker, 2026-08 era - see [[frank-redo-2026-08-17]]) decoded at
+  14-18 t/s for the 27B dense model, so an NPU offload would free the head or upgrade
+  the worker's model.
 
 The vendor also claims "over 10x more power-efficient" versus GPU. That is a marketing claim. We have not measured it.
 
@@ -219,7 +224,12 @@ Notes:
 
 ## Promotion (2026-08-16)
 
-`frank-zealot` now runs the NPU endpoint on Dankclaw (was the Dankserver llama.cpp service). Unit: `scripts/frank-zealot.service` (symlinked into `/etc/systemd/system`), wrapper `scripts/serve-flm-small.sh`, tunables `scripts/frank-zealot.env`. `LimitMEMLOCK=infinity` is set in the unit. Default model: `gemma4-it:e4b`. Swap `FLM_MODEL` in the env to switch.
+`frank-zealot` then ran the NPU endpoint on Dankclaw (2026-08; the name was reused
+twice after this window - see the banner - and the NPU unit today is `frank-npu`,
+masked). Unit: `scripts/frank-zealot.service` (symlinked into `/etc/systemd/system`),
+wrapper `scripts/serve-flm-small.sh`, tunables `scripts/frank-zealot.env`.
+`LimitMEMLOCK=infinity` is set in the unit. Default model: `gemma4-it:e4b`. Swap
+`FLM_MODEL` in the env to switch.
 
 ### Boot policy (2026-08-17)
 
@@ -256,11 +266,13 @@ The 4-stream wall times form a near-perfect 10.7 s ladder. Each stream self-repo
 Consequence: the NPU endpoint is a single lane. It suits low-frequency background work (triage, summarization, agent side-tasks). It does not suit interactive chat for several simultaneous users. The 27B llama.cpp service, by contrast, runs PARALLEL=2 with true concurrent slots.
 
 ## Test Runbook
-
 This runbook targets a retired endpoint; keep it as the procedure if the NPU is
-ever revived. Do not run large model loads while the production service holds
+ever revived.
-most of the unified pool — 30 GiB exposed to the OS in the 2026-08 reading,
+
-**121 GiB** today (`free -g`, read 2026-10-18). Check free RAM first, or stop
+**Host RAM availability.** The gate is half of system RAM by default - a relic of the
+install: the endpoint ran on a machine that presented 30 GiB of system RAM; on today's
+box that ceiling is far larger (live figure: [[Dankclaw System Specs]]). Check free RAM
+first, or stop
 the service the way the bench policy requires (`sudo systemctl stop
 frank-dragoon && sudo systemctl mask frank-dragoon` — self-healing would
 otherwise restart it). The NPU shares the unified pool with everything else on

serverAppConfigs-docs/LLM/FreeToken Builds.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: FreeToken Builds
-description: Building FreeToken (the official franksdank fork of FreeTok Tokenworks' freetoken vLLM-MTP runtime) on Dankclaw — the CUDA vLLM venv build and the ROCm build, with the dependency traps each one hit.
+description: "Building the FreeToken runtime here: the CUDA and ROCm builds and the dependency trap each one hit."
 tags: [freetoken, build, dankclaw, vllm, mtp]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/LLM/GGUF Compatibility.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: GGUF Compatibility and Runtime Lock-in
-description: How to answer "will engine X load this GGUF?" from the file's header alone, why a custom tensor type forces the runtime, and the discipline for pinning a fork build that can actually serve the file.
+description: "Answering whether an engine loads a GGUF from the file header alone, and pinning a fork build that can."
 tags: [gguf, llama.cpp, forks, quantization, speculative]
 timestamp: 2026-10-05T00:00:00-07:00
 ---
@@ -119,5 +119,6 @@ re-download.
 
 - [[Llama Cpp Runtimes]] — which fork ships which custom types
 - [[Llama Cpp Code Diff]] — the enum tables and code-level differences
-- [[frank-dragoon]] — the ftype-115 lock-in in production
+* [[kingjones-q8agent-rocmfpx]] — the era that served the ftype-115 file, and
+  [[frank-dragoon]] for what runs there now
 - [[Llama Cpp Serving Sizing]] — pricing what a payload costs once it loads

serverAppConfigs-docs/LLM/Heterogeneous Split Triage.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Heterogeneous Split Triage
-description: Triage before building when someone asks to split a model across unequal accelerators on one host (24 GB GDDR6X + LPDDR APU, PCIe x4 link) — link characterisation, the real bottleneck, what placement never buys, UMA pools, drafter splits, and the verdict ranking.
+description: "Triage before splitting across unequal accelerators: link characterisation, real bottleneck, what placement never buys."
 tags: [heterogeneous, multi-device, llama-cpp, triage, pcie]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/LLM/Hybrid CPU GPU Processing Dankserver.md

@@ -56,7 +56,10 @@ Lower values leave more GPU memory for KV cache. This reduces swap frequency.
 
 ### Swap Space / KV Offload
 
-Recent vLLM releases removed the `--swap-space` engine argument — `CacheConfig` on `main` has no `swap_space` field ([source](https://raw.githubusercontent.com/vllm-project/vllm/main/vllm/config/cache.py), read 2026-10-18). Use `--kv-offloading-size` (`kv_offloading_size`, same file) to move KV cache to CPU RAM. In Podman, mount the host cache read-write for KV offload writes. The table below shows historical `--swap-space` guidance as a sizing reference.
+Current vLLM has no `--swap-space` engine argument, and the CPU KV-offload knob pair
+is owned by [[RAM CPU Offloading in VLLM]] (that page carries the upstream
+`CacheConfig` verification). In Podman, mount the host cache read-write for KV offload
+writes. The table below shows historical `--swap-space` guidance as a sizing reference.
 
 | System RAM | Recommended Swap |
 |------------|------------------|

serverAppConfigs-docs/LLM/LLM Bench Windows and Measurement.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: LLM Bench Windows and Measurement
-description: Stopping-and-restoring benchmark windows on the fleet LLM hosts (llama-bench sweeps, HTTP param benches, multi-arm vLLM offload sweeps), honest benchmark methodology, and the usage-counter measurement law under speculative decoding.
+description: "Opening and restoring benchmark windows on fleet hosts, honest methodology, and the usage-counter law under drafting."
 tags: [benchmarking, llama-bench, ab-testing, speculative, vllm, fleet]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/LLM/LLM Performance Diagnosis.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: LLM Performance Diagnosis
-description: Probing why a served LLM is slow — the flat-depth probe, the expert-offload duty-cycle arithmetic, kernel-time attribution via the profiler window, live telemetry without benchmarking, RAM-bandwidth ceilings, IBS tensor attribution and prefix-cache-aware routing.
+description: "Probing why a served model is slow: the flat-depth probe, offload duty-cycle arithmetic, and profiler attribution."
 tags: [performance, profiling, moe, pcie, prefix-cache, routing, telemetry]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/LLM/Llama Cpp Multi-Device Splits.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Llama Cpp Multi-Device Splits
-description: What llama.cpp can and cannot express across devices, the no-collective layer-split path, split balancing by measurement, drafter KV sizing from GGUF headers, and heterogeneous placement triage.
+description: "What llama.cpp can express across devices: the no-collective layer-split path, balancing, and drafter KV sizing."
 tags: [llama.cpp, multi-gpu, layer-split, pcie, sizing, speculative]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/LLM/Llama Cpp Serving Sizing.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Llama Cpp Serving Sizing
-description: Slot-pool sizing against a headroom band, per-device VRAM accounting, prompt-cache/state sizing and the QSA flash-attn fix — the measurement-first procedures for llama.cpp serving shapes.
+description: "Measurement-first sizing for llama.cpp shapes: slot pools against a headroom band, per-device accounting, prompt cache."
 tags: [llama.cpp, vram, kv-cache, slots, flash-attn, sizing]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/LLM/Model Swap and Rollback.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Model Swap and Rollback
-description: The full model-swap discipline for the LLM fleet — fit preflight, fetch and payload verification, runtime build/flag checks, git-only config, live validation, systemd handoff, close-out, the three-pin revert law, and research-verification discipline.
+description: "The model-swap discipline: fit preflight, fetch verification, build and flag checks, live validation, three-pin revert."
 tags: [models, swap, gguf, huggingface, rollback, deployment, verification]
 timestamp: 2026-10-05T00:00:00-07:00
 ---
@@ -40,9 +40,9 @@ curl -s <health>                                      # then a REAL completion
 ```
 
 Deploy caveat: "healthy after Ns" = systemd ACTIVE, not model LOADED —
-confirm with a real `/v1/chat/completions`. RTX 3090 (Ampere) has no
+confirm with a real `/v1/chat/completions`. On Ampere an FP8 file buys memory
-FP8/FP4 tensor cores: FP8 weights run via upcast but must still fit; choose
+and no compute ([[Quantization by Hardware Architecture]]): choose the quant by
-quant by size fit, then accept the compute path the card supports. Before
+size fit, then accept the compute path the card supports. Before
 choosing a smaller quant, state WHICH of the two you are buying — headroom,
 or a design change (a smaller quant does not change what the runtime can
 express; per-tensor cross-device placement stays refused under
@@ -60,8 +60,8 @@ express; per-tensor cross-device placement stays refused under
 ## 3. Fetch and verify (HF payloads)
 
 **Inventory by QUANT NAME, never by extension** — large quants ship as
-`.partNofM` fragments (Q4_K_M = 37.00+37.00+36.97 GiB), so an
+`.partNofM` fragments, so an `endswith(".gguf")` filter makes a whole rung look
-`endswith(".gguf")` filter makes Q4_K_S look nonexistent. Check both
+nonexistent (AGENTS.md carries the worked fragment ledger). Check both
 mradermacher repos (`…-i1-GGUF` imatrix, `…-GGUF` plain) and the model's own
 repo; the tree API's `blobs=true` gives `lfs.oid` per file. Gated mirrors
 return 403 even with a valid token until the account accepts the gate —
@@ -150,7 +150,7 @@ recoverable, drift is not.
    entry in `serverAppConfigs-docs/log.md`.
 2. `~/.omp/agent/models.yml`: `contextWindow` must equal the REAL per-slot
    context — llama.cpp logs `n_ctx_slot` per prompt (`--parallel N` divides
-   the pool; e.g. 262144 native / 2 slots = 131072 per slot); vLLM reports
+  the pool; e.g. a 524288 pool over 2 slots = 262144 per slot); vLLM reports
    `max-model-len` and its concurrency line. Overselling causes silent
    client-side overflow or a discovered-wall 400. Also `maxTokens` vs the
    engine's cap, `input` capabilities (text/image), and
@@ -252,12 +252,10 @@ small/fast + image roles at the new endpoint; move the vision role WITH the
 vision tower (one owner per capability). `shared/homepage/services.json`: a
 card per endpoint, probed from the monitor's own host. Prometheus: only add
 a job if the runtime actually exposes Prometheus text — and re-measure rather
-than repeat, because that answer moves. This bullet once said halogen serves
+than repeat, because that answer moves: halogen's HTTP surface has grown twice
-`/health`, `/cache`, `/v1/*` "and nothing else"; measured 2026-10-18 on
+since this page was written, and the endpoint list that matters for a scrape
-Dankclaw, `curl -s http://127.0.0.1:7770/metrics` returns Prometheus text
+target — including whether `/metrics` answers — is [[frank-dragoon]]'s wire
-(`# HELP llamacpp:prompt_tokens_total …`, content-type
+contract.
-`text/plain; version=0.0.4`) while an invented path 404s — so the surface has
-grown and a scrape target is expressible again.
 
 **4. Cutover, then verify by driving it.** `deploy.sh <target> --service
 <large> --service <small>` (order matters); per endpoint: `/health`,
@@ -265,10 +263,10 @@ grown and a scrape target is expressible again.
 `reasoning_content`, a `tools` request returns `tool_calls`, an image
 request is answered (or refused with a named reason), the runtime's own
 speculation counters move, and the unit is `enabled` and `active`. All three LLM
-endpoints are **root** units today (`User=dank` + `WantedBy=multi-user.target` —
+endpoints are **root** units today (`scripts/frank-archon.service`,
-`scripts/frank-archon.service:30,71`, `scripts/frank-dragoon.service:8,31`,
+`scripts/frank-dragoon.service`, `scripts/frank-zealot.service`), so linger is
-`scripts/frank-zealot.service:8,26`), so linger is not what gates them; linger
+not what gates them; linger matters for rootless quadlets. Read the engine's boot
-matters for rootless quadlets. Read the engine's boot ledger for a silent clamp. Finally spend one
+ledger for a silent clamp. Finally spend one
 real request through the harness per changed role — routing labels lie; the
 servers' own journals do not.
 
@@ -285,4 +283,5 @@ predecessor "stopped" (the port race above).
 - [[Llama Cpp Serving Sizing]] — pricing the shape once it loads
 - [[RDNA4 MoE Expert Offload VRAM Budget]] — vLLM-side fit arithmetic
 - [[LLM Bench Windows and Measurement]] — measuring the new deployment
-- [[frank-archon]] — the retired tcclaviger vLLM endpoint (2026-09-29 → 10-05); the live Dankserver endpoint is [[frank-archon]]
+* [[frank-archon]] — the live Dankserver endpoint; the tcclaviger vLLM era
+  (2026-09-29 → 10-05) is a row in its Eras table

serverAppConfigs-docs/LLM/PCIe Link and Atomics.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: PCIe Link and Atomics
-description: Link probing (idle downshift, path ceilings, CUDA/HIP bandwidth probes), the streaming-vs-compute ceiling arithmetic, and the PCIe-atomics wall that decides whether AMD multi-GPU collectives can exist at all.
+description: "Link probing, the streaming-versus-compute ceiling arithmetic, and the atomics wall that decides multi-GPU collectives."
 tags: [pcie, rccl, atomics, multi-gpu, bandwidth, amd, nvidia]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/LLM/Pipeline Parallelism/Ethernet Bandwidth Math.md

@@ -1,11 +1,11 @@
 ---
 type: reference
 title: Ethernet Bandwidth Math
-description: Bytes-per-token math for pipeline vs tensor parallelism, feasibility tables for 1/2.5/10 GbE, and real multi-node benchmark numbers.
+description: "Bytes-per-token math for pipeline versus tensor parallelism, and the link budgets that follow from it."
 tags:
   - pipeline-parallelism
   - research
-timestamp: 2026-08-17
+timestamp: 2026-10-19
 ---
 
 # Bandwidth Analysis: Multi-Node LLM Inference over Ethernet
@@ -147,19 +147,11 @@ bytes_per_boundary = batch_size × hidden_size × 2   [fp16 = 2 bytes]
 - Per-token, per-boundary: `6144 × 2 = 12,288 bytes = 12 KB`
 - With Nₚₚ stage boundaries: total = `Nₚₚ × 12 KB/tok`
 
-**Full example — 27B model, 2 PP stages (1 boundary), batch=1:**
+**Worked examples (1 boundary = 2 PP stages):**
 ```
-1 boundary × 4096 × 2 bytes = 8,192 bytes/tok
+27B, batch=1:  1 boundary × 4096 × 2      bytes = 8,192 bytes/tok  = 8 KB
-```
+27B, batch=64: 1 boundary × 4096 × 64 × 2 bytes = 524,288          = 512 KB/tok
-
+36B, batch=1:  1 boundary × 6144 × 2      bytes = 12,288 bytes/tok = 12 KB
-**Example — same model, batch=64:**
-```
-1 boundary × 4096 × 64 × 2 bytes = 524,288 bytes = 512 KB/tok
-```
-
-**Example — 36B model, 2 PP stages, batch=1:**
-```
-1 boundary × 6144 × 2 bytes = 12,288 bytes = 12 KB/tok
 ```
 
 ### 1.2 Tensor Parallelism (TP) — for comparison
@@ -244,57 +236,13 @@ total_bytes_per_tok = L × batch_size × hidden_size × 2   [L all-reduces total
 | 50 | 10.24 Mbit/s | 163.84 Mbit/s | 655.36 Mbit/s |
 | 100 | 20.48 Mbit/s | 327.68 Mbit/s | 1,310.72 Mbit/s |
 
-### 2.3 Feasibility matrix
+### 2.3 Feasibility
 
-Green = feasible (< 50% of link capacity). Yellow = marginal (50–90%). Red = saturated (> 90%).
+Thresholds: **feasible** = under 50% of link capacity, **marginal** = 50–90%,
-
+**saturated** = over 90%. Cross-checking §2.2 against §2.1: every PP case is
-**27B model — PP (1 boundary), batch=1:**
+feasible on every link class — even the heaviest, 27B at batch=64 and 100
-
+tok/s (81.92 Mbit/s), is feasible on 1 GbE — and every TP case is feasible
-| | 1 GbE (118 MB/s) | 2.5 GbE (294 MB/s) | 10 GbE (1175 MB/s) |
+except batch=64:
-|---|---|---|---|
-| 10 tok/s | ✅ 0.13 Mbit/s | ✅ 0.13 Mbit/s | ✅ 0.13 Mbit/s |
-| 50 tok/s | ✅ 0.65 Mbit/s | ✅ 0.65 Mbit/s | ✅ 0.65 Mbit/s |
-| 100 tok/s | ✅ 1.31 Mbit/s | ✅ 1.31 Mbit/s | ✅ 1.31 Mbit/s |
-
-**27B model — PP (1 boundary), batch=16:**
-
-| | 1 GbE | 2.5 GbE | 10 GbE |
-|---|---|---|---|
-| 10 tok/s | ✅ 2.05 Mbit/s | ✅ 2.05 Mbit/s | ✅ 2.05 Mbit/s |
-| 50 tok/s | ✅ 10.24 Mbit/s | ✅ 10.24 Mbit/s | ✅ 10.24 Mbit/s |
-| 100 tok/s | ✅ 20.48 Mbit/s | ✅ 20.48 Mbit/s | ✅ 20.48 Mbit/s |
-
-**27B model — PP (1 boundary), batch=64:**
-
-| | 1 GbE | 2.5 GbE | 10 GbE |
-|---|---|---|---|
-| 10 tok/s | ✅ 8.19 Mbit/s | ✅ 8.19 Mbit/s | ✅ 8.19 Mbit/s |
-| 50 tok/s | ✅ 40.96 Mbit/s | ✅ 40.96 Mbit/s | ✅ 40.96 Mbit/s |
-| 100 tok/s | ✅ 81.92 Mbit/s | ✅ 81.92 Mbit/s | ✅ 81.92 Mbit/s |
-
-**27B model — TP (32 layers), batch=1:**
-
-| | 1 GbE | 2.5 GbE | 10 GbE |
-|---|---|---|---|
-| 10 tok/s | ✅ 2.05 Mbit/s | ✅ 2.05 Mbit/s | ✅ 2.05 Mbit/s |
-| 50 tok/s | ✅ 10.24 Mbit/s | ✅ 10.24 Mbit/s | ✅ 10.24 Mbit/s |
-| 100 tok/s | ✅ 20.48 Mbit/s | ✅ 20.48 Mbit/s | ✅ 20.48 Mbit/s |
-
-**27B model — TP (32 layers), batch=16:**
-
-| | 1 GbE | 2.5 GbE | 10 GbE |
-|---|---|---|---|
-| 10 tok/s | ✅ 32.77 Mbit/s | ✅ 32.77 Mbit/s | ✅ 32.77 Mbit/s |
-| 50 tok/s | ✅ 163.84 Mbit/s | ✅ 163.84 Mbit/s | ✅ 163.84 Mbit/s |
-| 100 tok/s | ✅ 327.68 Mbit/s | ✅ 327.68 Mbit/s | ✅ 327.68 Mbit/s |
-
-**27B model — TP (32 layers), batch=64:**
-
-| | 1 GbE | 2.5 GbE | 10 GbE |
-|---|---|---|---|
-| 10 tok/s | ✅ 131.07 Mbit/s | ✅ 131.07 Mbit/s | ✅ 131.07 Mbit/s |
-| 50 tok/s | ✅ 655.36 Mbit/s | ✅ 655.36 Mbit/s | ✅ 655.36 Mbit/s |
-| 100 tok/s | ✅ 1310.72 Mbit/s | ✅ 1310.72 Mbit/s | ✅ 1310.72 Mbit/s |
 
 **27B TP batch=64 at 100 tok/s: 1310.72 Mbit/s > 1 GbE usable (1000 Mbit/s) — link-saturated on 1 GbE**
 
@@ -368,10 +316,7 @@ With TP, each layer transfers `H × 2` bytes but this happens L times. For 256 K
 **Petals [1]:**
 - Uses pipeline parallelism with dynamic 8-bit quantization (halves bandwidth)
 - For BLOOM-176B (H=14336), per-boundary communication is ~14 KB/tok with quantization
-- Recommended bandwidth: 25 Mbit/s bidirectional for interactive inference [1]
 - Key finding: "For inference, performance does not depend much on bandwidth or sequence length but degrades with higher latency" — RTT matters more than throughput
-- At 1 Gbit/s with <5 ms RTT: 1.71 steps/s; at 100 Mbit/s with <5 ms: 1.66 steps/s (only 3% difference)
-- At 100 Mbit/s with 100 ms RTT: 1.23 steps/s (28% degradation)
 
 **llama.cpp RPC [2]:**
 - Model weights and KV cache distributed across nodes proportionally to memory
@@ -493,38 +438,17 @@ With Nₚₚ = 4 and 30 µs per-hop RTT: ~120 µs network, still <6% of compute
 
 ## Appendix: Full bandwidth formulae
 
-### Pipeline Parallelism (generation, batch=1)
+### Pipeline and Tensor Parallelism (generation)
+
+`N` is the batch size; `N = 1` is the batch=1 form.
 
 ```
-bytes_per_boundary_per_tok = hidden_size × 2   [fp16]
+bytes_per_boundary_per_tok = hidden_size × N × 2              [fp16, PP boundary]
-total_bytes_per_tok = num_boundaries × hidden_size × 2
+bytes_per_layer_allreduce  = hidden_size × N × 2              [TP, one all-reduce per layer]
+total_bytes_per_tok = num_boundaries × hidden_size × N × 2    [PP]
+total_bytes_per_tok = num_layers      × hidden_size × N × 2   [TP]
 bandwidth_mbps = total_bytes_per_tok × tokens_per_second × 8 / 1,000,000
-```
 
-### Pipeline Parallelism (generation, batch=N)
+# With 8-bit quantization (like Petals): simply divide all fp16 byte counts by 2
-
-```
-bytes_per_boundary_per_tok = hidden_size × N × 2
-total_bytes_per_tok = num_boundaries × hidden_size × N × 2
-```
-
-### Tensor Parallelism (generation, batch=1)
-
-```
-bytes_per_layer_allreduce = hidden_size × 2
-total_bytes_per_tok = num_layers × hidden_size × 2
-bandwidth_mbps = total_bytes_per_tok × tokens_per_second × 8 / 1,000,000
-```
-
-### Tensor Parallelism (generation, batch=N)
-
-```
-total_bytes_per_tok = num_layers × hidden_size × N × 2
-```
-
-### With 8-bit quantization (like Petals)
-
-```
-# Simply divide all fp16 byte counts by 2
 bytes_per_boundary_per_tok = hidden_size × 1                  [int8]
 ```

serverAppConfigs-docs/LLM/Pipeline Parallelism/Expected Performance.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Expected Performance
-description: Estimated tokens per second for a 25-40B model split across two nodes over 1/2.5/10 GbE, with real benchmark anchors.
+description: "Estimated split-model throughput over ethernet, with the benchmark anchors the estimates rest on."
 tags:
   - pipeline-parallelism
   - performance
@@ -13,7 +13,7 @@ timestamp: 2026-08-14
 
 This page estimates the speed of a 25-40B model split across two machines
 over ethernet. It uses the bandwidth math in [[Ethernet Bandwidth Math]]
-and the measured numbers in [[Mixed-Vendor Experiments]].
+and the mixed-vendor measurements in [[x4-pair-experiment]].
 
 ## The Bandwidth Ceiling Is Not the Limit
 
@@ -93,5 +93,5 @@ roughly 200k-260k tokens across both nodes.
 ## See Also
 
 - [[Ethernet Bandwidth Math]]
-- [[Mixed-Vendor Experiments]]
+- [[Qwen3.8 PP Deployment]]
 - [[Sample Script Set]]

serverAppConfigs-docs/LLM/Pipeline Parallelism/Mixed-Vendor Experiments.md

@@ -1,9 +0,0 @@
----
-type: reference
-title: "Mixed-Vendor Experiments"
-description: "Real-world NVIDIA + AMD Strix Halo multi-node experiments: what works (llama.cpp RPC, Vulkan split), what breaks (mixed CUDA+ROCm vLLM), measured tok/s."
-tags:
-  - pipeline-parallelism
-  - research
-timestamp: 2026-08-14
----

serverAppConfigs-docs/LLM/Pipeline Parallelism/Qwen3.6 27B Spec Methods.md

@@ -1,9 +0,0 @@
----
-type: reference
-title: "Qwen3.6 27B Spec Methods"
-description: "Qwen3.6-27B Q8 GGUF variants and llama.cpp speculative decoding (draft-mtp, draft-dflash, ngram-mod): flags, RPC compatibility, memory/context math."
-tags:
-  - pipeline-parallelism
-  - research
-timestamp: 2026-08-14
----

serverAppConfigs-docs/LLM/Pipeline Parallelism/Qwen3.8 PP Deployment.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "Split Qwen3.8-27B across the Strix Halo iGPU (head) and the RTX"
+description: "The real split deployment: which node is head and which is worker, the flags, and the verified gotchas."
 tags:
   - llm
   - pipeline

serverAppConfigs-docs/LLM/Pipeline Parallelism/Sample Script Set.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Sample Script Set
-description: An educational two-node llama.cpp RPC split of Qwen3.6-27B-Q8_K_P over ethernet. For reading only. Do not run or deploy.
+description: "An educational two-node RPC split script set, for reading only — never run it or deploy it."
 tags:
   - pipeline-parallelism
   - sample
@@ -255,7 +255,7 @@ is 30 GiB.
 
 ## See Also
 
-- [[llama.cpp RPC]]
+- [[Qwen3.8 PP Deployment]]
 - [[Expected Performance]]
 - [[Ethernet Bandwidth Math]]
-- [[Qwen3.6 27B Spec Methods]]
+- [[DFlash DSpark Speculative Decoding]]

serverAppConfigs-docs/LLM/Pipeline Parallelism/index.md

@@ -28,28 +28,24 @@ graph LR
     end
 ```
 
-- [[llama.cpp RPC]] — the working, production-capable path for two
   heterogeneous nodes over ethernet.
-- [[vLLM Pipeline Parallelism]] — supported but heavier; needs Ray or
   multiprocessing and does not compose with speculative decoding yet.
 
 ## What the Research Found
 
-- [[Ethernet Bandwidth Math]] — a PP boundary moves only the hidden state
+- [[Ethernet Bandwidth Math]] — Bytes-per-token math for pipeline versus tensor parallelism, and the link budgets that follow from it.
   (about 10 KiB per token for a 27B model). 1 GbE supports hundreds of
   tokens per second on paper; the real limit is latency and RPC overhead.
-- [[Mixed-Vendor Experiments]] — NVIDIA + Strix Halo multi-node inference
   works today via llama.cpp RPC with separate CUDA and ROCm builds. The
   exact NVIDIA-desktop + Strix-Halo-NUC pair has not been benchmarked with
   published numbers yet.
-- [[Qwen3.6 27B Spec Methods]] — Q8 GGUF variants, and which speculative
   methods (MTP, DFlash, ngram-mod) work with RPC. DSpark is vLLM-only.
-- [[Expected Performance]] — estimated tokens per second for a 27B Q8 split
+- [[Expected Performance]] — Estimated split-model throughput over ethernet, with the benchmark anchors the estimates rest on.
   across an RTX 3090 and a Strix Halo NUC over 1/2.5/10 GbE.
 
 ## Deployment
 
-- [[Qwen3.8 PP Deployment]] — the real Qwen3.8-27B split: head on Dankclaw
+- [[Qwen3.8 PP Deployment]] — The real split deployment: which node is head and which is worker, the flags, and the verified gotchas.
   (Strix), worker on Dankserver (RTX 3090), b10433 on both sides, scripts in
   `scripts/`, morning-of test runbook. Verified gotchas: no `--device` with
   `--rpc`, default split is proportional to reported free memory (pin 1,1),
@@ -57,7 +53,7 @@ graph LR
 
 ## Sample Scripts
 
-- [[Sample Script Set]] — a two-node llama.cpp RPC split of
+- [[Sample Script Set]] — An educational two-node RPC split script set, for reading only — never run it or deploy it.
   Qwen3.6-27B-Q8_K_P with MTP, DFlash, and ngram-mod variants, sized for
   the largest context that fits. For educational reading only. Do not run
   it in production.
@@ -68,3 +64,8 @@ graph LR
 - [[frank-zealot]]
 - [[Dankserver System Specs]]
 - [[Dankclaw System Specs]]
+
+## Pages
+
+| Page | Owns |
+|---|---|

serverAppConfigs-docs/LLM/Pipeline Parallelism/llama.cpp RPC.md

@@ -1,9 +0,0 @@
----
-type: reference
-title: "llama.cpp RPC"
-description: "llama.cpp distributed inference via ggml-rpc-server and the --rpc flag: architecture, CLI, versions, limitations, and RPC-compatible speculative decoding."
-tags:
-  - pipeline-parallelism
-  - research
-timestamp: 2026-08-14
----

serverAppConfigs-docs/LLM/Pipeline Parallelism/vLLM Pipeline Parallelism.md

@@ -1,9 +0,0 @@
----
-type: reference
-title: "vLLM Pipeline Parallelism"
-description: "vLLM multi-node pipeline parallelism: flags, Ray/mp backends, interconnect requirements, PP bubble, and PP + speculative decoding support."
-tags:
-  - pipeline-parallelism
-  - research
-timestamp: 2026-08-14
----

serverAppConfigs-docs/LLM/Quantization Production.md

@@ -1,3 +1,13 @@
+---
+type: "howto"
+title: "Quantization Production"
+description: "Making a quantized payload here: the conversion recipe, the scoring gate, and the campaign ladder behind a shipped file."
+tags:
+  - llm
+  - quantization
+timestamp: 2026-10-19
+---
+
 # Quantization Production — making our own quants, per card and runtime
 
 **Research page (2026-10-08).** Question: how do WE produce quantizations
@@ -147,12 +157,14 @@ cut to GPTQ-w4 for the 3090 is a bench experiment that needs no new
 hardware; EXL3 (`convert.py` on the 3090, exllama serve) is the
 quality-per-bit extreme of the same menu.
 Caveats before any swap: the serving contract (OpenAI server,
-`reasoning_content`, vision mmproj, compaction-hub window
+`reasoning_content`, vision mmproj, and the compaction-hub window the endpoint
-200,704 ×2 slots) must be met by the challenger runtime, and the
+declares in its Current shape — [[frank-zealot]]) must be met by the challenger
-24 GB card runs ONE server — benching follows the stop-and-mask law.
+runtime, and the 24 GB card runs ONE server — benching follows the stop-and-mask
+law.
 
 #### Worked example — the frank-archon w4dn8 recipe ported to the 3090
-(audit 2026-10-08, target `Qwen3.6-35B-A3B`)
+(audit 2026-10-08, target `Qwen3.6-35B-A3B`; sized at that date's hub shape —
+the window history is [[frank-zealot]]'s Eras table)
 **The methodology ports; the encoding must be translated.** llama.cpp
 decodes no GPTQ — the recipe re-expresses on GGUF-native terms:
 imatrix on our corpora (replaces the radiance grams; runs the 65 GiB
@@ -253,8 +265,6 @@ top-8**, moe_intermediate 512, hidden 2048, MTP ×1, 262k ctx, vocab
 - Repo: `scripts/convert-swift15-w4dn8.sh`,
   `scripts/recipes/qwen4exp-swift15-w4dn8-i8-hc8m.recipe`,
   `scripts/kld-gate-swift15.sh`, `scripts/build-llama-rdna4.sh`,
-  `scripts/build-kairic-edge-gfx1151.sh`, [[frank-dragoon]],
+  `scripts/build-kairic-edge-gfx1151.sh`; endpoints [[frank-archon]],
-  [[frank-dragoon]], [[qwen3.8-strix-optimizations]],
+  [[frank-dragoon]], [[frank-zealot]]; method [[qwen3.8-strix-optimizations]]
-  [[frank-archon]],
+  and [[GGUF Compatibility]].
-  [[frank-zealot]],
-  [[frank-dragoon]], [[GGUF Compatibility]].

serverAppConfigs-docs/LLM/Quantization by Hardware Architecture.md

@@ -108,9 +108,10 @@ Use ROCmFP4 only with the ROCmFPX fork of llama.cpp. Upstream llama.cpp cannot r
 
 ## Choices for This Project
 
-### Dankserver (RTX 3090, 24 GB, Ampere)
+### The RTX 3090 (24 GB, Ampere) — frank-zealot's card
 
-The RTX 3090 has no native FP8 or FP4 tensor cores. Use:
+The 3090 has no native FP8 or FP4 tensor cores. It has sat in Dankclaw since
+2026-09-16; [[frank-zealot]]'s Eras table records the move off Dankserver. Use:
 
 | Ranking | Format | Why |
 |---------|--------|-----|
@@ -121,13 +122,17 @@ The RTX 3090 has no native FP8 or FP4 tensor cores. Use:
 
 ### Dankclaw (Strix Halo gfx1151, RDNA 3.5)
 
-RDNA 3.5 has no native FP8 tensor cores. The APU shares memory. The active Ling-3.0-flash service runs vLLM-ROCm with the AMD Quark INT4 (W4A16) format (the jcbtc CIRU Strix-native bundle). INT4 weights keep the 124B model inside the 96 GiB frame buffer with a full-precision KV cache.
+RDNA 3.5 has no native FP8 tensor cores and the APU shares its memory, so the
+GPU budget is the GTT aperture and every live figure on the box is
+[[Dankclaw System Specs]]. What serves here today is [[frank-dragoon]]: a
+vendor `.hgn` checkpoint, a format this page cannot rank because no public
+quantizer exists for it ([[Quantization Production]]).
 
 | Ranking | Format | Why |
 |---------|--------|-----|
-| 1 | INT4 W4A16 (Quark/vLLM) | active; fits 96 GiB; native ROCm kernels; concurrency |
+| 1 | `.hgn` (deployed) | the halogen engine's own format; production door is closed |
-| 2 | MXFP4 (Quark) | same-bit, higher accuracy; beta on gfx1151 (A/B experiment) |
+| 2 | GGUF K/I quants, K_P blends | the only self-produced option on this card ([[Quantization Production]]) |
-| 3 | GGUF Q4_K_M / Q8_0 | works with upstream llama.cpp only |
+| 3 | INT4 W4A16 (Quark) / MXFP4 (Quark) | the retired Ling-3.0-flash vLLM era, measured under the firmware-VGM frame buffer: [[ling-3.0-flash-trial]] |
 | 4 | FP8 (vLLM) | software emulation; memory savings only; no compute win |
 
 ## See Also

serverAppConfigs-docs/LLM/RAM CPU Offloading in VLLM.md

@@ -11,9 +11,19 @@ timestamp: 2026-08-28
 
 ## Overview
 
-vLLM uses CPU RAM and swap space to extend GPU memory capacity. This allows larger models to run on GPUs with limited VRAM. vLLM does not offload model weights to CPU. Instead, vLLM moves KV cache data between GPU and CPU.
+Stock vLLM offloads **KV pages**, not weights: the scheduler moves KV cache between GPU
+and CPU. That is the upstream behaviour and it is NOT the whole story on our hosts — the
+tcclaviger/R4D fork ran a real **weight** offload (`--enable-expert-offload`, tiered
+expert placement, a pinned host pool per rank), which is how a 147 GiB MoE served from a
+246 GiB box: [[RDNA4 MoE Expert Offload VRAM Budget]] and the tcclaviger era row of
+[[frank-archon]]. First-hand in-repo evidence outranks a generic upstream claim about our
+own hosts ([[Model Swap and Rollback]] §10).
 
-> **Current vLLM note:** Recent vLLM releases removed the `--swap-space` engine argument. CPU KV-cache offloading now uses `--kv-offloading-size`. See the parameters below for details.
+> **Verified 2026-10-19 against `vllm/config/cache.py` on `main`:** there is no
+> `swap_space` field — `--swap-space` is gone from current engine args. CPU KV offload is
+> `--kv-offloading-size`, and it activates **only** together with `--kv-offloading-backend`
+> (default `native`); both fields live in that one file. This page is the fleet's owner of
+> that knob contract — other pages link here instead of restating it.
 
 ## How CPU Offloading Works
 
@@ -42,9 +52,12 @@ This parameter controls the fraction of GPU memory used for KV cache.
 
 Lower values leave more GPU memory for model weights. Higher values allow more concurrent requests but increase swap frequency.
 
-### swap_space (removed) / kv-offloading-size (current)
+### swap_space (removed) / kv-offloading-size + kv-offloading-backend (current)
 
-The `--swap-space` argument was removed from current vLLM engine args. Use `--kv-offloading-size` instead. The table below describes the historical `--swap-space` values for reference.
+`--swap-space` no longer exists in current engine args (verified above); the live pair is
+`--kv-offloading-size` with `--kv-offloading-backend`, and offload stays off until the size
+is set. The table below is the historical `--swap-space` sizing guidance, kept as a sizing
+reference only.
 
 | Value | Description |
 |-------|-------------|
@@ -103,6 +116,9 @@ This parameter sets the KV cache data type.
 
 ## Memory Configuration Examples
 
+All three examples carry the retired `--swap-space` syntax and are kept as sizing
+references; the live knob pair is named above.
+
 ### Small Model on Single GPU
 
 ```
@@ -157,7 +173,7 @@ WARNING scheduler.py: Sequence group 0 is preempted by PreemptionMode.RECOMPUTE
 If you see frequent preemptions:
 
 1. Increase `gpu_memory_utilization`
-2. Increase `swap_space`
+2. Raise the KV offload budget (`--kv-offloading-size`, with `--kv-offloading-backend`)
 3. Decrease `max_num_seqs`
 4. Increase `tensor_parallel_size`
 5. Increase `max_model_len` to match actual usage
@@ -169,7 +185,8 @@ If you see frequent preemptions:
 - Reduce `max_num_seqs` to limit concurrent requests
 - Disable CUDA graphs with `--enforce-eager` to save memory
 - Set `compilation_config.cudagraph_capture_sizes` to smaller values
-- Use `--kv-cache-memory` to skip memory profiling
+- Set `--kv-cache-memory-bytes` to pin the KV budget instead of letting the profiler guess
+  (the flag our own `scripts/patches/gpu_worker-kv-cap.patch` reads)
 - Limit multi-modal inputs with `limit_mm_per_prompt`
 
 ## Environment Variables

serverAppConfigs-docs/LLM/RDNA4 Container Serving.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: RDNA4 Container Serving
-description: Bringing a model larger than VRAM onto Dankserver's 2x R9700 (gfx1201) with the tcclaviger vLLM stack — quant-class gating, fetch verification, container GPU-init triage, memory budgeting and the expert-offload plan.
+description: "Bringing a model larger than VRAM onto the two-card box: quant gating, fetch verification, container GPU-init triage."
 tags: [rdna4, gfx1201, r9700, vllm, expert-offload, podman, rocm]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/LLM/RDNA4 MoE Expert Offload VRAM Budget.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: RDNA4 MoE Expert Offload VRAM Budget
-description: The expert-offload plan arithmetic on the tcclaviger fork — which terms a deploy can move, the util law, the CUDA-graph charge, what free VRAM really is, knife-edge survivability, parallelism ceilings and the context ladder.
+description: "Expert-offload arithmetic on the RDNA4 fork: movable terms, the utilisation law, graph charge, ceilings, context ladder."
 tags: [vllm, expert-offload, vram, arena, kv-cache, ladder, tcclaviger]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/LLM/Running Qwen3.6 27B FP8 on Dankclaw.md

@@ -1,12 +1,18 @@
 ---
 type: reference
-description: "Qwen3.6-27B is a dense vision-language model from the Qwen3.6 series."
+description: "Serving a dense FP8 vision-language checkpoint on the Strix Halo iGPU: the load path, the flags, the format gate."
 tags:
   - llm
 timestamp: 2026-09-03
 ---
 
 # Running Qwen3.6 27B FP8 on Dankclaw
+> **RETIRED - vLLM era (before the 2026-08-17 redo).** Nothing on this page serves
+> today: no vLLM or ROCm process runs on Dankclaw, and the iGPU endpoint at
+> `192.168.0.143:7770` is [[frank-dragoon]] (halogen flash-server). The page stays as
+> the era record of the Qwen3.6-27B-FP8 vLLM bring-up and the Strix Halo ROCm
+> recipes ([[frank-redo-2026-08-17]]). The hardware table below carries the era's
+> host figures; live ones are [[Dankclaw System Specs]].
 
 ## Model Information
 
@@ -29,6 +35,7 @@ Qwen3.6-27B is a dense vision-language model from the Qwen3.6 series. It uses 27
 | Vision Encoder | Yes (image-text-to-text) |
 
 ## Hardware: Dankclaw
+*Era figures (2026-08). The host has changed since - [[Dankclaw System Specs]].*
 
 | Property | Value |
 |----------|-------|
@@ -55,7 +62,11 @@ The FP8 variant requires approximately 16-17 GB. ThinkingCap-FP8 requires ~29 GB
 
 ## Prerequisites
 
-> **Production note:** Dankclaw's primary service now runs vLLM-ROCm with the Ling-3.0-flash CIRU INT4 model (see `scripts/frank-dragoon.service`). This page documents the alternative vLLM FP8 deployment of Qwen3.6-27B.
+> **Era note (2026-08, superseded twice):** at writing time Dankclaw's primary
+> service was the vLLM-ROCm Ling-3.0-flash CIRU INT4 trial ([[ling-3.0-flash-trial]],
+> retired 2026-08-17), and this page documented the alternative vLLM FP8 deployment
+> of Qwen3.6-27B. Both paths are dead; `scripts/frank-dragoon.service` today is the
+> halogen flash-server unit ([[frank-dragoon]]).
 
 Install vLLM for ROCm. Version 0.24.0+ is required for Qwen3.6 with speculative decoding:
 

serverAppConfigs-docs/LLM/Running Qwen3.6 35B A3B FP8 on Dankserver.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "Qwen3.6-35B-A3B is a Mixture-of-Experts vision-language model from the Qwen3.6 series."
+description: "Serving a mixture-of-experts FP8 checkpoint on the R9700 host: the load path, the format gate, the offload shape."
 tags:
   - llm
 timestamp: 2026-09-03

serverAppConfigs-docs/LLM/Shared Memory Architecture Dankclaw.md

@@ -103,7 +103,7 @@ vllm serve model \
 
 - `gpu_memory_utilization`: Set lower (0.8-0.85) to leave room for CPU operations
 - `max_model_len`: Match actual context needs
-- The old `--swap-space` argument was removed from current vLLM — `CacheConfig` on `main` carries no `swap_space` field ([source](https://raw.githubusercontent.com/vllm-project/vllm/main/vllm/config/cache.py), read 2026-10-18). Use `--kv-offloading-size` (`kv_offloading_size`, same file) for CPU KV offload
+- `--swap-space` is retired from current vLLM; the CPU KV-offload knob pair, with the upstream `CacheConfig` verification, is owned by [[RAM CPU Offloading in VLLM]]
 
 ### NUMA Binding
 

serverAppConfigs-docs/LLM/Tcclaviger Fork Ops.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: Tcclaviger Fork Ops
-description: Operating the tcclaviger RDNA4 vLLM fork on dankserver (shape G era, rollback target since the 2026-10-05 FreeToken cutover) — the ad-hoc sweep harness, measured knob verdicts, sweep hygiene, the large-MoE serving recipe, and compile-cache persistence.
+description: "Operating the RDNA4 vLLM fork: the sweep harness, measured knob verdicts, sweep hygiene, compile-cache persistence."
 tags: [tcclaviger, vllm, dankserver, expert-offload, sweeps, cache]
 timestamp: 2026-10-05T00:00:00-07:00
 ---

serverAppConfigs-docs/LLM/VLLM Index.md

@@ -1,6 +1,6 @@
 ---
 type: reference
-description: "This index contains all documentation for vLLM deployment on Dankserver and Dankclaw."
+description: "Locator for every vLLM page in this vault."
 tags:
   - llm
   - vllm
@@ -60,7 +60,7 @@ vllm serve meta-llama/Llama-3.1-70B-Instruct --tensor-parallel-size 4
 vllm serve Qwen/Qwen2.5-1.5B-Instruct --quantization fp8
 
 # With GPU memory control
-vllm serve Qwen/Qwen2.5-1.5B-Instruct --gpu-memory-utilization 0.8 --swap-space 8
+vllm serve Qwen/Qwen2.5-1.5B-Instruct --gpu-memory-utilization 0.8 --kv-offloading-size 8 --kv-offloading-backend native
 ```
 
 ### Common API Endpoints
@@ -79,7 +79,7 @@ vllm serve Qwen/Qwen2.5-1.5B-Instruct --gpu-memory-utilization 0.8 --swap-space
 |-----------|-------------|---------------|
 | tensor_parallel_size | Number of GPUs for model sharding | 1-8 |
 | gpu_memory_utilization | Fraction of GPU memory for KV cache (default 0.92) | 0.7-0.95 |
-| swap_space | Removed in current vLLM; use `--kv-offloading-size` | n/a |
+| swap_space | Retired; live knob pair in [[RAM CPU Offloading in VLLM]] | n/a |
 | max_model_len | Maximum context length | auto |
 | max_num_batched_tokens | Max tokens per batch | 2048-8192 |
 | max_num_seqs | Max sequences per batch | 128-512 |

serverAppConfigs-docs/LLM/VLLM Overview.md

@@ -140,7 +140,7 @@ curl http://localhost:8000/v1/chat/completions \
 | `tensor_parallel_size` | 1 | Number of GPUs for tensor parallelism |
 | `pipeline_parallel_size` | 1 | Number of GPUs for pipeline parallelism |
 | `gpu_memory_utilization` | 0.92 | Fraction of GPU memory for KV cache |
-| `swap_space` | removed | Removed in current vLLM; use `--kv-offloading-size` |
+| `swap_space` | — | retired; the live CPU-KV-offload knob pair is in [[RAM CPU Offloading in VLLM]] |
 | `enforce_eager` | false | Use eager mode (no CUDA graphs) |
 | `max_num_batched_tokens` | 2048 | Max tokens per batch |
 | `max_num_seqs` | 128 | Max sequences per batch |
@@ -167,7 +167,7 @@ curl http://localhost:8000/v1/chat/completions \
 | Argument | Default | Description |
 |----------|---------|-------------|
 | `gpu_memory_utilization` | 0.92 | Fraction of GPU memory for KV cache |
-| `swap_space` | removed | Removed in current vLLM; use `--kv-offloading-size` |
+| `swap_space` | — | retired; the live CPU-KV-offload knob pair is in [[RAM CPU Offloading in VLLM]] |
 | `kv_cache_dtype` | auto | KV cache data type (auto, fp8, fp8_e5m2) |
 | `max_model_len` | auto | Maximum context length |
 | `num_gpu_blocks` | auto | Number of GPU blocks |

serverAppConfigs-docs/LLM/dankclaw-iommu-translation-off.md

@@ -1,7 +1,7 @@
 ---
-type: research
+type: reference
 title: Dankclaw IOMMU boot line — decision record (amd_iommu=off 2026-09-11 → iommu=pt 2026-10-18)
-description: Dankclaw boots iommu=pt since 2026-10-18 — identity DMA with the IOMMU armed, which restored the XDNA2 NPU at a measured prefill cost of nothing (+2.0% on byte-identical traffic). Records the 2026-09-11 amd_iommu=off era that bought a vendor-claimed 13-16% figure never measured here, what that cost, the AMD PerfOpt research (Linux 7.4), the tooling that owns the boot line, and the revert path.
+description: "Why Dankclaw boots with identity DMA, what the earlier off-era bought and cost, and which tooling owns the boot line."
 tags:
   - dankclaw
   - iommu

serverAppConfigs-docs/LLM/dankserver-frontier-moe-feasibility.md

@@ -1,7 +1,7 @@
 ---
-type: research
+type: reference
 title: Frontier MoE on Dankserver — what fits, on which runtime
-description: VERIFIED 2026-09-28 by measurement and source reading. Compares DeepSeek-V4.1-Flash, MiMo-V2.6-Flash-MOPD and GLM-5.3-Flash against the 2x R9700 (gfx1201) / 246 GiB box, and assesses the Affinity runtime's portability off DeepSeek-V4-Flash. Records the capacity arithmetic that decides the answer before any model is loaded.
+description: "The capacity arithmetic that decides whether a frontier mixture-of-experts fits this box before any model is loaded."
 tags:
   - dankserver
   - r9700

serverAppConfigs-docs/LLM/dankserver-vram-growth.md

@@ -14,6 +14,10 @@ timestamp: 2026-09-03
 
 > **SUPERSEDED 2026-08-17.** The Frank redo retired this topology.
 > See [[frank-redo-2026-08-17]] and [[deployment]] for the active configuration.
+> The `frank-zealot` below is the 2026-08 service: llama.cpp on the RTX 3090
+> **while that card sat in Dankserver**. Today's [[frank-zealot]] is a different host
+> (Dankclaw), payload and runtime build, though the same card class - this crash
+> signature is not a live fault.
 
 # Dankserver VRAM and RAM Growth Under Load
 

serverAppConfigs-docs/LLM/dealign-ornith-crack.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: dealign Ornith-1.5-35B-A3B CRACK on Dankserver
-description: dealignai/Ornith-1.5-35B-A3B-UNCENSORED (CRACK Q6_K) served by upstream llama.cpp on the RTX 3090. MoE model with ngram-mod speculative decoding; selected expert weights offloaded to CPU with an explicit --override-tensor. frank-zealot.
+description: "Retired era: a mixture-of-experts checkpoint served with CPU expert offload and n-gram drafting on a single card."
 tags:
   - llamacpp
   - cuda
@@ -9,6 +9,7 @@ tags:
   - moe
   - ornith
   - mtp
+  - retired-endpoint
 timestamp: 2026-08-24
 ---
 
@@ -123,4 +124,4 @@ llama-server \
 
 - [[deployment]] — deploy and update process
 - [[Dankserver System Specs]] — the box
-- [[frank-redo-2026-08-17]] — fleet topology history
+- [[frank-redo-2026-08-17]] — fleet topology histor

serverAppConfigs-docs/LLM/deployment.md

@@ -1,5 +1,5 @@
 ---
-type: guide
+type: howto
 title: LLM Deployment
 description: Scoped deployment and update process for the three inference services (frank-archon, frank-dragoon, frank-zealot).
 tags:

serverAppConfigs-docs/LLM/frank-archon.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: "frank-archon on Dankserver — radiance (StillDeadcode) 1.0.13, publisher Qwen3.8-Flash-Next iq4r .rad, 2× R9700 TP=2 (ACTIVE)"
-description: "The one frank-archon page: the live radiance shape and harness contract (read off scripts/frank-archon.env), the Eras table carrying every rollback path including the re-download doors for the purged payloads, the laws this endpoint taught (pinned-RAM/TTM preflight, the KV dtype law, the one per-card VRAM budget, descriptor selection), the wire contract, and the files that own it. It replaces the nine per-era runbooks."
+description: "The radiance endpoint: live shape and harness contract, every era with its rollback path, and the laws it taught."
 tags:
   - llm
   - frank-archon
@@ -11,6 +11,7 @@ tags:
   - r9700
   - tp2
   - expert-offload
+  - endpoint
 timestamp: 2026-10-18
 ---
 
@@ -139,15 +140,21 @@ marked "re-fetch" is gone from `/home/dank/models/`, which today holds only `Sti
 | 2026-09-26 → 09-27 | unsloth Q8_0, 175.30 GiB / 6 parts + shared-Q8_0 MTP 2,786,568,256 B + `mmproj-BF16.gguf` 907,542,944 B | unsloth llama.cpp b11030-mix prebuilt (commit `6ba30d05b`), ROCm gfx120X | `-ts 1,1` layer split, routed experts **and** the PLE table computed in host RAM (`-ot exps=CPU,per_layer_token_embd.weight=CPU`), 262,144 × 1 slot, then the same-day reshape to 4 × 262,144 with V `q8_0` and hot expert blocks 5/3 | the R9V radiance-vLLM fork took the port at Frank's direction (true TP=2 plus MTP4) | trio at commit `4992e5a`+; the GGUF/MTP/mmproj set is no longer on disk → re-fetch, then redeploy |
 | 2026-09-26 (same day) | `Lucebox/DeepSeek-V4.1-Flash-ROCMFP23-GGUF`, 377.2 GiB, sha256 `2daea6ca…` | `localhost/lucebox-rocm:gfx1201`, built from `Dockerfile.rocm` + 3 local patches | ONE R9700, `--max-ctx 131072`, `--chunk 8192`, q4_0 K+V, `--ds4-prefill sparse`, routed experts on CPU from the page cache | 377 GiB fits neither 63.7 GiB of VRAM nor 246 GiB of RAM → NVMe page-cache thrash; Qwen Flash-Next Q8 gave better quality, vision and 262k at comparable speed | image still in dank's rootless storage; payload gone; the quadlet and its entrypoint were deleted by `8500600` — `git show 8500600^:dankserver/frank-primary/quadlet/frank-primary.container` (and `…:dankserver/frank-primary/frank-primary-entrypoint.sh`), stop the root unit, start the user quadlet |
 
-Before 2026-09-26 the port belonged to the **`frank-medium`** service: [[frank-medium-radiance-mxfp4]]
+Before 2026-09-26 the port belonged to the **`frank-medium`** service, and its era
-(vllm-radiance TP=2 MXFP4, 2026-09-20 → 09-26) is that era's page and is **not** superseded here.
+pages are **not** superseded here: [[frank-medium]] is the locator for that
+endpoint's whole shape history, including the unresolved end date of the
+vllm-radiance era (this table opens on 09-26; the era page claims 10-10).
 
 ## Laws learned here
 
 ### The radiance engine
 
 - **KV dtype law.** `--kv-cache-dtype` takes only `bf16|fp8` — ONE dtype for the whole cache,
-  so llama.cpp's exact-K / quantized-V pair (what [[frank-zealot]] runs as `--cache-type-k`/
+  a **radiance** restriction, not stock vLLM's: upstream advertises `auto|fp8|fp8_e5m2|fp8_e4m3`
+  (`docs.vllm.ai` engine-args) and even there the advertised set is not the usable set — several
+  accepted values crash engine init at the attention layer's own dtype check
+  ([vllm-project/vllm#42587](https://github.com/vllm-project/vllm/issues/42587)).
+  So llama.cpp's exact-K / quantized-V pair (what [[frank-zealot]] runs as `--cache-type-k`/
   `--cache-type-v`) is unservable here: the rung below bf16 is fp8 on both halves. Measured
   per-rank cost out of the boot ledger's group table (fp8 boot 2026-10-08, bf16 boot
   2026-10-11): `kv_attn` 13 layers / 4-token blocks pages **26.00 → 52.00 KiB**, while
@@ -438,3 +445,4 @@ Related: [[frank-dragoon]] (the abliterated family), [[frank-zealot]],
 [[Dual-R9700-Cooperation]], [[deployment]], [[swift15-campaign-worklog]],
 [[dankserver-frontier-moe-feasibility]], [[x4-pair-experiment]], [[RDNA4 Container Serving]],
 [[frank-medium-radiance-mxfp4]], [[LLM/index]].
+---

serverAppConfigs-docs/LLM/frank-dragoon.md

@@ -1,7 +1,7 @@
 ---
 type: reference
 title: "frank-dragoon on Dankclaw — halogen-flash-server 0.16.2, native v2 abliterated Qwen3.8-Flash-Next (canonical)"
-description: "The one runbook for frank-dragoon, the Strix Halo iGPU endpoint (192.168.0.143:7770): current shape from the env, every retired era with its rollback path, the durable laws this endpoint paid for, the wire contract, and the files that own it."
+description: "The iGPU endpoint: live shape, every era with its rollback path, the laws it paid for, and the files that own it."
 tags:
   - llm
   - frank-dragoon
@@ -9,6 +9,7 @@ tags:
   - strix-halo
   - gfx1151
   - halogen
+  - endpoint
 timestamp: 2026-10-18
 ---
 
@@ -234,3 +235,4 @@ created it — earlier topologies in [[frank-redo-2026-08-17]].
 - Related: [[deployment]] · [[Model Swap and Rollback]] · [[frank-zealot]] · [[frank-archon]] ·
   [[dankclaw-iommu-translation-off]] · [[frank-redo-2026-08-17]] · [[Dankclaw System Specs]] ·
   [[DFlash DSpark Speculative Decoding]] · [[qwen3.8-spec-matrix]] · [[qwen3.8-strix-optimizations]].
+---

serverAppConfigs-docs/LLM/frank-medium-batch-ubatch.md

@@ -2,7 +2,7 @@
 timestamp: 2026-09-17
 type: reference
 title: frank-medium — Batch and Ubatch Sweep
-description: llama-bench sweep of --batch-size against --ubatch-size on frank-medium (2x Radeon AI PRO R9700, layer split) at the deployed context shape, and the rebalance it forced. Prefill peaks at ubatch 512 and falls on BOTH sides.
+description: "The batch-versus-ubatch sweep on the layer-split pair at its deployed shape, and the rebalance the sweep forced."
 tags:
   - benchmark
   - llamacpp
@@ -11,6 +11,7 @@ tags:
   - dankserver
   - layer-split
 ---
+  - retired-endpoint
 
 # frank-medium — Batch and Ubatch Sweep
 
@@ -222,4 +223,5 @@ re-checking that 35:30 and 37:28 still fail so the gate keeps discriminating.
   difference: with no KV to attend over, per-pass overhead dominates and a
   bigger micro-batch wins; at 64k of resident KV it does not.
 - [[Dual-R9700-Cooperation]] — why the cards are layer-split at all
-- [[Dankserver System Specs]] — hardware inventory
+- [[Dankserver System Specs]] — hardware inventory---
+timestamp: 2026-09-17

serverAppConfigs-docs/LLM/frank-medium-llamacpp-dflash2.md

@@ -1,7 +1,7 @@
 ---
-type: configuration
+type: reference
 title: frank-medium llama.cpp Runbook (DFlash2 drafter)
-description: The former ACTIVE frank-medium deployment since 2026-09-16 (model swapped 2026-09-19) — mainline llama.cpp on Dankserver serving orcarouter/Qwen3.8-27B-Uncensored-GGUF at Q8_0 with the z-lab DFlash2 Q4_K_M drafter (the model's own MTP head stays in the file, one SPEC_TYPE change away), as ONE layer-split process across both Radeon AI PRO R9700 cards at a balanced 32:33 split, a 327680-position KV pool (163840 per conversation over two slots), f16 KV plus a 16 GiB host-RAM prompt cache, vision via the BF16 mmproj.
+description: "Retired era: the layer-split llama.cpp shape with a drafter, its ladder measurements, and the balance it settled on."
 tags:
   - frank-medium
   - dankserver
@@ -12,6 +12,7 @@ tags:
   - gfx1201
   - r9700
   - layer-split
+  - retired-endpoint
 timestamp: 2026-09-20
 ---
 
@@ -730,3 +731,4 @@ fleet.
 - [[frank-medium-batch-ubatch]] — the batch/ubatch sweep that set the deployed
   geometry and moved this split from 36:29 to 35:30: the ubatch optimum at 512,
   why the logical batch is free, and the harness traps
+---

serverAppConfigs-docs/LLM/frank-medium-model-swap.md

@@ -1,7 +1,7 @@
 ---
-type: runbook
+type: howto
 title: frank-medium Model Swap
-description: How to swap the checkpoint behind the frank-medium endpoint (Dankserver :7770, vllm-radiance TP=2) — the streamlining toolchain (hf-manifest.py, hf-fetch.sh, swap-frank-medium.sh), the quantization-aware entrypoint contract, the quadlet edit, the deploy, the capability battery, and the rollback path.
+description: "Retired-era swap procedure: the fetch toolchain, the entrypoint contract, the capability battery, the rollback path."
 tags:
   - frank-medium
   - dankserver
@@ -9,17 +9,19 @@ tags:
   - vllm-radiance
   - huggingface
   - runbook
+  - retired-endpoint
 timestamp: 2026-09-20
 ---
 
 # frank-medium Model Swap
 
-Swapping the checkpoint behind **frank-medium** (Dankserver `:7770`,
+**Historical.** frank-medium is a retired endpoint — `:7770` on Dankserver is
-vllm-radiance TP=2) is a four-step process, and the toolchain below drives all
+[[frank-archon]] today, and the live procedure is [[Model Swap and Rollback]].
-of it. The design goal (2026-09-20, after the MXFP4 → FP8 swap) is that a swap
+This page records how a swap worked in that era: a four-step process whose design
-is **one command**: generate a manifest, download it verified, point the
+goal (2026-09-20, after the MXFP4 → FP8 swap) was that a swap be **one command** —
-quadlet at it, deploy. The entrypoint is quantization-aware, so the only repo
+generate a manifest, download it verified, point the quadlet at it, deploy. The
-change a swap makes is the quadlet's four env vars.
+entrypoint was quantization-aware, so the only repo change a swap made was the
+quadlet's four env vars.
 
 ## Why this exists
 
@@ -154,9 +156,10 @@ back:
 2. `deploy.sh dankserver --service frank-medium --skip-e2e`.
 3. Re-run the capability battery.
 
-The 2026-09-20 rollback target is the MXFP4 checkpoint at
+The 2026-09-20 rollback target is the MXFP4 checkpoint with
-`/home/dank/models/Qwen3.8-27B-Uncensored-MXFP4-awq` (19.37 GiB single
+`SPEC_METHOD=dflash`, `SPEC=7`; [[frank-medium-radiance-mxfp4]] owns that
-safetensors) with `SPEC_METHOD=dflash`, `SPEC=7`.
+payload's identity, and as of the 2026-10-19 host census it is a re-fetch, not a
+local file.
 
 ## 2026-09-20 swap record (MXFP4 → FP8)
 
@@ -183,3 +186,4 @@ safetensors) with `SPEC_METHOD=dflash`, `SPEC=7`.
   DFlash2 drafter's 2.1 GiB costs the pool vs MTP's 461,540 (1.76×); both
   smaller than MXFP4's 943,581 (3.59×) because FP8 weights are bigger (30.9
   vs 19.4 GiB).
+---

serverAppConfigs-docs/LLM/frank-medium-radiance-mxfp4.md

@@ -1,7 +1,7 @@
 ---
-type: configuration
+type: reference
 title: frank-medium vllm-radiance MXFP6 Runbook
-description: ACTIVE frank-medium runbook — vllm-radiance serving hugypufy/Swift-Qwen3.8-27B-PARO-MXFP6 (ParoQuant MXFP6 W4A8, DFlash2 drafter, unquantized bf16 KV) as ONE tensor-parallel process (TP=2) on Dankserver's two AMD Radeon AI PRO R9700 (gfx1201). Cut to MXFP6 on 2026-09-21 (PR #51's launch6_p kernel, image 0.13.0-e060895); the MXFP4 checkpoint (just1moremodel/Qwen3.8-27B-Uncensored-MXFP4-awq, the 2026-09-21 shape) is the on-disk rollback. Model-swap process: [[frank-medium-model-swap]]. The sections below describe the 2026-09-16 two-replica era.
+description: "Retired era: the tensor-parallel radiance shape on two cards, its quant-class swap, and the on-disk rollback payload."
 tags:
   - frank-medium
   - dankserver
@@ -14,12 +14,14 @@ tags:
   - rccl
   - pcie-atomics
   - quadlet
+  - retired-endpoint
 timestamp: 2026-09-21
 ---
 
 # frank-medium vllm-radiance MXFP6 Runbook
 
-The ACTIVE frank-medium deployment: the `ggz14/vllm-radiance-mxfp4:0.13.0-e060895`
+**RETIRED era (2026-09-21 → 10-10; the endpoint is [[frank-archon]] today and this
+shape is one row in its Eras table.)** The deployment was the `ggz14/vllm-radiance-mxfp4:0.13.0-e060895`
 image (built from PR #51's head, tagged locally as
 `localhost/radiance-vllm:0.13.0-e060895`) plus the `radiance-vllm-mxfp4`
 patches at e060895, serving `hugypufy/Swift-Qwen3.8-27B-PARO-MXFP6`
@@ -36,11 +38,14 @@ e4m3fn scale) with `--kv-cache-dtype auto` (unquantized bf16 KV) and
 `--gpu-memory-utilization 0.98`. The Swift variant is a finetune of
 `ukisai/Swift-Qwen3.8-27b` (a different base from `Qwen/Qwen3.8-27B`), so the
 DFlash2-FP8 drafter's hidden-state distribution is a mismatch — acceptance may
-drop from the MXFP4 era's 4.24/7, but it is still a net win over no spec
+drop from the 4.24/7 that the DFlash2 arm measured on the FP8 target (the A/B
-decode. **The MXFP4 checkpoint is the on-disk rollback**: flip `SNAP` back to
+below ran both arms on FP8, not on MXFP4). **The MXFP4 checkpoint is the
-`/models/Qwen3.8-27B-Uncensored-MXFP4-awq`, and the image
+rollback**, and as of the 2026-10-19 host census it is **no longer on disk**:
-back to `localhost/radiance-vllm:0.9.3` (re-pull `docker.io/stilldeadcode/
+`/home/dank/models/` holds `StillDeadcode`, `rad` and `tpl.jinja` only, so a
-vllm-radiance:0.9.3` if it is no longer on disk; the MXFP4 shape auto-sized to
+rollback re-fetches `/models/Qwen3.8-27B-Uncensored-MXFP4-awq` (Hub
+`just1moremodel/Qwen3.8-27B-Uncensored-MXFP4-awq`) and flips `SNAP` and the
+image back to `localhost/radiance-vllm:0.9.3` (re-pull
+`docker.io/stilldeadcode/vllm-radiance:0.9.3` if the local tag is gone; the MXFP4 shape auto-sized to
 486,464 tokens with bf16 KV and held the full 262,144 window).
 
 **Deployed shape since 2026-09-20: one rootless Quadlet, `--tensor-parallel-size 2`.**
@@ -527,9 +532,8 @@ soak (three concurrent loops, each re-sending a ~30k-token document every turn
 with growing history) shows what happens at that limit: turns alternate between
 **~1.1 s** when the prefix is resident and **12-22 s** when it has been evicted
 and must be prefilled again, because two families per card plus their cached
-prefixes exceed the pool. Nothing failed — ~120 requests, no errors, no failover,
+prefixes exceed the pool. Nothing failed, and per-family pinning kept the fast
-both replicas steady — and per-family pinning kept the fast turns on the replica
+turns on the replica that holds the prefix.
-that holds the prefix.
 
 Read that as a capacity budget, not a defect: two concurrent large-context
 sessions per card are comfortable, three or more of that size trade turns
@@ -631,3 +635,4 @@ if that person is looking. That is the honest state of "alerting" here.
   the same image and kernel 7.0.0-30 failing identically.
 - `ggz14/radiance-vllm-mxfp4` — the patch set and the reference benchmark table
   this page compares against.
+---

serverAppConfigs-docs/LLM/frank-medium-rocmfpx.md

@@ -1,7 +1,7 @@
 ---
-type: configuration
+type: reference
 title: frank-medium ROCmFPX Runbook
-description: charlie12345/ROCmFPX llama.cpp serving kingjones777/Qwen3.8-27B-ROCmFPX-Q8_0-AGENT-GGUF as frank-medium on Dankserver (2x AMD Radeon AI PRO R9700, gfx1201).
+description: "Retired era: the ROCmFPX fork serving an agent-tuned checkpoint on the two-card box, and the loader pin it required."
 tags:
   - frank-medium
   - dankserver
@@ -10,6 +10,7 @@ tags:
   - mtp
   - gfx1201
   - r9700
+  - retired-endpoint
 timestamp: 2026-09-15
 ---
 

serverAppConfigs-docs/LLM/frank-medium.md

@@ -0,0 +1,65 @@
+---
+type: reference
+title: frank-medium (retired) — the Dankserver endpoint before frank-archon
+description: "Locator for the retired Dankserver LLM endpoint: which era page owns which payload, and where the dates disagree."
+timestamp: 2026-10-19
+tags:
+  - llm
+  - dankserver
+  - frank-medium
+  - retired
+  - retired-endpoint
+---
+
+# frank-medium (retired) — the Dankserver endpoint before frank-archon
+
+`frank-medium` was the LLM service on Dankserver port 7770. It is **not** a live
+endpoint: the same port is [[frank-archon]] today, and [[frank-archon]] owns every
+shape served from 2026-09-26 onward, including the `frank-medium` → `frank-archon`
+name cutover dated 2026-10-10 in `AGENTS.md`. This page owns only the **locator** —
+which era page holds which payload's evidence — and carries no measurements: every
+number stays in the era page that measured it.
+
+## Eras
+
+Windows are quoted from each era page's own banner; no date here is derived.
+
+| Window | Runtime | Payload | Shape | Page | Rollback |
+|---|---|---|---|---|---|
+| 2026-09-15 → 2026-09-16 | `charlie12345/ROCmFPX` llama.cpp `main` at `c49ebdb`, self-contained ROCm 7.14 | `Qwen3.8-27B-Q8_0_ROCMFPX_AGENT.gguf` (custom tensor type 103) + an MTP Q4_0 draft | 2× R9700 `-sm layer` over `ROCm0,ROCm1`, 131,072 × 1 slot, f16 KV + flash attention, draft-MTP pinned to `ROCm1`; the fork is the only loader for that tensor type | [[frank-medium-rocmfpx]] | re-fetch the GGUF, rebuild the fork |
+| 2026-09-16 → 2026-09-19 | vllm-radiance on the old TUF GAMING B650-E board | ParoQuant MXFP4 | two single-GPU replicas behind an adaptive-routing proxy | [[frank-medium-radiance-mxfp4]] (sections below its deployed-shape header) | the replica pair is reconstructable from that page's flags |
+| 2026-09-16 → 2026-09-20 | llama.cpp `fb27a525`, ROCm `7.14.0a` | its own GGUF build, DFlash drafter | `-sm layer` split across the two cards, drafter pinned to one device | [[frank-medium-llamacpp-dflash2]] | the page is the named rollback target for the llama shape |
+| 2026-09-20 → disputed, see Open questions | vllm-radiance on the replacement ProArt board | ParoQuant MXFP4 → FP8 E4M3 128×128 (`orcarouter/…-FP8`, same day, [[frank-medium-model-swap]]) → ParoQuant MXFP6 (`paroquant_mxfp6`) from 09-21 | `--tensor-parallel-size 2` over x8/x8 Gen5 root ports | [[frank-medium-radiance-mxfp4]] (deployed-shape header) | re-fetch the MXFP4 checkpoint (host census 2026-10-19: not local); image `localhost/radiance-vllm:0.9.3` |
+
+`[[frank-medium-batch-ubatch]]` is not an era: it is the batch-versus-ubatch sweep run
+on the layer-split pair at its deployed shape, and its numbers belong to that
+campaign. `[[frank-medium-model-swap]]` is likewise a campaign ledger — the record of
+the 2026-09-20 swap procedure — while the procedure itself is owned by
+[[Model Swap and Rollback]].
+
+## Laws
+
+None restated. Each era page carries its own laws and links them to the technique
+page that owns the mechanism ([[PCIe Link and Atomics]],
+[[Llama Cpp Multi-Device Splits]], [[DFlash DSpark Speculative Decoding]],
+[[Llama Cpp Serving Sizing]], [[Dual-R9700-Cooperation]]).
+
+## Open questions
+
+Two date claims in the era pages do not reconcile, and both are left standing rather
+than silently corrected:
+
+- `frank-medium-rocmfpx.md` banner says the MXFP4 stack replaced that era and, in the
+  next sentence, names [[frank-medium-llamacpp-dflash2]] as the active successor. The
+  MXFP4 replica era and the llama layer-split era both open on 2026-09-16, so which
+  one directly followed the ROCmFPX fork cannot be settled from the repo.
+- `frank-medium-radiance-mxfp4.md` dates its own retired era to 2026-10-10, while
+  [[frank-archon]]'s Eras table opens on 2026-09-26. The gap is either an unrecorded
+  fortnight on that endpoint or a stale banner; nothing else in the repo covers
+  2026-09-26 → 10-10 for port 7770.
+
+## Files
+
+No repo files own this endpoint: its units, env and serve scripts were renamed to
+`frank-archon` on 2026-10-10 and are owned by [[frank-archon]]. `scripts/old/` holds
+retired serve scripts from these eras as reference only.