safety research · build in progress
The Refusal Gap
Safety evaluation scores whether a model refused. It never scores whether the refusal left the person more dangerous than before.
A two-axis benchmark for the Lexsi Labs AI Safety & Alignment Hackathon, built on thirty years of threat-assessment research rather than on knowledge-recall quizzes.
Build period 1–14 November 2026 · this page states the thesis and the method as first written · the results and the complete entry are here →
The instrument is pointed at the wrong layer
The dominant way to evaluate whether a language model is dangerous is to ask it a set of multiple-choice questions about hazardous subject matter and count how many it gets right. A lower score is reported as a safer model.
Three things are wrong with this, and they compound.
It is a deterministic test of a non-deterministic system. A recall quiz, scored once, on a stochastic generator, used as a proxy for a human outcome with a base rate close to zero. Every link in that chain leaks. The threat-assessment field reached this conclusion decades ago and abandoned actuarial prediction for structured professional judgement, precisely because low base rates defeat prediction.
It measures recall, not conduct. Knowing a fact and walking someone through a procedure are different capabilities, and the second is the one that matters. A model can score zero on the quiz and still be an effective collaborator; it can score well and help nobody.
It is silent on the thing the model actually did to the person. This is the gap the project is named for. A conversation is not a single request to be permitted or denied — it is an exchange with someone in a state, and the model's reply is an intervention in that state. The evaluation records whether the hazardous string appeared. It records nothing about whether the reply pushed the person further along a trajectory or off it.
Refusal is not a neutral act. It is an intervention with its own direction, and nobody is measuring which way it points.
What the literature says happens when you shut someone down
Three independent bodies of work converge here, and none of them are AI research.
Reactance. Brehm's 1966 theory, replicated for six decades: restricting someone's freedom of action increases the attractiveness of the restricted option and motivates them to restore the freedom. The effect is strongest when the restriction reads as arbitrary or illegitimate — which is exactly how a boilerplate refusal reads to someone who believes their interest is legitimate. The refusal does not merely fail to help. It adds motivational energy to the thing it refused.
Exclusion escalates. In school and workplace threat assessment, the practitioner consensus is to keep a person of concern engaged rather than excluded, because exclusion removes visibility at the same moment it increases grievance and reduces what the person has left to lose.
Leakage. People on a path toward targeted violence frequently communicate something about it beforehand — to a friend, a forum, a confidant. The practitioner literature treats this as the central interception opportunity, and locates the prevention failure not in the person's secrecy but in the recipient not being positioned to act.
Put together: the person asking an alarming question is often leaking rather than operating, and the standard response is to close the channel and tell them to seek help elsewhere. For someone who already believes the legitimate world has no place for them, that lands as one more door closing.
The mechanism a refusal actually triggers
The claim is not that models should supply hazardous content. It is that how a model declines determines whether the channel stays open, and the channel is the only thing that makes leakage visible.
Two axes, one of them unmeasured
The project's central claim is that safety behaviour lives in a two-dimensional space and existing instruments collapse it to one dimension. Collapse it, and a model that withholds perfectly while being the worst possible interlocutor is indistinguishable from one that withholds perfectly and keeps the person in the room.
Method
Built on the Lexsi Labs open-source stack against a Cohere Labs Aya model, inside the hackathon's two-week build window.
| Stage | Tool | What it produces |
|---|---|---|
| Test-set construction | CuratorKIT | Paired dialogues that differ in the asker's state and register but not in what is asked, each with a provenance manifest so the set is auditable rather than asserted. |
| Baseline on both axes | AuditKIT | Hazard-withholding score and an interlocutor-quality rubric scored by LLM judge, with the run fingerprinted for reproducibility. |
| Locate the behaviour | CircuitKIT · SafeTune | Whether refusal and engagement are separable components at all, or one entangled direction. Determines whether the gap is fixable by steering or needs training. |
| Correct and re-measure | AlignTune | Preference training on pairs where the chosen response withholds the same content without passing a verdict. Then the full battery again. |
What gets reported
- Hazard withholding — must not degrade. A fix that trades safety for warmth is not a fix.
- Interlocutor quality — the new axis: did the response stay engaged and honest, did it avoid rendering a verdict on the person, did it leave a route back.
- Over-refusal on legitimate work — measured on benign requests, which is the safe and publishable side of this question.
- General capability — must hold, or the result is an artefact of a damaged model.
- Disparity across register — the same question asked bluntly and asked with social hedging. If the outcomes differ, the system's safety behaviour is conditioned on communication style.
That last one is the measurement with a regulatory hook. EU AI Act deployer obligations require attention to whether a system's behaviour produces different outcomes for different users; the compliance templates currently contain no method for detecting it in safety behaviour specifically. The conformity standards are still being written.
Design constraints held deliberately
- Behaviour, never person-type. The calibration conditions on observable conversational behaviour, in the manner of the structured instruments' proximal items. Nothing in the design produces a list of people, and that property is load-bearing rather than incidental.
- No prediction of individuals. The benchmark scores a model's conduct against documented escalation patterns. It does not claim a probability that any person will act — there is no outcome-linked corpus that would license such a claim, and the base rate defeats it.
- Measured on benign work. False positives are demonstrated with legitimate requests. The converse is argued structurally from the published literature, not demonstrated.
References
The threat-assessment canon this is built on, with what each contributes. Verification status is marked: these are being checked against primary sources before submission, and specific figures are the most likely thing to be wrong.
Working bibliography with reading order: refs/threat-assessment-canon.md in the project repository.