Qwen3.6-35B-A3B-Uncensored-Heretic-REAP-30-bf16
Overview
Qwen3.6-35B-A3B-Uncensored-Heretic-REAP-30-bf16 is a BF16 checkpoint preserving the model in a broadly supported training and inference format, published by groxaxo.
It is intended for open-source evaluation, reproducible experimentation, and compatible local or
hosted inference workflows. The wording below is deliberately limited to what can be verified
from this repository's metadata and artifacts.
The repository name identifies a behavior-modified or reduced-filtering lineage. That label describes the source or conversion history; it is not a guarantee of unrestricted behavior in every prompt or runtime. Test outputs carefully before sharing or deploying them.
At a glance
| Field | Details |
|---|---|
| Format | BF16 |
| Source / base | the source checkpoint identified in the repository metadata |
| Intended task | text-generation |
| License | the license declared in the repository files |
What is included
*.safetensors(3 files)config.jsongeneration_config.jsontokenizer.jsontokenizer_config.jsonchat_template.jinja- Additional configuration, tokenizer, processor, or shard files (9 visible artifacts total)
Quick start
Getting started
Start with the upstream library named in the repository metadata and keep all configuration,
tokenizer, processor, and weight files together. This repository is an artifact release, so the
source project remains the authoritative reference for task-specific loading code.
Compatibility and responsible use
- Use a runtime that explicitly supports this format, architecture, and modality.
- Keep configuration, tokenizer, processor, projection, and weight files from the same revision together.
- Review the source model card and license before redistribution or deployment.
- Hardware needs depend on parameter count, context length, cache precision, quantization, and concurrency.
- Report reproducible issues with the runtime version, hardware, launch command, and a minimal example.
Generated outputs may be inaccurate or unsuitable for a given use case. Users are responsible for
testing behavior, applying appropriate safeguards, and complying with applicable licenses and laws.