Files
serverAppConfigs/serverAppConfigs-docs/LLM/frank-medium.md
T
Frank a5fe045b58 docs(vault): one fact, one owner — repair the doubled pages, single-source the facts
Structural repair:
- 13 pages were the same document twice (each exactly 2x its HEAD size),
  a second frontmatter block whose closing fence had been glued onto a body
  line by a frontmatter rewrite that re-read its own output. Un-doubled by
  cutting at the second frontmatter and keeping the copy whose body is a
  superset; the orphan census reports 0 lost tokens against HEAD.
- log.md: one entry per date, bare `## YYYY-MM-DD` headings, newest first —
  66 dated headings merged into 34, titles demoted to bold leads, every
  content line verified present. The file had been descending at the head
  and ascending at the tail.

Ownership moves:
- New `LLM/frank-medium.md` is the locator for the retired Dankserver
  endpoint: era windows quoted from each era page's own banner, no numbers
  restated, and the two unresolved date conflicts recorded instead of
  silently resolved. `frank-archon.md` links to it instead of restating the
  pre-rename window.
- The four Pipeline-Parallelism stubs (frontmatter only, no body) are gone;
  `Multi-Node Runtimes.md` owns runtime construction, launch, mixed-vendor
  verdicts and cross-split spec decode, and the four links that pointed at
  the stubs were repointed at it or at the drafter page.
- Authentik's three stub pages fold into `Authentik.md`, with the process
  detail and the outpost reference split out so the parent stays under the
  length hint.

Verified corrections (host census + live probe, 2026-10-19):
- The MXFP4 checkpoint two pages called the "on-disk rollback" is gone:
  /home/dank/models/ holds StillDeadcode, rad and tpl.jinja. Stated once, on
  the era page that owns that payload; the swap page now links to it.
- frank-medium-radiance-mxfp4: the 4.24/7 accept rate belongs to the DFlash2
  arm measured on the FP8 target, not to the MXFP4 era; the 3-family soak run
  census is kept once (155 requests) instead of twice (~120 and 155).
- Fleet shapes re-confirmed against the live endpoints before touching any
  page: 3x200000 fp8 KV, 2x200704, 2x262144.

Index rows are regenerated, not hand-carved. Net -1,849 vault lines.
2026-10-19 05:00:43 -07:00

66 lines
3.8 KiB
Markdown

---
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 | llama.cpp, ROCmFPX fork pinned at commit `36e9acd` | `Qwen3.8-27B-Q8_0_ROCMFPX_AGENT.gguf` (custom tensor type 103) | single card; the fork is the only loader | [[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, then MXFP6 (`paroquant_mxfp6`) with bf16 KV | `--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.