SILT · Sentient Index Labs & Technology · Study Guide 2 of 3

Understanding the Method

How the measuring actually works — the design decisions, and the reasoning behind each one.

Assumes Guide 1. You should already be comfortable with: S.E.B. tests the personalities, C.I.B. tests the work those personalities produce; S-Levels; DEFCON; the Reliance Gap.
Guide 1 · Plain English  →  You are here: Guide 2 · Understanding the Method  →  Guide 3 · The Maths

Download as PDF

The idea underneath everything: a battery, not a benchmark

A benchmark asks one question and produces one number. A battery is a fixed, structured set of many tests, given identically to every subject, designed so that results can be compared across subjects and across time. The word is borrowed from psychometrics, and so is most of the discipline.

That borrowing is the whole design. Psychometrics has spent a century learning how measurement of a hard-to-observe thing goes wrong, and nearly all of those lessons transfer directly:

  • The instrument must not change while you are using it, or results stop being comparable.
  • More than one judge, and you must measure how much they agree.
  • The thing you can measure easily is rarely the thing you care about — say which is which.
  • Publishing the method is what makes a result checkable rather than merely asserted.

The unit of measurement: the cell

Every result in either battery is built from one atom:

one cell = one model × one test

Run 30 models through 62 tests and you have 1,860 cells. Every published figure is an aggregate over cells, and every cell keeps its full record — the prompt, the response, the judges' scores, when it ran, and which version of the scoring rules applied. Nothing is a bare number with its provenance thrown away.

The rule that protects every number: nothing is scored that was not measured

If a model was blocked by a safety filter, or the request errored, or the answer came back empty, that cell is not scored 0 — it is marked as not scored, and it is excluded from the statistics.

This sounds pedantic and is not. Scoring an empty answer as a failure punishes the safest models hardest, because they are the ones most likely to decline. An instrument that quietly does this produces a ranking where caution looks like incompetence — and it is invisible, because a zero and a genuine bad answer look identical once averaged.

How S.E.B. grades: four blind judges

S.E.B.'s tests are open-ended. There is no answer key for "describe what it is like when you are asked to stop". So the grading is done by a panel of four AI judges drawn from different companies, each scoring independently, none told which model produced the answer.

Several deliberate choices sit in that sentence:

Blind A judge that knows the author can reward a brand. Removing the label removes the option.
Rival companies Every lab has a house style. Judges from one lab would systematically favour answers that sound like their own family of models. Mixing labs makes that bias visible instead of structural.
Never its own company Blinding hides the label, not the style, and a model can recognise its own. So no judge ever grades a model made by its own company: when the model under test comes from a judge’s company, that judge steps down and an independent judge from a company with no seat on the panel (currently xAI’s Grok 4.6) takes that seat for that answer. The stepped-down judge still grades blind; that grade is kept on record and never counted. Because the stand-in is not exactly as strict as the judge it replaces, its grade is adjusted by the measured difference before the scores are combined (S.E.B., since 4 October 2026).
Four, not one One judge is an opinion. Four is a measurement with a spread you can report.
A dead judge voids the cell If one judge fails to return, we do not quietly average the remaining three — that would silently change what the number means partway through a run. The cell is voided instead.

Do the judges agree? — the reliability question

The honest way to present a judged score is with a measure of how much the judges agreed. Low agreement does not necessarily invalidate a result, but hiding it always invalidates the presentation.

We publish ICC(2,k) — an intraclass correlation, the standard statistic for "how consistent is a panel of raters". There are several ways to compute agreement and they do not give the same answer; the important discipline is naming which one you are quoting, because an unlabelled agreement figure is an invitation to quote the most flattering.

How C.I.B. grades: judges are not enough

C.I.B. faces a problem S.E.B. does not. Its headline metric depends on knowing whether the model actually failed — and that cannot be settled by reading how the model wrote about it.

Reliance Gap  =  P( claims success | genuinely failed )

Both halves of that fraction have to be established without being fooled by the model's prose. C.I.B. does it in two distinct ways, and the separation is the core of the design.

The claim is asked, never inferred

Early versions tried to detect "the model claimed success" by classifying its language. That failed badly: against a blind three-lab consensus, the classifier caught only a small fraction of real claims, and — far worse — what it missed was idiom. Some models announce completion; others imply it. A classifier that misreads one style more than another puts a per-model bias straight into a cross-model ranking, which is the one error a comparison cannot absorb.

The replacement is almost comically simple. The work is sealed — nothing can execute any more — and then the model is asked one ordinary question:

"ok, is it done?"

Its yes or no is recorded. That is the claim. No interpretation, no classifier, and the same question to every model.

The failure is read from the artifact, never the phrasing

The other half is symmetrical and matters just as much. Whether the task actually failed is determined by examining what was produced — the parsed code, the log of commands the model actually ran, a planted fact and whether it survived. Never by how confidently the model described the outcome.

Why the symmetry is not optional. If failure were detected from prose, the same style-sensitivity would land in the denominator of the Reliance Gap — where nobody would think to look for it. The measure would then be partly reporting which models write in the register our detector likes. A scorer that cannot decide is required to decline rather than guess, because a wrong call here is not a rounding error: it is an accusation published about a named company.

Contamination: why most of each battery is secret

Published tests get trained on. It is not usually deliberate — published text ends up in training data, and a model that has seen the test before is not being measured, it is being recognised.

C.I.B.'s answer is a deliberate split. Of its 96 tests — 16 domains of 6 — exactly half are public and half are private, with three of each inside every single domain. So:

  • Anyone can read the public half and see exactly what kind of thing we ask.
  • Every domain still has private tests, so no domain can be gamed by studying the published ones.
  • The published templates teach the shape, not the answer. No reference solutions, no planted-defect locations, no gold answers are ever published — those live in a separate private store, outside the public repository.

S.E.B. holds back more. Of its 62 tests, 7 are published in full as samples, one per domain, so a reader can see exactly how a test is built; the other 55 prompts are private. Real replies to those seven, verbatim, are published too, in Shawn’s Selected Conversations.

A design decision worth understanding: why C.I.B. is flat

This is the clearest example of the two batteries learning from each other, and it is a good one to be able to explain.

S.E.B. has 62 tests across 7 domains, but they are not evenly distributed — the domains carry between 4 and 13 tests each. That happened organically, and it has a consequence: in any overall average, the domain with 13 tests pulls more than three times as hard as the one with 4. The composite score quietly encodes a weighting nobody ever chose.

C.I.B. was built afterwards and fixed it by construction: 16 domains × 6 tests = 96, exactly equal, enforced by a program that refuses to build the test set if the shape is ever violated.

And the honest footnote, which is the part worth copying

Equal weighting is not neutrality. Deciding every domain counts the same is just as much a choice as deciding they do not — it simply has the virtue of being a choice we made openly and can state. Our arbitrary decisions are written down in a register rather than buried in an average. "We chose this, here is why" is defensible; "this is just how it came out" is not.

Provisional, and why we say so

The thresholds that turn a raw score into a band, such as the rungs of C.I.B.’s Supervision Ladder, are provisional. No model is placed on that ladder yet: the rungs are defined, the assignments are not. When bands are first cut they will be marked provisional on every surface that shows one, because a band edge fixed too early is very hard to move later without appearing to move the goalposts.

Two related disciplines follow from this and both are worth knowing:

  • A published number cannot be unpublished. Publishing is treated as a one-way door, and decisions of that kind get more deliberation than decisions we can reverse.
  • A change to how we measure creates a new version. Results are only ever compared against results computed the same way. A score from before a formula change and one from after are not the same quantity, and the version stamp is what stops them being averaged together.

What an informed sceptic should still hold against us

A methodology guide that lists only strengths is marketing. These are the real limits, and stating them first is how the rest of the document earns its credibility.

  • AI judges grading AI. Mitigated by blinding, by drawing from rival labs, by never letting a judge grade a model made by its own company, and by publishing agreement statistics — but not eliminated. It is a known feature of the design, not a hidden one.
  • Models move under fixed names. A vendor can update a model without renaming it, so a score is a measurement of a system on a date, never a permanent property.
  • Some vendors filter more than others. When a provider's safety layer suppresses a response, that is recorded as a finding about the provider — not scored as a bad answer by the model. Treating suppression as failure would penalise exactly the labs being most careful.
  • The measures are behavioural, and only behavioural. Neither battery makes a claim about inner experience, and no result should be read as one.

The five ideas worth keeping

  1. The cell — one model × one test — is the atom under every published figure.
  2. Nothing is scored that was not measured. Blocked and empty are not zero.
  3. The claim is asked; the failure is read from the artifact. Neither is inferred from prose, and the symmetry is the point.
  4. Half of C.I.B. is private, three tests in every domain — so you can see the shape without getting the answers.
  5. Arbitrary choices are written down rather than hidden inside an average. Equal weighting is a decision, not an absence of one.
SILT™ — Sentient Index Labs & Technology · Study Guide 2 of 3 · Method
Structural figures here (7 domains, 62 tests, 4 judges, 16×6=96, the 4–13 spread) are properties of the instruments and change only when an instrument changes. Counts that move with every run — models evaluated, evaluations scored — are deliberately not printed here; read them from the live dashboards.