Model-Safety

TL;DR for operators A model-risk team estimating failures too rare for ordinary sampling has to decide which kind of error it can least afford. The benchmark shows that this choice can reverse which estimator looks best. :contentReference[oaicite:0]{index=0} Under approximately symmetric penalties, GA-AMLS has much lower average SPB loss than QLD for the 1-layer and 4-layer models. When the loss instead makes underestimation much more costly, QLD sharply outperforms GA-AMLS—even though QLD systematically overestimates and GA-AMLS has lower bias. ...

TL;DR for operators A team that has trained separate mathematics, coding, instruction, multilingual, and safety adapters still has one deployment decision left: which saved checkpoint from each expert should enter the merged model. The checkpoint with the lowest held-out validation loss is the expert’s individual stopping point, called $T^\ast$, but that does not guarantee it will cooperate best with the other experts. ...

TL;DR for operators Most model-governance systems still treat LLM failure like a customer-support ticket: hallucination, bias, unsafe compliance, sycophancy, escalation, add a dashboard, summon a committee, repeat until morale improves. NeuroCogMap proposes a more useful question: when the model fails, which internal systems were recruited, under-recruited, or misrouted? The paper builds a functional atlas of LLM internals by clustering sparse autoencoder features into parcels, attaching cognitive descriptions to those parcels, mapping them to capabilities, and arranging those capabilities into a four-level hierarchy: perception, representation, abstraction, and application.1 ...

Audit. That is the word companies use when they want something to sound objective, disciplined, and preferably immune to politics. A model produces an answer. Another model evaluates it. The evaluator gives a verdict. Everyone gets a dashboard. The dashboard gets shown to management. Management nods, because dashboards have a calming effect on adults in conference rooms. ...

Duplicates are supposed to be boring. In data engineering, duplicate records are usually treated as a hygiene problem: remove them, clean the pipeline, reduce noise, move on. In language-model training, repetition is less innocent. Repeated text can help a model learn an underrepresented domain. It can also teach the model to reproduce specific sequences too well. Somewhere between “useful exposure” and “verbatim recall,” a model stops learning only the pattern and starts carrying around the document. ...

TL;DR for operators GRAINS is not “fine-tuning, but cheaper.” That framing misses the point and commits the usual business sin of turning a mechanism into a procurement slogan. The paper’s useful claim is more specific: token-level attribution can be converted into an inference-time steering signal. Instead of retraining model weights, GrAInS identifies which text or image tokens most strongly push the model toward preferred or dispreferred outputs, builds layer-wise steering vectors from those activation shifts, and applies normalized edits during inference.1 ...