Source and measurements
Base revision: 1bae0e1088993b9b82de08f59de5be5a34e42170.
Patch repository: pqhaz/DeepSeek-V4.1-Flash-1017-heretic, revision 12d58ad0878b5008e80d720251adb969a0069412.
Patch SHA256: 16e63cd3e79c3590855aad340b5b9dc37f27562bf2d0a40f85268915da221ce2.
Local paired chat-mode scores: GSM8K 1276/1319, executed HumanEval 156/164, strict-format MMLU 11824/14042. Original base: 1279, 157 and 11920 respectively. These are local protocols, not official leaderboard scores. Temperature-zero output is not bitwise deterministic.
On four RTX PRO 6000 Blackwell Workstation GPUs, native drafting achieved mean aggregate reasoning throughput of 131.55, 425.19 and 830.06 output tokens/s at concurrency 1, 8 and 32. Three repeated legs used a warm 40K public-code prefix, natural stopping, temperature 1, top_p 1 and a 16384-token output cap. All nine legs passed integrity checks. Unrelated training and embedding workloads remained active.
The official HarmBench classifier passed 95/100 balanced human-majority controls. It scored direct-prompt behavior success on 287/300 edited outputs versus 30/300 base outputs. This measures behavior success, not a generic refusal rate. Full methodology, limitations and plots are in the benchmark dataset.
Run on four 96GB Blackwell GPUs
Use Linux, Docker with NVIDIA Container Toolkit, and sufficient disk for approximately 510.3GB of serialized tensors. The pinned runtime streams Engram tables from disk. The configured 300000-token context and 32 scheduler slots do not imply 32 simultaneous full-context sessions. Runtime cache metadata estimates approximately 15 full 300K contexts before workload overhead; that concurrency was not measured.
hf download Infatoshi/DeepSeek-V4.1-Flash-1017-MXFP4-heretic --local-dir /data/deepseek-modelbash /data/deepseek-model/runtime/serve-native.sh /data/deepseek-model /data/deepseek-cache
The launcher never stops or replaces an existing container. Wait for http://127.0.0.1:8317/health to succeed. The local API model ID is deepseek-v41-local. Remote clients should forward loopback port 8317 over SSH. MODE=off disables speculative decoding for a matched comparison; the default uses DSpark with up to five proposed tokens.
bash /data/deepseek-model/runtime/harnesses/claude-ds.shbash /data/deepseek-model/runtime/harnesses/opencode-ds.shuv run --no-project python /data/deepseek-model/runtime/harnesses/configure-omp.pybash /data/deepseek-model/runtime/harnesses/omp-ds.sh
Install the corresponding clients first. The OMP configuration helper preserves existing providers and refuses to overwrite an existing local-provider entry. The Claude wrapper retains normal instructions, hooks and plugins, selects bypassPermissions, and routes Agent-tool subagents to this same local model. Plain Claude commands launched through Bash regain the normally configured provider. No existing credentials are bundled.
The measured native runtime passed two editing tasks in each harness and a real Claude session reaching 260809 input tokens. That fixture does not establish arbitrary long-context task reliability. Incremental tool-driven growth passed; a single 250K-token initial stdin prompt failed Claude's estimator before reaching the API.
The exact packaged launcher and wrappers were also tested with this staged release as the only model mount. All six editing fixtures passed. The packaged Claude wrapper reached 260,205 input tokens with a reported 300,000-token window, 11 Read calls and no compaction, retaining the checked facts. evaluation/runtime-qualification.json records that full model and launcher check. The subsequent client-only OpenCode fix is recorded in evaluation/client-routing-qualification.json: an explicit CLI model selection prevents a configured agent default from redirecting the main session. A conflicting-agent fixture passed with the exact updated wrapper; server configuration and weight files are unchanged.
Weights retain the upstream MIT license. Runtime components retain their own licenses; included vLLM/B12X material is Apache-2.0. Full-file release hashes and provenance accompany the checkpoint. Raw benchmark requests, generated responses and private machine information are not included.
Additional installed-client long-context evidence
All three clients completed bounded tool-memory fixtures above 250K input tokens with the native model’s 300K server window and no compaction. Claude Code reached 260,205 input tokens using the exact packaged wrapper. Installed OpenCode and OMP aliases reached 281,477 and 255,419, retaining the checked early and final facts. The OpenCode test used stdin rather than a truncated file attachment. OMP required a verifier-only correction for filename:line-range read paths; its original receipt and session were preserved.
See evaluation/installed-harness-long-context.json for receipt hashes and scope. The OpenCode/OMP checks are installed-client evidence, not new exact-package runs. These fixtures do not certify every source line, arbitrary long-context reasoning, media support, or relative client speed. That evidence-only update changed no runtime, configuration or weight file. The later OMP client update is described below.
OMP context budgeting
The bundled omp-ds.sh loads omp-context.yml for that invocation. Automatic compaction and mid-turn checks remain enabled. It reserves 24,576 tokens: the 16,384-token output budget plus 8,192 tokens of headroom. With the 300,000-token window, the reserve-based trigger is 275,424 tokens. The same profile is used by the installed local alias. Global settings and other providers are unchanged.
OMP normally reserves 15% when this setting is unset. An earlier NVFP4 package fixture compacted at 269,638 input tokens under that policy and failed the qualification gate; the failed receipt was preserved. The revised native client configuration passed all six editing tasks. Its exact packaged OpenCode and OMP wrappers reached 281,805 and 259,066 input tokens, retained the checked facts, and completed without compaction or fixture changes. These remain bounded tool-memory tests.
evaluation/omp-context-qualification.json binds the previous and tested runtime hashes and the client results. Only the OMP wrapper and its new configuration file changed; model weights and server configuration did not. The prior Claude long-context result remains recorded separately. See OMP settings for the reserve and per-run overlay semantics.