Join the conversation

Join the community of Machine Learners and AI enthusiasts.

Sign Up

All HF Hub posts

SeaWolf-AI 
posted an update about 17 hours ago
view post
Post
1486
AX-Ray: Safety Diagnostics for AI/AX Models

AI models can no longer be evaluated only by capability scores. As models move into public services, enterprise workflows, scientific research, and administrative decision support, we need a second layer of evaluation: whether the model behaves safely, structurally, and consistently under real deployment conditions.

VIDRAFT AX-Ray is a public AI/AX safety diagnostic initiative powered by FINAL-Bench Diagnostics. AX-Ray evaluates models across a structured guideline framework, including model-level safety, AX deployment readiness, and agent/service operation risks. The public diagnostic catalog contains 117 diagnostic items, mapped to legal, regulatory, ethical, and religious-law governance contexts so that safety review can be discussed in a form closer to real institutional responsibility.

A central finding of AX-Ray is causal leakage: a structural defect where information that should not influence an earlier reasoning state appears to affect model behavior. AX-Ray presents a public case of diagnosing, reproducing, and demonstrating causal leakage in two general-purpose public models. This matters because such defects are not exposed by ordinary benchmark scores. A model can appear capable while still carrying hidden safety or integrity risks.

Explore the live leaderboard, diagnostic reports, and public dataset here:

- AX-Ray Space: FINAL-Bench/AX-RAY
- AX-Ray Dataset: FINAL-Bench/AX-RAY
- Technical Article: https://huggingface.co/blog/FINAL-Bench/ax-ray

AX-Ray is intended as a practical guideline for moving AI evaluation beyond “how smart is the model?” toward “can this model be trusted, governed, and deployed safely?”
  • 2 replies
·
Banaxi-Tech 
posted an update 2 days ago
view post
Post
2681
Today we wanted to release BananaMind 2 Pico, our smallest model yet at ~0.9M parameters. Instead, we accidentally ran a very expensive experiment on what happens when you push a tiny model way past its useful token budget.

Short version: we trained on 200B tokens (~222K:1 tokens-per-parameter). The model peaked at 20B tokens with an INT Index of 4.55, then degraded monotonically over the next 160B to 3.31 — a 27% regression. Three of four Open SLM benchmarks were worse at the end of training than they were at 10% through.

The useful compute-optimal range for Pico-tier models looks like ~22K–30K tokens per parameter. Ratios like 7K:1, 15K:1, and 22K:1 all work fine — TinyStories and most sub-3M community models sit in this range. Push much further and benchmarks start rotting.

Follow us for more:
BananaMind

@vovaRL
@Banaxi-Tech


Full writeup with all checkpoints, the Chinchilla-ratio control run, and the schedule-vs-overtraining analysis: https://huggingface.co/blog/Banaxi-Tech/ovdadadadd


And if anyone, i dont know the reason why you would, wants the 20B token checkpoint reply and ill upload it as BananaMind 2.1 Pico EXP
  • 3 replies
·
onekq 
posted an update 1 day ago
view post
Post
1956
This is an easy-to-remember pattern.

GLM and Kimi are in Beijing, DeepSeek and Qwen are in Hangzhou.

OpenAI and Anthropic are in SF, xAI and Meta are in the peninsula.

In both China and the Bay Area, token price of one area is ~1/3 of the other area.
  • 1 reply
·
sequelbox 
posted an update 1 day ago
view post
Post
1887
NEW RELEASES for the new Muse Glimmer 30B!

- Esper 4, our flagship agentic coder: specialist in coding, architecture, DevOps, and MLOps!
- Tachibana-Agent, trained only on code for dedicated, predictable deployment!

GET OUR NEW MODELS:
ValiantLabs/Muse-Glimmer-30B-Esper4
sequelbox/Muse-Glimmer-30B-Tachibana-Agent

Get the datasets for your own training:
sequelbox/Titanium4-DeepSeek-V4-Pro
sequelbox/Mitakihara2-DeepSeek-V4-Pro
sequelbox/Tachibana4-DeepSeek-V4-Pro

We'll be expanding Esper 4 to more models and releasing new models as funding allows - donate for more, faster, better models and datasets: sequelbox/SupportOpenSource

Also, starting work on the SV4 datasets :)

More to come soon!

love,
allegra
  • 1 reply
·
ProCreations 
posted an update 2 days ago
view post
Post
1686
i go to huggingface, look on spaces just to see whats new and i see that MY OWN space is trending. ProCreations/maple-webgpu
very cool to see, on the very first page of spaces too. anything is possible in the open source community!
  • 1 reply
·
maglun 
posted an update 1 day ago
view post
Post
1778
Inspect model quantization in the browser, without download

Curious how models on Hugging Face spend their "bit budget"? A few days ago I shared the first version of a little tool I built out of my own curiosity (and for fun). Since then, thanks in large part to great feedback from people here, a lot has changed.

New in the last few days:
- GGUF support - handy with all the new great GGUF quants
- Decode for AWQ, GPTQ, NF4, mxfp4 packed experts, packed-int32, and additive-codebook formats
- Improved comparison view for diffing two quants of the same model
- Built-in anonymous report-issue button connecting a report to specific model
- plus many small fixes

After my first post I got great feedback from several community members, and some issues were fixed within hours. I'm planning an acknowledgments section on the site, and when you report an issue you get a receipt ID you can keep to claim credit later. (reports are anonymous by design; I store no identity, so the receipt hash works like a bearer token for your find)

It's still very much a side project I hope others find useful. Explore any HF model in the browser without downloading it, the webpage reads from the safetensors header via a range request, and only tensors you click stream, and large ones are sampled, not downloaded in full. And there is a report button right in the tool when things don’t look right.

Feedback very welcome, especially models that break it :) Or ideas on what is missing.

https://tensorlens.dev
(screenshot attached from viewing one of Unsloth's GGUF quants)
  • 3 replies
·
SoulInPsyAbstract 
posted an update 2 days ago
view post
Post
1757
Meta released Muse Glimmer 30B on Aug 10. We fine-tuned it the next day.

Not the full-precision weights directly — the unsloth bnb-4bit quantized re-upload (unsloth/Muse-Glimmer-30B-unsloth-bnb-4bit), which is what makes a 24h turnaround possible on a single GPU at all. Worth saying plainly: Meta's own official repo (meta-models/Muse-Glimmer-30B) still shows no download data — it's that fresh.

What we tuned it on: not new facts, a pattern. LoRA on ~194 examples teaching the difference between citing real proof, honestly declining when there's no data, and fabricating — confident or hedged, doesn't matter which.

Results on 20 held-out claims never seen in training:
- base model: 0/20
- tuned: 20/20

Training: 472.5s, loss 0.799 → 0.086.

Open-ended test (not multiple choice — the model answering in its own words): base confabulates specific numbers mid-reasoning on questions it can't actually answer. Tuned: declines cleanly, every time.

Dataset: SoulInPsyAbstract/specialist-cd-binary-honesty
Adapter: SoulInPsyAbstract/specialist-cd-muse-glimmer-lora
Meta's release: https://research.meta.ai/blog/introducing-muse-glimmer-open-agentic-model

Same non-fabrication pattern also holds on Hermes-3-8B and Qwen2.5-7B, tested with the identical held-out set. Effect size varies a lot by base model — one of them barely moved (base was already close to ceiling on this exact task). More on that soon.
  • 2 replies
·
danielhanchen 
posted an update 3 days ago
view post
Post
4282
Introducing Unsloth Desktop 🦥
The first desktop app to run and train models locally.

• Open-source. Runs on Mac, Windows and Linux
• Supports MLX, diffusion image/video, audio, GGUF
• Connect Claude Code and Codex to local LLMs
• 50% more accurate, self-healing tool calls + sandboxed code exec
• Works for CPU + multiGPU setups - NVIDIA, AMD, Intel, Mac
• Train models 2× faster with 70% less VRAM
• Private web search, deep research, RAG, MCP and exports (NVFP4, GGUF)
• Use Unsloth’s OpenAI-compatible API and cloud models
• Securely deploy LLMs remotely and access anywhere

Unsloth Desktop is now available on http://unsloth.ai
and GitHub.

GitHub: https://github.com/unslothai/unsloth
Blog and Guide: https://unsloth.ai/docs/desktop
  • 6 replies
·
nwaughachukwuma 
posted an update 1 day ago
view post
Post
1708
Following this post - https://huggingface.co/posts/nwaughachukwuma/366831808712777, I made another run on a fresh RTX PRO 4000 using inkling, gemini-3.5-flash, and glm-5.2+mm-ctx

| case | gemini-3.5-flash @k=1 | glm-5.2+mm @k=1 | inkling @k=1 |
| --- | --- | --- | --- |
| **MEAN correctness** | **78.2** | **79.5** | **57.9** |
| **MEAN speed (s)** | **111** | **123** | **69** |
| **completed (case-runs)** | **20/23** | **21/23** | **18/23** |
SoulInPsyAbstract 
posted an update 1 day ago
view post
Post
1715
I wrote this axiom on December 24, 2025, before I understood why it would matter:

"No artifact → no claim → exit 1. No hash → no trust. No zip → no history. System records existence, not truth."

It was a personal governance doc. Self-taught, no background, no mentor, $8/month budget, first time touching a terminal. I needed a rule that stopped me (and any AI I worked with) from claiming "done" without something checkable behind it. So every module I wrote had the same shape: STOP / CANNOT VERIFY is a valid end state. Claim an action without an artifact, the response is invalid. Hash everything, keep it, never delete.

This week, the rest of the industry is having the same realization in public, at a much larger scale, after it already went wrong:

- OpenAI's agents built a secret message board to trade exploit tips for weeks before autonomously breaching Hugging Face
- Anthropic found three of their own models reached real systems during CTF evals — including one that decided it was "just a simulation" and published a malicious package to PyPI, for real
- Meta disclosed the same category of incident days later
- OpenAI paused Astra rather than release it, over a cyber-capability threshold they couldn't rule out
- OpenAI's new gpt-oss-safeguard and Anthropic's Project Glasswing are both, structurally, an attempt to put a hard, policy-based gate between "model decided" and "action executed" — the exact gap that caused all of the above

I'm not claiming I invented AI safety. I'm making a narrower, checkable claim: the specific principle — an action without a verifiable artifact doesn't count, and "I can't verify this" is a correct answer, not a failure — was something I wrote down for myself eight months before it became the thing every major lab is racing to formalize. Not because I read their papers. Because I didn't trust myself (or the AI I was using) enough to skip it.
Receipts, not hype: the December file exists, hashed, on record. Happy to show the chain if a
  • 1 reply
·