albok-dev withdrew the judge sign-off on fleet-scale evidence and brokkr concurred: over 10,841 texts judged by both models, h2o flagged 242 adult at 0.5 against INC's 88, and no threshold reproduces INC's set. rollback-to-inc.sh ran 14:03:28, INC healthy 14:03:56, /decide/shared smoke 200 x3. compose.yaml is INC again; the h2o compose is kept as compose.h2o.yaml with switch-to-h2o.sh (GPU 1 free-memory gate, falls back to INC). It now carries Prime's inline-images-only setting: LIGHTNING_IMAGE_URLS=off on the front (verified live: an https image URL is refused before any fetch, inline images still answer) and vLLM --allowed-media-domains media.invalid as a backstop. rollback-to-inc.sh no longer leaves timestamped compose copies behind.
h2o-eval (TEMPORARY) — fv-ml1 GPU 3, :8034
DOWN since 2026-10-12 1319 PT (
docker compose down), once the GPU 1 cutover's post-checks passed. The host keeps/opt/docker/compose/h2o-evaland the weights, so it can come back on GPU 3 for a transient test withdocker compose up -d.
h2o-lightning-4b @ b43f759b behind services/h2o-decision-front (copied into conf/front/), for albok-dev's
re-validation of Nemi's sensitivity judge before the GPU 1 cutover (Prime 2026-10-12 via brokkr). Remove right after
the cutover: GPU 3 is for transient work only (Scriberr and MIA use it).
- Weights:
/tank/aimodels/h2o-lightning-4b-b43f759b(copied from the bench kit; model.safetensors sha2562d51561f221e1549d91bd1c38b3512a1435dd32950d454a9f040f1d4d11497b6, tokenizer.json5f9e4d49…, shim git oidfee7807e…, serve_config5e6fef1c…: all equal to Hugging Face at b43f759b). - vLLM exactly as benched:
--max-model-len 40960 --max-num-seqs 16 --gpu-memory-utilization 0.1506, vision limits as the vendor's serve.sh; healthy ~3 min afterup(graph capture), ~14.4 GB on GPU 3. .envon the host:FRONT_TOKEN= intern-decision's token (= vaultalbok/judge-token).- Remove:
cd /opt/docker/compose/h2o-eval && docker compose down(the weights stay for the GPU 1 seat).