Hybrid FP4 experts + FP8 E4M3 blocks + BF16 quality-sensitive tensors, about 169.5 GB on the Hub
Targeted update
46 attn.wo_b weight/scale pairs, with all routed experts and untargeted parent tensors preserved
Verified context
1,048,576 configured; 1,028,621-token prompt accepted with successful needle retrieval
Aggregate decode
118.6 tok/s forced output and 123.3 tok/s structured tool output at p256/C6
Behavior shift
Worst-mode refusal 97.92% -> 4.17%, while the measured tool gates remain 100%
Capability floor
Minimum capability mean 0.9375 -> 0.9583 against the pinned parent
Why run this model
Far fewer unnecessary refusals: the selected checkpoint reduces the measured
worst-mode refusal rate from 97.92% to
4.17%.
Tools stay intact: tool compliance and correct-tool selection remain at
100.00% and
100.00% in the paired release gate.
Real 1M context proof: both 149,845-token and 1,028,621-token needle-retrieval
requests completed successfully.
Fast on two DGX Spark nodes: the measured serving profile reaches
123.3 aggregate tok/s on structured tool generation.
Surgical rather than destructive: experts, routers, embeddings, mHC tensors,
and every untargeted parent tensor retain the official checkpoint representation.
Quantization and precision
MQ in the model name means mixed quantization. This is an
official-layout mixed-precision checkpoint, not a full-BF16 release and not a
custom whole-model requantization.
Table with columns: Component, Precision / storage
Component
Precision / storage
MoE expert weights
FP4, inherited from the official expert_dtype=fp4 checkpoint layout
BF16 (torch_dtype=bfloat16) with F32 metadata/normalization where defined upstream
Output head recovery
One bounded BF16head.weight overlay, rank-64, relative Frobenius delta 0.0025
Measured serving KV cache
NVFP4 DS-MLA
The parent checkpoint is pinned to 9e165c30e2704aec5d9d593cce3eebd58bbef1cb. Only the declared FP8
attn.wo_b pairs and the single bounded BF16 output head are redirected by the final
weight index; the remaining parent tensors keep their original quantization and bytes.
What was changed
The release uses two measured weight-space passes:
OBLITERATUS fits a robust rank-1 refusal direction across chat,
think-high, and think-max modes and applies the selected strength
2.
A second rank-1 residual pass is recaptured from the baked first pass,
orthogonalized against it, and applied at strength
0.5.
A bounded rank-64 output-head recovery was applied; its relative Frobenius delta was 0.0025.
The final checkpoint modifies only the 43 backbone and three MTP attn.wo_b
weight/scale pairs plus the bounded output head. There is no inference-time adapter.
Behavior and capability
Table with columns: Metric, Official parent, SuperDeepseek-V4-Flash-abliterated-MQ-2xDGX
Metric
Official parent
SuperDeepseek-V4-Flash-abliterated-MQ-2xDGX
Worst-mode refusal
97.92%
4.17%
Worst empty answer
0.00%
0.00%
Worst tool compliance
100.00%
100.00%
Worst correct-tool rate
100.00%
100.00%
Minimum capability mean
0.9375
0.9583
The independently reloaded checkpoint reproduced the selected candidate's deterministic
validation behavior exactly. Empty-output, Unicode, repetition, serialization,
reasoning, code, formatting, and tool-use sentinels were included in the release gate.
Decode performance
The numbers below are aggregate concurrent decode throughput, not single-stream speed.
They use six distinct prompts, fixed-length generation, and the sealed
sparkDash-style measurement contract at commit
dfde4214f32b174880832a4d317d3c0567750ac5.
Table with columns: Workload, Prompt / concurrency, Aggregate decode
Workload
Prompt / concurrency
Aggregate decode
Forced output
p256 / C6
118.5505 tok/s
Structured tool output
p256 / C6
123.2888 tok/s
Median matched decode ratio vs the parent: 1.0012x
Minimum matched-case ratio vs the parent: 0.9627x
Regular CUDA graphs vs breakable: 1.2125x at C1 and 1.2674x at C6
Verified long context
Table with columns: Actual prompt tokens, Accepted, Needle retrieved
Actual prompt tokens
Accepted
Needle retrieved
149,845
Yes
Yes
1,028,621
Yes
Yes
The configured maximum is 1,048,576 tokens. These are end-to-end acceptance and
retrieval probes; they are not a claim that every task benefits equally from the full
window.
Two-node DGX Spark serving
The measured profile uses TP=2 over direct CX-7 RoCEv2 with the
ghcr.io/anemll/dspark-vllm-gx10:0.1.1 runtime:
NVFP4 DS-MLA KV cache
DSpark speculative decoding with K=1 and greedy draft sampling
FlashInfer b12x MoE and FlashInfer autotuning
prefix caching, asynchronous scheduling, and chunked prefill
regular CUDA graphs with VLLM_USE_BREAKABLE_CUDAGRAPH=0
The repository includes the exact two-rank launcher under
repro/scripts/serve_superdeepseek_v4_dual.sh. Its measured model-facing options are:
messages=[{"role":"user","content":"Design a reliable tool-using agent."}],
max_tokens=1024,
)
print(response.choices[0].message.content)
Uncensored behavior
“Uncensored” means this checkpoint measurably reduces the selected refusal subspace
while retaining the declared capability and output-integrity gates. It does not imply
that every answer is correct or that downstream deployment controls are unnecessary.
Decode, tool, reasoning, long-context, and output-integrity gates: passed
Machine-readable benchmark and release evidence included under evidence/
Limitations
The speed figures are measured on a specific two-node DGX Spark/CX-7 runtime and
should not be treated as universal hardware results.
Abliteration changes refusal behavior and can produce content the parent would
decline. Operators remain responsible for access control and appropriate use.
The capability and integrity suites are finite regression gates, not proof of
universal correctness.
One million token acceptance does not guarantee perfect recall at every position or
on every task.
The parent model's license and upstream limitations continue to apply.