docs(vault): retire the ACTIVE labels on frank-medium era pages (cluster C5)
The root and LLM index pages still advertised two retired endpoints' pages as live procedure: - `frank-medium-radiance-mxfp4`: frontmatter said "ACTIVE frank-medium runbook" and the body opened "The ACTIVE frank-medium deployment". Both re-keyed to the era it ran (2026-09-21 -> 10-10), with [[frank-archon]]'s Eras table named as the owner of that shape. - `frank-medium-model-swap`: read as live how-to for a retired endpoint. Re-keyed to historical, pointing at [[Model Swap and Rollback]] for the current swap law. - Both index pages' rows re-keyed to match (rows are hand-copied from frontmatter - no generator - so both sites move together). Refs: vault de-dup campaign, cluster C5.
This commit is contained in:
1 parent
73fb27254e
commit
6a8cbde260
4 files changed
+15
-13
No files matched your search
@@ -1,7 +1,7 @@
|
||||
---
|
||||
type: runbook
|
||||
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 procedure (frank-medium is a retired endpoint; `:7770` on Dankserver is [[frank-archon]] today and the live swap law is [[Model Swap and Rollback]]) — how a checkpoint swap behind frank-medium worked: 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.
|
||||
tags:
|
||||
- frank-medium
|
||||
- dankserver
|
||||
@@ -14,12 +14,13 @@ timestamp: 2026-09-20
|
||||
|
||||
# frank-medium Model Swap
|
||||
|
||||
Swapping the checkpoint behind **frank-medium** (Dankserver `:7770`,
|
||||
vllm-radiance TP=2) is a four-step process, and the toolchain below drives all
|
||||
of it. The design goal (2026-09-20, after the MXFP4 → FP8 swap) is that a swap
|
||||
is **one command**: generate a manifest, download it verified, point the
|
||||
quadlet at it, deploy. The entrypoint is quantization-aware, so the only repo
|
||||
change a swap makes is the quadlet's four env vars.
|
||||
**Historical.** frank-medium is a retired endpoint — `:7770` on Dankserver is
|
||||
[[frank-archon]] today, and the live procedure is [[Model Swap and Rollback]].
|
||||
This page records how a swap worked in that era: a four-step process whose design
|
||||
goal (2026-09-20, after the MXFP4 → FP8 swap) was that a swap be **one command** —
|
||||
generate a manifest, download it verified, point the quadlet at it, deploy. The
|
||||
entrypoint was quantization-aware, so the only repo change a swap made was the
|
||||
quadlet's four env vars.
|
||||
|
||||
## Why this exists
|
||||
|
||||
|
||||
Reference in new issue
Block a user