refact(comments): state the mechanism, not the incident

Every comment that invoked a 'law' (50 word-boundary sites across 28
tracked files) now states what is going on and why, in terms that
transfer to any project: gate twins drift until one side greenlights
what the other refuses; a tag re-points while a digest pins; a
restrictive engine behavior belongs to the runtime that imposed it and
must be re-tested, not inherited; a speculative head is tensors in the
file, not a flag; snapshot links dangle where the container resolves
them; exit 0 is a clean stop to systemd, so a self-exiting daemon on
on-failure goes dark reporting success. Event narratives and dates are
gone from these comments; the mechanics carry the argument.

Behavior-identical: bash -n, py_compile, yaml parse, full bats suite
408/408 green. One symbol rename rides along (stack script local
scale_law -> scale_contract, with its log text).
This commit is contained in:
Frank
2026-10-14 13:36:40 -07:00
parent 65bd5ccea7
commit d4ce76b68b
28 changed files with 195 additions and 164 deletions
+2 -2
View File
@@ -26,8 +26,8 @@ RECIPE=/home/dank/serverAppConfigs-swift15/scripts/recipes/qwen4exp-swift15-w4dn
CALIB=/home/dank/corpora/calib
OUT=/home/dank/models/rad/qwen4exp-swift15-w4dn8-i8-hc8m.rad
LOG=/home/dank/logs/swift15_convert.log
# gate_up ~37.6 + down ~18.8 + PLE 47.7 + trunk/embeddings/head ~10 GiB (all-w4 expert table;
# the plugin's one-encoding law dropped the block-fp8 down tier -- see the recipe header).
# gate_up ~37.6 + down ~18.8 + PLE 47.7 + trunk/embeddings/head ~10 GiB (all-w4 expert
# table; one encoding per expert table rules out a block-fp8 down tier -- see the recipe header).
MIN_MIB=${FRANK_SWIFT15_RAD_MIN_MIB:-108000}
# Gate 1: inputs. A missing Gram directory converts UNCALIBRATED with a
+17 -16
View File
@@ -11,7 +11,7 @@ set -euo pipefail
# The LLM handlers' artifact gates are the serve scripts' own library, so
# the deployer and the unit refuse the same missing payload with the same
# words (the fleet law from the 2026-10-01 crash-loop). GATE_PREFIX is set
# words — no deploy can pass a gate the unit would fail. GATE_PREFIX is set
# per handler.
# shellcheck disable=SC1091
source "$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)/lib/llm-gates.sh"
@@ -926,17 +926,17 @@ deploy_plex() {
systemctl --user restart plex.service
# Readiness gate: /identity answers MediaContainer XML once PMS is up.
#
# HTTPS, NOT HTTP. PMS drops plain HTTP off-loopback: the probe's
# connection arrives on the container's eth0, so an http:// request is
# accepted and then answered with nothing (curl 52, Empty reply) against a
# perfectly healthy server. Measured 2026-10-02 — the gate burned its full
# 600s and failed a plex whose https://127.0.0.1:32400/identity answered
# 200 in 44 ms the whole time. The same law is why the Caddyfile dials the
# plex upstream over TLS (tests/caddyfile.bats pins it).
# HTTPS, NOT HTTP. PMS serves plain HTTP on loopback only: a probe
# arriving on the container's interface gets its connection accepted and
# then an empty reply (curl 52) from a perfectly healthy server, so an
# http:// probe would burn the whole timeout and fail a service that
# answers https://127.0.0.1:32400/identity in milliseconds. The Caddyfile
# dials the same upstream over TLS for the same reason
# (tests/caddyfile.bats pins it).
# -k: PMS presents its own self-signed cert on 32400.
#
# Reality check from the 2026-09 cutover: the FIRST container boot of a
# years-old library ran ~10 min, so the gate still allows 600s.
# The budget accounts for a first boot of a large pre-existing library,
# which spends minutes indexing before it answers anything.
# Fail the deploy (pending state preserved) rather than mark it deployed blind.
for ((i = 1; i <= 120; i++)); do
curl -fsSk --max-time 3 https://127.0.0.1:32400/identity >/dev/null && return 0
@@ -1184,11 +1184,12 @@ deploy_llm_dragoon() {
retire_halogen_dragoon_quadlet
# The predecessor on a re-deploy is THIS unit: stop it (ExecStop stops
# the container) before waiting on the port. The stray sweep is keyed
# on the FULL container name, which appears in the argv of a manual
# `podman run --name frank-dragoon-halogen` / `podman wait` but NOT in
# this deployer's own command line (`bash deploy-remote.sh
# frank-dragoon`) — so it cannot shoot itself in the foot (the fleet
# pkill law), and it can never match frank-zealot's llama-server.
# on the FULL container name: it appears in the argv of a manual
# `podman run --name frank-dragoon-halogen` / `podman wait`, while a
# pattern naming only the runtime would ALSO match this deployer's own
# command line — a pkill whose pattern hits its own argv takes the
# running deploy down with the target. The full name can never match
# frank-zealot's llama-server either.
run_privileged systemctl stop frank-dragoon.service 2>/dev/null || true
pkill -f 'frank-dragoon-halogen' 2>/dev/null || true
podman rm -f frank-dragoon frank-dragoon-halogen >/dev/null 2>&1 || true
@@ -1220,7 +1221,7 @@ deploy_llm_zealot() {
# Refuse rather than restart-loop: a unit whose runtime or payload is
# missing never becomes healthy, and a green deploy would leave the
# endpoint dark with nothing in the log to say why. Same library calls
# as serve-frank-zealot.sh (the 2026-10-01 law).
# as serve-frank-zealot.sh, so the deployer's twin refuses identically.
export GATE_PREFIX=frank-zealot
require_exec "$LLM_ZEALOT_RUNTIME" runtime \
"build it: cmake -B build-cuda -DGGML_CUDA=ON -DCMAKE_CUDA_ARCHITECTURES=86" \
+1 -1
View File
@@ -2,7 +2,7 @@
"""derive-protected-experts.py — rewrite the recipe's protected-expert section
from a calibration recording. RUNS ON DANKSERVER (venv: numpy).
The law (docs/MOE-W4.md "Protected experts", restated in the recipe):
The selection rule (docs/MOE-W4.md "Protected experts", restated in the recipe):
an expert whose share of its layer's down-input energy is at least 3% AND
at least three times its share of the routing is kept bf16; the count must
be EVEN on each rank's half of the layer (the four-bit GEMM takes the rest
+5 -4
View File
@@ -14,10 +14,11 @@
# Fetch uses the vendored scripts/hfget.sh (StillDeadcode's Apache-2.0
# listing/resume downloader, curl+jq only): per-file size checks against
# the Hub listing, `-C -` resume, pickle-format duplicates skipped.
# Verify (default) is the AGENTS.md law in three parts: every listed file
# present with the listed size, the shard count matches the weight-map
# index, and every shard's sha256 equals the Hub's LFS oid. Verify needs
# only the public API.
# Verify (default) is three independent agreements: every listed file
# present with the listed size (catches truncation), the shard count
# matching the weight-map index (catches omissions), and every shard's
# sha256 equal to the Hub's LFS oid (catches substituted content).
# Verify needs only the public API.
set -euo pipefail
REPO="ukisai/Swift1.5-Qwen3.8-Flash-Next"
+5 -4
View File
@@ -12,10 +12,11 @@
# Fetch uses the vendored scripts/hfget.sh (StillDeadcode's Apache-2.0
# listing/resume downloader, curl+jq only): per-file size checks against
# the Hub listing, `-C -` resume, pickle-format duplicates skipped.
# Verify (default) is the AGENTS.md law in three parts: every listed file
# present with the listed size, the shard count matches the weight-map
# index, and every shard's sha256 equals the Hub's LFS oid. Verify needs
# only the public API.
# Verify (default) is three independent agreements: every listed file
# present with the listed size (catches truncation), the shard count
# matching the weight-map index (catches omissions), and every shard's
# sha256 equal to the Hub's LFS oid (catches substituted content).
# Verify needs only the public API.
set -euo pipefail
REPO="Qwen/Qwen3.8-Flash-Next-FP8"
+11 -6
View File
@@ -4,12 +4,15 @@
# .hgn, the REQUIRED lookup table and the optional vision tower from
# peonist-ai/halogen-qwen3.8-flash-next (both at the revisions the model
# card pins), and the flat tokenizer the two repos share. All public, no
# token — and per the fleet secret law, none would ever touch argv.
# token needed — and a secret would never be passed via argv anyway: the
# command line is world-readable through /proc, so any token placed there
# leaks to every process-listing tool on the host.
#
# The fetch law, same as every sibling script: curl -f (an access error
# must not become a "successful" 153-byte artifact), exact byte count from
# the Hub tree API, LFS sha256 verification, --verify-only to re-check an
# existing payload without downloading.
# The fetch rules, uniform across every sibling script: curl -f so an
# access error fails loudly instead of writing the error body as a
# "successful" tiny artifact; the exact byte count from the Hub tree API;
# LFS sha256 verification; --verify-only to re-check an existing payload
# without downloading.
#
# File manifest (verified against the Hub tree API on 2026-10-06):
# qwen38-flash-next-v2-swift15-abliterated.hgn 66,687,678,464 B sha256
@@ -26,7 +29,9 @@
# tokenizer/* @e053f488 — byte-identical to the 27B-era tokenizer
# already on disk (tokenizer.json LFS
# 0997f410c57a1f4e53b09e4be8f4a172d90edd9564368fb0847030937229b9f3);
# fetched fresh rather than symlinked, per the no-symlink law.
# fetched fresh, never symlinked: a snapshot link points into the
# host-side cache directory, which does not exist inside the
# container mount, so the link dangles exactly where it is consumed.
set -euo pipefail
DEST="${FRANK_DRAGOON_MODEL_DIR:-$HOME/models/halogen-flashnext-v2}"
+8 -6
View File
@@ -1,13 +1,15 @@
#!/usr/bin/env bash
# download-frank-dragoon-halogen.sh — fetch frank-dragoon's halogen payload:
# the qwen3.8-27b .hgn checkpoint and the export tokenizer, from the
# PUBLIC peonist-ai/halogen-qwen3.8-27b repo (no token — and per the fleet
# secret law, none would ever touch argv).
# PUBLIC peonist-ai/halogen-qwen3.8-27b repo (no token — and a token
# would never travel in argv: command lines are world-readable through
# /proc, so a secret placed there leaks to any process-listing tool).
#
# The fetch law, same as every sibling script: curl -f (an access error
# must not become a "successful" 153-byte artifact), exact byte count from
# the model card, LFS sha256 verification, --verify-only to re-check an
# existing payload without downloading.
# The fetch rules, uniform across every sibling script: curl -f so an
# access error fails loudly instead of writing the error body as a
# "successful" tiny artifact; the exact byte count from the model card;
# LFS sha256 verification; --verify-only to re-check an existing payload
# without downloading.
set -euo pipefail
DEST="${FRANK_DRAGOON_MODEL_DIR:-$HOME/models/halogen-qwen3.8-27b}"
+7 -7
View File
@@ -11,13 +11,13 @@ Tensor extents are DERIVED from consecutive GGUF header offsets — no quant
type-size table (those are easy to get subtly wrong; a wrong per-element size
silently under-covers each tensor and dumps tail samples into a junk bucket).
Fleet law this instrument established (2026-09-26, 75 s window, 4 mixed
streams, 2.7M expert-tensor samples): per-BLOCK read volume is FLAT
(0.93x-1.08x of mean across all 40 CPU-resident blocks) because MoE top-k
routing fires every block every token — there are no "most active layers" at
`-ot` granularity. The real skew is per-EXPERT (top 10% of (block,expert)
cells carry ~40% of samples), which tensor-level overrides cannot reach.
Any 8 GPU-resident blocks are therefore equivalent; COUNT is the only lever.
What this instrument settles: per-BLOCK expert read volume is FLAT across
all CPU-resident blocks, because MoE top-k routing fires every block on
every token — there are no "most active layers" at `-ot` granularity. The
real skew is per-EXPERT: a small fraction of (block,expert) cells carries
most of the samples, and tensor-level overrides cannot reach that level.
Any fixed number of GPU-resident blocks is therefore equivalent; COUNT is
the only lever.
Usage (needs passwordless sudo for perf only; model files must be readable):
fp-expert-activity.py <pid> [duration_s] # dump + sample + analyze
+14 -12
View File
@@ -115,15 +115,16 @@ FRANK_ARCHON_TP=2
FRANK_ARCHON_TP_WIRE=wht6
# Decode slots: TWO, so the served window is a CAPACITY CONTRACT — two
# concurrent conversations of --max-model-len fit the KV pool (see the KV
# block below). The "seqs 2 cannot boot" law is NOT radiance's: it was the
# tcclaviger vLLM fork's torch.compile shape specialization on
# query_start_loc (ConstraintViolationError, measured 2026-10-02, retired
# with that runtime). Radiance booted seqs 2 at the fp8-native first boot,
# and the 2026-10-06 decode sweep measured seqs 2 and 3 statistically tied
# (30.9-33.1 t/s, inside the +-3% noise floor). Side benefit: the fused TP
# all-reduce is declared over seqs x (1 + spec) = 6 rows, under the 25-row
# bound at which the wht6 wire stays EXACT (single-sequence decode and any
# step of <= 25 rows is bit-exact; only busier steps are lossy).
# block below). Slot-count limits observed on other runtimes do NOT
# transfer: a "this slot count cannot boot" refusal is usually that
# runtime's compiler specializing shapes (e.g. a ConstraintViolationError
# from shape specialization on query_start_loc), not a property of the
# engine now running. This engine boots seqs 2, and seqs 2
# vs 3 decode measurements land inside each other's noise floor. Side
# benefit: the fused TP all-reduce is declared over seqs x (1 + spec) = 6
# rows, under the 25-row bound at which the wht6 wire stays EXACT
# (single-sequence decode and any step of <= 25 rows is bit-exact; only
# busier steps are lossy).
FRANK_ARCHON_MAX_SEQS=2
# Served window. Native is 262,144; 200,000 is the publisher's production
# value (compose) and what models.yml's contextWindow must quote — a longer
@@ -203,9 +204,10 @@ FRANK_ARCHON_MAX_BATCHED_TOKENS=2048
# (104 GiB available with the service loaded).
FRANK_ARCHON_PREFIX_HOST_MIB=8192
FRANK_ARCHON_PREFIX_DISK_MIB=65536
# Frank's pin law: the PLE n-gram table (47.7 GiB) serves from pinned host
# RAM the cards read. `ram` REFUSES the start if the memlock limit is too
# small — the unit's LimitMEMLOCK=infinity is the other half of this law.
# The PLE n-gram table (47.7 GiB) serves from pinned host RAM the cards
# read. `ram` REFUSES the start if the memlock limit is too small — a
# named refusal beats a mid-load allocator failure — and the unit's
# LimitMEMLOCK=infinity is the other half of the arrangement.
FRANK_ARCHON_NGRAM_PLACEMENT=ram
# TTM preflight: the pinned ledger (2 x 44 GiB pools + 47.7 GiB PLE + 8 GiB
# prefix host = ~147 GiB) rides TTM's shared pages, capped by ttm's
+9 -7
View File
@@ -42,10 +42,11 @@
# form of the engine's default, so the seam test can pin the product.
# KV costs ~28 KiB/position (FLAGS.md) => 524,288 x 28 KiB = 14.0 GiB.
# HALOGEN_KV_SLOTS=2 restores the w4b-era shape on this box: the MTP
# drafter is NOT slot-locked on this engine (batching and speculation
# coexist — DFlash-era slots>1 law does NOT carry over; the card's own
# quickstart ships 2 slots WITH the head), so the second slot is
# concurrent capacity, not a speculation tax.
# drafter is NOT slot-locked on this engine. A "slots > 1 disables the
# drafter" restriction is a property of the engine generation that
# imposed it, not of speculation itself — batching and speculation
# coexist here, and the card's own quickstart ships 2 slots WITH the
# head — so the second slot is concurrent capacity, not a speculation tax.
# Memory ledger against the box's 121.2 GiB unified (the n-gram table is
# mmap'd page cache beside the checkpoint, not a pinned charge — the
# card's own quickstart arithmetic does not bill it):
@@ -88,9 +89,10 @@
# before. Kernel needs CONFIG_HSA_AMD_SVM (CachyOS ships it) and
# amdgpu.noretry=0 (check at deploy).
# Image: digest-pinned (fetch law: tag pulls silently re-point; the digest
# is what was qualified). 0.16.2 = the version the model card names as its
# quickstart pin; RepoDigest captured at pull on 2026-10-06.
# Image: digest-pinned, not tag-pinned — a tag can be re-pointed to a
# build that was never qualified here, while the digest pins exactly the
# build that was tested. 0.16.2 = the version the model card names as its
# quickstart pin; the RepoDigest was captured at a pull of that tag.
FRANK_DRAGOON_IMAGE=ghcr.io/peonist-ai/halogen-flash-server@sha256:0c61bf84ac22308a53f5d1ca6b86806702d7039e5ebc51cae4c66621b92fe04a
# Container identity: kept from the 27B era (unit ExecStop names it).
FRANK_DRAGOON_CONTAINER=frank-dragoon-halogen
+5 -5
View File
@@ -16,11 +16,11 @@
# custom-quant lock-in like the ROCmFPX era). NO nextn/mtp tensors exist, so
# in-file MTP is impossible here; SPEC_TYPE=none is forced by the payload.
#
# KV rate law: 8 full layers × 4 KV heads × 256 dim = 8,192 elements per
# token per cache. f16 K + f16 V = 32,768 B/token = 32 KiB/token, so the
# 401,408-token pool is 12.25 GiB. The 24 DeltaNet layers cost a fixed
# recurrent state per SLOT (not per token) — that is why two 200k slots fit
# where the 26B MoE fit only one.
# The KV rate follows from the architecture: 8 full layers × 4 KV heads ×
# 256 dim = 8,192 elements per token per cache. f16 K + f16 V = 32,768
# B/token = 32 KiB/token, so the 401,408-token pool is 12.25 GiB. The 24
# DeltaNet layers cost a fixed recurrent state per SLOT (not per token) —
# that is why two 200k slots fit where the 26B MoE fit only one.
#
# Feasibility comes from the predecessor's MEASURED boots, not a formula:
# MiMo-V2.6-Distill-Qwen-9B (identical qwen35 geometry, 7,793,710,624 B) at
+5 -4
View File
@@ -12,10 +12,11 @@ Group=dank
LimitMEMLOCK=infinity
Environment="FRANK_ZEALOT_ENV_FILE=/home/dank/serverAppConfigs/scripts/frank-zealot.env"
ExecStart=/home/dank/serverAppConfigs/scripts/serve-frank-zealot.sh
# Restart=always, the fleet law for LLM units: exit 0 is a CLEAN stop to
# systemd, so on-failure leaves the endpoint dark (and the unit reporting
# success) until the next boot. frank-zealot is the fleet's compaction hub —
# every endpoint's compaction dies when it does.
# Restart=always is the right policy for a serving daemon: a process that
# exits on its own — exit 0 — is a CLEAN stop to systemd, so on-failure
# never fires and the endpoint stays dark (with the unit reporting
# success) until the next boot. frank-zealot is the fleet's compaction
# hub — every endpoint's compaction dies when it does.
Restart=always
RestartSec=10
+14 -12
View File
@@ -1,10 +1,11 @@
#!/usr/bin/env bash
# llm-gates.sh — the artifact gates every LLM endpoint runs before it starts.
#
# Why this file exists: the fleet law from the 2026-10-01 crash-loop is that
# a serve script and the deployer must refuse the SAME missing/truncated
# artifact, the SAME way. When the two gates were hand-written twins they
# drifted mid-cutover — green deploy, red unit, every time the payload moved.
# Why this file exists: every LLM endpoint gates its payload twice — the
# serve script at start, the deployer before dispatch. Two hand-written
# copies of the same checks drift apart in wording and strictness, and the
# drift surfaces as deploy-time disagreement: one side passes, the other
# refuses, and the failure lands in production instead of in the gate.
# Both sides source this library, so the refusal is one text and one rule.
#
# Contract (public interface):
@@ -27,9 +28,10 @@
# disagree. The deployer's old "halogen vision tower" and the serve script's
# "vision-tower" were one gate in two vocabularies that no grep could join.
# The size law is equality, not a floor, for `require_bytes`: a hub fetch
# that truncates is the fleet's standing hazard (curl exits 0 on 401/403 and
# writes the error body as the artifact), and the declared byte count is a
# Size checks use equality, not a floor, for `require_bytes`: a fetch that
# truncates looks like a success (an HTTP error exit is often swallowed, and
# the error body is written in the artifact's place), so "exists and is big
# enough" is not proof of the right artifact. The declared byte count is a
# contract in both directions — a bigger file is a DIFFERENT artifact.
# GATE_PREFIX names the endpoint in every refusal (e.g. frank-dragoon). The
@@ -38,7 +40,7 @@
# shellcheck disable=SC2034
: "${GATE_PREFIX:=gate}"
# Two bash laws make the `return 1` at every call site load-bearing:
# Two bash behaviors make the `return 1` at every call site load-bearing:
# * a function whose body ends inside an `if` returns the CONDITION's
# status (true = 0), so a gate that ends on its own refusal prints the
# refusal and reports SUCCESS;
@@ -100,10 +102,10 @@ require_min_mib() {
}
# require_dir_files — DIR must be a directory and every named member a
# regular file (the flat-tokenizer law: snapshot symlinks dangle in the
# container mount even when the directory itself is real. A symlinked
# DIRECTORY is refused too: a HF cache snapshot can link the directory
# itself, and a link dangles inside the container mount.
# regular file, never a symlink: snapshot layouts link files into place, and
# a link dangles inside the container mount even when the directory itself
# is real. A symlinked DIRECTORY is refused too — the same layout can link
# the directory itself, and the link dangles identically.
require_dir_files() {
local dir="$1" label="$2" hint="$3"
shift 3
@@ -29,10 +29,11 @@
# its base SupportsEagleBase (has_own_lm_head, has_own_embed_tokens) -- and
# getattr_static()s each one off the instance, breaking on the first miss.
# So BOTH wrappers need all three attributes.
# * MRO law: INHERITING SupportsEagle3 as a base dies at class creation with
# "Cannot create a consistent method resolution order (MRO) for bases ..."
# (GLM's wrappers already carry four/five Protocol-derived bases). The
# attribute route avoids the MRO entirely. Also proven by simulation:
# * Why not inheritance: adding SupportsEagle3 as a BASE class dies at
# class creation with "Cannot create a consistent method resolution
# order (MRO) for bases ..." (GLM's wrappers already carry four/five
# Protocol-derived bases; the base ordering cannot take another). The
# attribute route avoids the MRO entirely; simulation confirms that
# the four-base ForCausalLM ordering cannot take SupportsEagle3 in ANY
# position.
# * Method placement: without inheriting, the Protocol's default
+6 -4
View File
@@ -9,7 +9,9 @@ No scratch container, no mask: the service under test is the service.
Three probes, in increasing cost:
A decode at depth — one ~51k-token chat completion, 512 tokens, greedy.
Reports the engine's own `timings` (prefill, decode, draft acceptance).
The bench law applies: >=128 generated tokens, greedy, real text.
Method: >=128 generated tokens (below that, first-token latency
dominates the decode rate), greedy (sampling noise is unattributable),
real text (synthetic text inflates draft acceptance).
B the capacity contract — TWO concurrent chats of ~197k prompt tokens
(~394k tokens resident) each carrying a unique marker at its head. Both
must answer their own marker. This is what a 2 x 200,000 endpoint owes:
@@ -17,11 +19,11 @@ Three probes, in increasing cost:
C prefix-cache restore — probe A's cold prompt again, so the disk tier has
to give the blocks back (cache_n > 0, TTFT collapses).
PROBE LAW (learned the hard way, twice): radiance routes the thinking block to
PROBE PITFALL: radiance routes the thinking block to
`reasoning_content`, so a chat request whose budget is spent inside
`<think>` returns EMPTY `content` with `finish_reason: stop`. A probe that
reads `content` alone scores 0/2 on a healthy server. Every request here sets
chat_template_kwargs.enable_thinking=false and reads both fields.
reads `content` alone scores 0/2 on a healthy server. Every request here
sets chat_template_kwargs.enable_thinking=false and reads both fields.
A/B method for a shape change (no scratch container): write a variant env file
on the host, point a transient systemd drop-in at it
@@ -1,10 +1,12 @@
# qwen4exp-swift15-w4dn8-i8-hc8m.recipe -- the Swift 1.5 finetune of Qwen3.8-Flash-Next
# (ukisai/Swift1.5-Qwen3.8-Flash-Next, BF16 source, 335.3 GiB, key set identical to the official
# base) as a radiance container for frank-archon: EVERY routed expert -- gate_up AND down --
# through GPTQ into the w4nl64a8h table. The plugin's one-table-one-encoding law
# ("one table of experts takes one encoding, and only a whole expert kept plain bf16 is served
# beside it", qwen4exp_fp8 rad_arch_declare) forbids the original split tier (down block-fp8 +
# gate_up w4): the served kernel is w4nl64a8h for the whole expert set, bf16 experts beside it.
# through GPTQ into the w4nl64a8h table. The converter declares ONE
# encoding per expert table (qwen4exp_fp8 rad_arch_declare): the served
# kernel covers the whole expert set, and the only legal mixed layout is a
# WHOLE expert kept plain bf16 beside it. That rules out the original
# split tier (down block-fp8 + gate_up w4), which asks one table for two
# encodings.
# The rest is qwen4exp-w5dn64-i8-hc8m.recipe verbatim: int8 trunk linears, block-fp8 hc mixers
# and MTP fc, the fixed-scale n-gram table, the 2-bit draft head.
#
@@ -25,11 +27,14 @@
# The protected experts, cast to bf16 ahead of both expert rules. THE NAMES BELOW ARE THE BASE
# CHECKPOINT'S (from its 1M-token recording, qwen4exp-w5dn64-i8-hc8m.recipe) -- a warm start only.
# The Swift 1.5 finetune's routing distribution is not assumed equal: the derivation step rewrites
# this section from Swift's OWN calibration recording before this recipe is ever run, by the base's
# law -- an expert whose share of its layer's down-input energy is at least 3% and at least three
# times its share of the routing, an even count on each rank's half of the layer (the four-bit GEMM
# takes the rest as two equal tables by parity) by adding that half's next most energetic expert.
# The Swift 1.5 finetune's routing distribution is not assumed equal: the
# derivation step rewrites this section from Swift's OWN calibration
# recording before this recipe is ever run. The selection rule is the base
# checkpoint's: an expert whose share of its layer's down-input energy is
# at least 3% AND at least three times its share of the routing; an even
# count on each rank's half of the layer (the four-bit GEMM takes the rest
# as two equal tables by parity), padded with that half's next most
# energetic expert.
# PROTECTED-BEGIN (rewritten from Swift's OWN grams by derive-protected-experts.py)
blk.1.ffn_*_exps.271.weight cast dtype=bf16
blk.1.ffn_*_exps.355.weight cast dtype=bf16
+3 -2
View File
@@ -28,8 +28,9 @@ set -euo pipefail
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
# The artifact gates are the shared library: the serve script and the
# deployer must refuse the same missing/truncated payload with the same
# words (the fleet law from the 2026-10-01 crash-loop).
# deployer gate the same payload, and two hand-written copies of the same
# checks drift apart until one side passes what the other refuses. One
# library, one refusal text, one rule.
export GATE_PREFIX=frank-archon
# shellcheck disable=SC1091
source "$SCRIPT_DIR/lib/llm-gates.sh"
+4 -3
View File
@@ -72,9 +72,10 @@ set +a
require_image "$FRANK_DRAGOON_IMAGE" \
"pull it: podman pull docker://$FRANK_DRAGOON_IMAGE" || exit 1
# Size-exact gates on all three payload files: a truncated curl exits 0 on
# some failures and a partial .hgn loads far enough to look alive, so the
# byte counts from the Hub tree API are the contract (fleet fetch law).
# Size-exact gates on all three payload files: a truncated download can
# exit 0, and a partial .hgn loads far enough to look alive, so existence
# proves nothing. The byte count published by the Hub tree API is the
# contract: any other size is a different (broken) artifact.
require_bytes "$FRANK_DRAGOON_MODEL_DIR/$FRANK_DRAGOON_CHECKPOINT" \
checkpoint "$FRANK_DRAGOON_CHECKPOINT_BYTES" \
"fetch it: bash scripts/download-frank-dragoon-flashnext.sh" || exit 1
+8 -7
View File
@@ -29,9 +29,10 @@ set -euo pipefail
SCRIPT_DIR="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd)"
# The artifact gates are the shared library: the serve script and the
# deployer must refuse the same missing payload with the same words
# (scripts/lib/llm-gates.sh; the fleet law from the 2026-10-01 crash-loop).
# The artifact gates are the shared library (scripts/lib/llm-gates.sh): the
# serve script and the deployer gate the same payload, and two hand-written
# copies of the same checks drift apart until one side passes what the
# other refuses.
export GATE_PREFIX=frank-zealot
# shellcheck disable=SC1091
source "$SCRIPT_DIR/lib/llm-gates.sh"
@@ -69,9 +70,9 @@ fi
# FP8 class; no true fp8 KV dtype exists in this build).
: "${CACHE_TYPE_K:=f16}"
: "${CACHE_TYPE_V:=f16}"
# Speculative decoding is OFF: this Q6_K file carries NO nextn/mtp tensors, so
# there is no in-file head (the law: MTP is a property of the file, not of the
# flags). SPEC_TYPE=none strips BOTH speculative flags (flags move as a set);
# Speculative decoding is OFF: this Q6_K file carries NO nextn/mtp tensors,
# so there is no in-file head — a speculative head is a property of the
# model file, not of the flags; no flag creates tensors that are absent.
# naming a drafter requires SPEC_DRAFT_FILE alongside SPEC_TYPE — the Gemma4
# assistant on disk is arch gemma4-assistant and cannot drafter-match qwen35.
: "${SPEC_TYPE:=none}"
@@ -89,7 +90,7 @@ fi
# Fail loudly rather than half-loading: a missing file is a download that
# has not finished, and Restart=always would turn it into a crash loop that
# reads like a runtime fault. The refusal text is the shared gate library's,
# so the deployer's twin refuses identically (the 2026-10-01 crash-loop law).
# so the deployer's twin refuses identically.
require_file "$LLAMA_BIN" runtime \
"build it: scripts/build-llama-master-cuda.sh" || exit 1
require_file "$MODEL_FILE" gguf \
+8 -6
View File
@@ -18,11 +18,12 @@ facts written by hand in three config files). They now all read
render pihole-hosts the Pi-hole addn-hosts file
check [NAME...] integrity + drift gates (exit 1 on drift)
Two laws the engine enforces structurally:
Two rules the engine enforces structurally:
* A path selects only services that RUN on the planned target. The old planner
matched paths host-blind and filtered at the end, so a frankbook-pro file
could plan a dankserver service (the stale *arr entries made that reachable).
* A path selects only services that RUN on the planned target. Path
matching that is host-blind (match first, filter later) lets a file on
one host plan a service on another; selection is scoped to the host the
path belongs to.
* The netns family is DERIVED, never declared: a unit file that says
`Network=gluetun.container` rides that tunnel, so a gluetun change selects
every sharer. The unit files are the source of that coupling.
@@ -499,8 +500,9 @@ def check_config(inv: Inventory) -> list[str]:
# --- node-exporter quadlet template (rank 6) --------------------------------
# The two node-exporter units were a MIRROR pair kept in step by a comment.
# The template is now the law; `check` drift-gates both tracked copies.
# Parallel per-host copies kept in step by a comment drift apart; the
# template is the single source, and `check` drift-gates every tracked
# rendering against it.
NODE_EXPORTER_TEMPLATE = """\
# Quadlet unit: node-exporter (rootless, boot-persistent) — RENDERED ARTIFACT.
# Regenerate: python3 scripts/service-map.py render node-exporter-unit --host {host}
+3 -3
View File
@@ -293,12 +293,12 @@ def main():
ddt, dsh = meta[f"{pre0}.mlp.experts.0.down_proj.weight"][3:5]
gsd, gssh = meta[f"{pre0}.mlp.experts.0.gate_proj.weight_scale_inv"][3:5]
dsd, dssh = meta[f"{pre0}.mlp.experts.0.down_proj.weight_scale_inv"][3:5]
scale_law = (gdt == F8 and ddt == F8 and gsd == BF16 and dsd == BF16
scale_contract = (gdt == F8 and ddt == F8 and gsd == BF16 and dsd == BF16
and list(gssh) == [(gsh[0] + 127) // 128, (gsh[1] + 127) // 128]
and list(dssh) == [(dsh[0] + 127) // 128, (dsh[1] + 127) // 128])
if not scale_law:
if not scale_contract:
log(f"ERROR: unexpected expert shapes: gate {gdt}{gsh} scale {gsd}{gssh} "
f"down {ddt}{dsh} scale {dsd}{dssh} (scale law 128x128)")
f"down {ddt}{dsh} scale {dsd}{dssh} (fp8 block scales cover 128x128 tiles)")
return 2
shapes = {"ffn2_h": (gsh[0] * 2, gsh[1]), "ffn": (dsh[1],),
"gs": tuple(gssh), "ds": tuple(dssh)}