NOTE: I have tested this and althgouh its capabilities are in tact, it seems to still respond with refusals. Or at least this is what happens with the quantization oft, at IQ4_XS GGUF, at least.
It was produced with a local gradient abliteration pass against the language model's refusal direction. The uploaded repository intentionally keeps the full HF/Transformers BF16 layout so it can be used later as a clean source for GGUF, AutoRound, AWQ, EXL3, NVFP4, GPTQ, FP8, or other quantization workflows.
The modification targets self_attn.o_proj weights in all 45 text layers. A refusal-associated direction was extracted by gradient backpropagation through the BF16 model, then projected out of the attention output projection weights with a small norm-preserving update.
In plain terms, the goal was to reduce excessive refusals, moralizing, policy-style deflections, and over-filtered responses while keeping the model close to the original Step-3.7-Flash behavior.
No tokenizer vocabulary, embedding table, architecture, vision encoder, or MLP/expert tensor was intentionally changed by the abliteration pass.
If using multi-GPU llama.cpp inference in the original local environment, GGML_CUDA_NO_PEER_COPY=ON was required for coherent output.
Indexed shard inventory
The active model.safetensors.index.json references 26 safetensor files:
File
Size
model-00001.safetensors
924,094,096
model-00002.safetensors
9,808,156,008
model-00003.safetensors
18,557,475,928
model-00004.safetensors
18,624,846,944
model-00005.safetensors
18,557,475,928
model-00006.safetensors
18,624,846,976
model-00007.safetensors
18,557,475,968
model-00008.safetensors
18,624,846,976
model-00009.safetensors
18,557,475,968
model-00010.safetensors
18,624,846,976
model-00011.safetensors
18,557,475,968
model-00012.safetensors
18,624,846,976
model-00013.safetensors
18,557,475,968
model-00014.safetensors
18,624,846,976
model-00015.safetensors
18,557,475,968
model-00016.safetensors
18,624,846,976
model-00017.safetensors
18,557,475,968
model-00018.safetensors
18,624,846,976
model-00019.safetensors
18,557,475,968
model-00020.safetensors
18,624,846,976
model-00021.safetensors
18,557,475,968
model-00022.safetensors
18,624,846,976
model-00023.safetensors
9,245,052,456
model-00024.safetensors
6,968,188,464
model-vit-00001.safetensors
1,613,990,904
model-vit-00002.safetensors
2,348,122,376
model-00025.safetensors and model-00026.safetensors are not referenced by the active index used here and are not required by this uploaded model layout.
Performance / benchmark status
Formal KL/refusal/MMLU tables have not yet been run for this Step-3.7-Flash release. To avoid inventing numbers, the benchmark fields are listed as pending.
Lower refusals indicate fewer content restrictions, rejections, objections, pushbacks, lecturing, censorship, softening, and deflections. Lower KL divergence indicates closer behavior to the original model baseline.
MMLU test results
MMLU has not yet been run for this release. Once measured, this section should include original-vs-heretic totals, accuracy, parse failures, and per-subject scores, following the same format used by comparable Heretic model cards.
Expected behavior
Compared with the base model, this version should generally exhibit:
fewer refusals on benign requests that the base model over-filters
less moralizing, policy language, and safety boilerplate
more direct task completion
similar architecture and tokenizer compatibility to the original
No formal refusal/KL/MMLU table is claimed yet for this release. Please run your own evaluations before deployment.
Limitations
This is abliteration, not supervised fine-tuning or RLHF.
It may reduce refusals but does not guarantee any specific behavior.
It can affect calibration, safety behavior, and edge-case instruction following.
Multimodal behavior has not been separately benchmarked after the text-path patch.
Users should validate downstream quantizations independently.
Safety and responsibility
This model is provided for research and experimentation with refusal-reduction / alignment-ablation methods. You are responsible for complying with applicable laws, platform rules, and the base model's license/terms.