Will it last?
This page is a projection of the one entry record, the Transparency factor that Support covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.
- AssessUse & modify + Transparency
- ImplementData control + Reliability
- UseReliability
- SupportTransparency
Common problems & fixes
Preview pitfalls, not an exhaustive catalogue:
AutoModelfails to load or reports an unknown architecture: Soofi-S is a custom hybrid Mamba-2/MoE. Passtrust_remote_code=Trueand use a recent transformers build.- Tool calling is silently ignored: the runtime is not applying the native tool template. Run
llama-server --jinja(llama.cpp) instead of a runtime whose template strips tools (e.g. Ollama). - The serving stack rejects the model: custom-architecture support is still maturing. Confirm your vLLM or llama.cpp version supports the hybrid architecture, or fall back to a first-party GGUF build.
- Out-of-memory when loading weights: decode uses ~3B active params, but all ~30B must be resident. Use a first-party GGUF or 3-bit quant or multi-GPU; the near-constant cache means long context is not the cause.
- Non-reproducible results or silent updates: a deployment floating on
mainchanges under you. Pin an exact Hugging Face revision and verify checksums.
Versions, changelog & cadence
Soofi-S is on an early preview/beta cadence, not a settled semantic-version stream. Alongside
Soofi-S-Base there are Instruct-Preview, Isar-Preview (reasoning) and Rhine-Preview variants,
first-party GGUF and 3-bit quant repos, and named iteration checkpoints (e.g. iter_1056000, the
final constant-annealing checkpoint used for evaluation). Versions are tracked as Hugging Face
revisions on the Soofi-Project org, so the revision hash is the changelog anchor: pin it and
diff against a newer revision when upgrading. The pretraining technical report documents
architecture, data and evaluation for the release.
Community & support channels
Usage questions go to the model and dataset discussion tabs on the Soofi-Project Hugging Face
org (ev-hf-org). Training-code and reproduction problems go to GitHub issues on
soofi-project/Soofi-Pretraining, soofi-trainer and soofi-model-hosting (ev-github).
Announcements come from the soofi.info project site and the CAIRNE launch page (ev-cairne),
plus the KI-Bundesverband-coordinated consortium behind the project. There is no paid support
tier; support is community and consortium based.
Tracked known issues
These come from model-card caveats, not a formal issue tracker, so coverage is partial.
- Preview status: capability, safety and tooling are still stabilising.
- Safety and privacy features are documented as incomplete, with no companion guard model.
- Tool-call templates are inconsistent across runtimes (native under
--jinja; omitted by some). - Runtime support is immature: not every serving stack and version handles the hybrid Mamba-2/MoE yet.
How this scores
The ownership factor this domain covers, drawn from the one entry record.
TransparencyDo you know what it is: weights, training, behaviour, and legible terms?
ModerateThe report, the per-source data accounting and the training code are public and inspectable, which is more than most weight-only releases offer. The weights are not publicly inspectable (manual gate, closed beta) and the training code has no licence file, so transparency stays at moderate until the weights and licence are released.
Sources
The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.