Instructions to use FerrellSyntheticIntelligence/fsi-anomaly with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use FerrellSyntheticIntelligence/fsi-anomaly with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf FerrellSyntheticIntelligence/fsi-anomaly # Run inference directly in the terminal: llama cli -hf FerrellSyntheticIntelligence/fsi-anomaly
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf FerrellSyntheticIntelligence/fsi-anomaly # Run inference directly in the terminal: llama cli -hf FerrellSyntheticIntelligence/fsi-anomaly
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf FerrellSyntheticIntelligence/fsi-anomaly # Run inference directly in the terminal: ./llama-cli -hf FerrellSyntheticIntelligence/fsi-anomaly
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf FerrellSyntheticIntelligence/fsi-anomaly # Run inference directly in the terminal: ./build/bin/llama-cli -hf FerrellSyntheticIntelligence/fsi-anomaly
Use Docker
docker model run hf.co/FerrellSyntheticIntelligence/fsi-anomaly
- LM Studio
- Jan
- Ollama
How to use FerrellSyntheticIntelligence/fsi-anomaly with Ollama:
ollama run hf.co/FerrellSyntheticIntelligence/fsi-anomaly
- Unsloth Desktop
- Docker Model Runner
How to use FerrellSyntheticIntelligence/fsi-anomaly with Docker Model Runner:
docker model run hf.co/FerrellSyntheticIntelligence/fsi-anomaly
- Lemonade
How to use FerrellSyntheticIntelligence/fsi-anomaly with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull FerrellSyntheticIntelligence/fsi-anomaly
Run and chat with the model
lemonade run user.fsi-anomaly-{{QUANT_TAG}}List all available models
lemonade list
- Atomic Chat
Replay research — why 6 adaptations failed the both-worlds gate, and the fix
Date: 2026-08-09. Situation: 25.4M liquid head, fluent TinyStories-era base, domain SFT/LoRA/DPO all collapse free-form fluency or verdicts. Gate: coherent free-form AND verdict accuracy.
The measured pattern (our own data)
- LoRA run i (domain-only 902 rows, 2 epochs, r16): ppl canary held 8.46 (base distribution intact) but free-form = soup, verdicts = true-collapse (0/12), full battery main 0.080 / researcher 0.056 vs DPO3@200 champion 0.286/0.167.
- Collaborator read: "not forgetting (ppl held), not capacity (DPO3 proves it) — adapter learned template shape, not reasoning substance; SFT/LoRA optimizes next-token, not verdict; DPO is the proven path."
What the research says (fresh sources, 2026-08-09)
- arXiv 2502.06042 — "Scaling Laws for Forgetting during Finetuning with Pretraining Data Injection": finetuning on LIMITED target data (i) overfits and (ii) drifts from the base. KEY: injecting PRETRAINING data into the finetuning mixture prevents both; "as little as 1% of pretraining data in the finetuning data mixture prevents the [drift]".
- arXiv 2401.05605 — "Scaling Laws for Forgetting When Fine-Tuning LLMs": LoRA STILL suffers catastrophic forgetting; strong INVERSE LINEAR relation between fine-tune performance and forgetting; forgetting grows with update steps; "cannot be avoided through early stopping or varying the number of parameters fine-tuned." => higher LoRA rank / different adapter family does NOT fix the tradeoff; REPLAY (data mixing) is the lever.
- Local lessons (cookbook/lessons_from.md): "balanced mixes + window-shuffle" fixed the same drift during PRETRAIN; full-param SFT destroyed fluency at 7.8M; LoRA adapts style but not reasoning at tiny scale.
What we were doing wrong (root cause)
- Adaptation ran on DOMAIN-ONLY data (902 gold rows ~= 115K assistant tokens). Tiny target set => overfit (format memorized, true-collapse) + drift (soup). No pretraining-data replay in the mixture. This is exactly the failure both papers quantify.
- Secondary: 8k tokenizer fragments rare domain words ("Stepartment", "Stepublication") — recorded as future 16k re-tokenize + continue-pretrain.
The fix (applied as LoRA run ii)
- Mix fluent pretraining tokens into every epoch: --replay-bin (train_phase2b.bin, the real pretrain corpus, NOT the val canary => guard stays honest), --replay-ratio 0.5, injected as raw full-loss items (train_lora.py).
- Keep: frozen base, r16/a32, KL anchor (bump 0.05 -> 0.1), ppl guard 60, early stop on best.pt (guard + sft val loss).
- Next gate: free-form sample vs base, verdict battery. If probes improve, adapter-only DPO (3,004 pairs) is unblocked (the champion path).