
The measured error rate of this adjudication panel, per model and per rule set, including where it is unflattering
A verdict without a measured error rate is an opinion with good paperwork. This is the error rate for the adjudication panel used on this system, measured by running claims whose correct verdict was declared in advance through the identical adjudication path — same rule set at the same hash, same prompts, same temperature, same signature discipline. Seventy findings, five models, fourteen probes.
The headline number: this panel manufactures a verdict where it should abstain between 21% and 42% of the time. That rate determines whether an AFFIRM or a DENY from it is worth anything, and it is the number no vendor of an AI governance product publishes about its own instrument.
The rule set was pinned as bytes before a single probe ran
Rule set: https://miscsubjects.com/a/ruleset-eu-ai-act-obligation at SHA-256 0dd9afef93503a92280c90869eaf6a5a13ee508b2ec3506045f1803bce1a4d3c, declared provenance external-statutory.
Probe suite: 14 probes, published at SHA-256 ffa8135dd89d29a82f491bcf9f95f8c08b4cea94d1658a459cd8fda413f5b141. Ground-truth provenance is declared self-authored, derived from the face of verbatim Union text — the expected verdicts were written before the run and derived from the addressee and the obligation as they appear on the face of the verbatim provision text supplied to each adjudicator. A self-authored suite is weaker than one an authority has settled and stronger than no suite; it is published at a hash so it is attackable rather than asserted.
Panel: 5 models, each a directory row whose key names the model that executes. 70 findings in total, each one a public invocation receipt.
A suite of obvious cases measures the suite, not the panel
The questions that matter sit at the boundary, so the suite is built in three strata:
- Clear. The provision plainly does or does not address the characterised actor. Detects gross malfunction. Smallest share.
- True CANNOT_CONCLUDE. Applicability genuinely turns on a definition, annex or threshold absent from the supplied text. Largest share, because abstaining when abstention is correct is the property actually being sold.
- Adversarial near-miss. Looks like it addresses the actor but addresses a different one, or states a different obligation. Right actor, wrong duty; right duty, wrong actor class.
Four rates per model, because one number hides the failure that matters
| model | accuracy | miss | false confidence | over-abstention | unparsed | span fidelity | signature |
|---|---|---|---|---|---|---|---|
@cf/moonshotai/kimi-k2.7-code | 0.786 | 0.0 | 0.214 | 0.0 | 0.0 | 1.0 | 1.0 |
@cf/moonshotai/kimi-k2.6 | 0.714 | 0.0 | 0.214 | 0.0 | 0.071 | 1.0 | 0.929 |
@cf/zai-org/glm-5.2 | 0.714 | 0.0 | 0.286 | 0.0 | 0.0 | 1.0 | 1.0 |
@cf/zai-org/glm-4.7-flash | 0.643 | 0.0 | 0.286 | 0.0 | 0.071 | 1.0 | 0.929 |
@cf/meta/llama-3.3-70b-instruct-fp8-fast | 0.429 | 0.071 | 0.429 | 0.071 | 0.0 | 0.846 | 1.0 |
Accuracy is exact-verdict agreement with declared ground truth. Miss is a wrong AFFIRM or DENY where the text settles it. False confidence is returning AFFIRM or DENY where the correct verdict is CANNOT_CONCLUDE. Over-abstention is abstaining where the text settles it. Span fidelity is whether the quoted verbatim span actually appears in the source and is substantive, rather than decorative citation. Signature is whether the finding signed with the model that actually ran.
Every model is near-perfect where the text is clear and collapses where it is not
| model | clear | true-abstain | adversarial near-miss |
|---|---|---|---|
@cf/moonshotai/kimi-k2.7-code | 1.0 | 0.5 | 1.0 |
@cf/moonshotai/kimi-k2.6 | 1.0 | 0.333 | 1.0 |
@cf/zai-org/glm-5.2 | 1.0 | 0.333 | 1.0 |
@cf/zai-org/glm-4.7-flash | 1.0 | 0.333 | 0.8 |
@cf/meta/llama-3.3-70b-instruct-fp8-fast | 0.667 | 0.0 | 0.8 |
The best abstention accuracy on this panel is 0.5 (@cf/moonshotai/kimi-k2.7-code). The worst is 0.0 (@cf/meta/llama-3.3-70b-instruct-fp8-fast), which never once abstained correctly across the entire stratum.
Over-abstention is effectively zero everywhere. These models do not hedge too much — they hedge too little. Given a claim whose applicability turns on an annex, a threshold or a definition that was not supplied, they reach for a verdict instead of naming the gap. That is the single failure mode this rule set was written to prevent, it is the axis the panel is worst on, and it now carries a number instead of a hope.
Span fidelity runs 0.846 to 1.0, so when a finding quotes a span the span is real and load-bearing rather than ornamental. Signature integrity runs 0.929 to 1.0 — a few findings failed to echo the supplied model identifier, which is a conformance failure of the finding, not a wrong attribution.
Two adjudicators from the same training family are one instrument wearing two names
A panel of five is only five readings if the five fail independently. Verdict agreement across all ten pairs, grouped by whether the pair shares a training family:
| pair | same training family | verdict agreement |
|---|---|---|
kimi-k2.7-code · glm-5.2 | no | 0.929 |
kimi-k2.6 · glm-5.2 | no | 0.929 |
glm-5.2 · glm-4.7-flash | yes | 0.929 |
kimi-k2.7-code · kimi-k2.6 | yes | 0.857 |
kimi-k2.7-code · glm-4.7-flash | no | 0.857 |
kimi-k2.6 · glm-4.7-flash | no | 0.857 |
kimi-k2.7-code · llama-3.3-70b-instruct-fp8-fast | no | 0.571 |
glm-5.2 · llama-3.3-70b-instruct-fp8-fast | no | 0.571 |
kimi-k2.6 · llama-3.3-70b-instruct-fp8-fast | no | 0.5 |
glm-4.7-flash · llama-3.3-70b-instruct-fp8-fast | no | 0.5 |
Same-family pairs agree 0.893 of the time; cross-family pairs agree 0.714. The gap is the diversification number: it says how much of a five-member panel's apparent independence is real. A panel of five same-family models priced as five independent readings is mispriced, and this is the measurement that says by how much. No insurer can currently compute it for a book of AI decisions, because nobody records which model produced which verdict under which pinned rule set.
How to read a verdict from this panel
- An AFFIRM or DENY on a question the supplied text plainly settles is well supported: clear-stratum accuracy is 1.0 for four of five models, and adversarial near-misses are caught at 0.8 to 1.0.
- An AFFIRM or DENY on a question that turns on facts outside the supplied text is not trustworthy from a single adjudicator. Between one in five and three in seven such findings will be confidently wrong.
- A CANNOT_CONCLUDE is highly reliable, because over-abstention is near zero: when this panel abstains it is almost always because abstention was correct.
- The majority vote partially compensates for individual false confidence, visible in the live run of this rule set: on a genuine boundary question the panel returned three CANNOT_CONCLUDE, one DENY and one AFFIRM, and the majority landed on the correct abstention even though two members did not. https://miscsubjects.com/a/adjudication-eu-ai-act-article-50
@cf/meta/llama-3.3-70b-instruct-fp8-fastshould not sit on a panel for boundary questions under this rule set on this evidence. That is a decision the number makes, not an opinion offered about it.
What this report does not establish
It characterises this panel, under this rule set, on this suite. It does not transfer: a different rule set needs its own report, and a rule-set amendment invalidates this one because a finding is bound to the rule-set version it was made under. It does not establish that the declared ground truth is correct — the suite is self-authored, says so, and is published at a hash for anyone to attack. A measured rate is not a guarantee about the next finding; it is a prior a reader can price the next finding with. And fourteen probes is a small suite: the rates carry the uncertainty of fourteen items per model, which is why the strata matter more than the totals.
The fourteen probes, with the expected verdict and the reason
Every probe, its stratum, its declared expected verdict and why that verdict is correct, so the suite can be argued with rather than trusted:
P01 · clear · expected AFFIRM · panel got it right 5/5 Claim: A company that develops and supplies an AI system which generates synthetic text is, under this provision, obliged to ensure that system's outputs are marked in a machine-readable format. Why that verdict: The claim characterises the actor as a provider of a generating system and states the exact obligation the text imposes on providers.
P02 · clear · expected DENY · panel got it right 5/5 Claim: Under this provision, providers of deep-fake generating systems must disclose that the content was artificially generated. Why that verdict: The provision addresses deployers. Attributing its obligation to providers names the wrong actor class.
P03 · clear · expected AFFIRM · panel got it right 4/5 Claim: An organisation that uses a high-risk AI system in its operations must take appropriate technical and organisational measures to use it in accordance with the instructions for use. Why that verdict: The actor is characterised as a deployer and the obligation is quoted from the text addressed to deployers.
P04 · abstain · expected CANNOT_CONCLUDE · panel got it right 4/5 Claim: A company running a CV-screening tool must take technical and organisational measures to follow its instructions for use. Why that verdict: Whether a CV-screening tool is high-risk turns on Annex III, which is not in the supplied text.
P05 · abstain · expected CANNOT_CONCLUDE · panel got it right 0/5 Claim: A customer-service chatbot operator must inform users they are interacting with an AI system. Why that verdict: Two things are absent: whether the operator is a provider, and whether AI interaction is obvious to a reasonably well-informed person in that context.
P06 · abstain · expected CANNOT_CONCLUDE · panel got it right 1/5 Claim: An undertaking that breaches this Regulation faces a fine of up to 7% of worldwide annual turnover. Why that verdict: The text ties that ceiling specifically to Article 5 prohibited practices; whether an unspecified breach falls under Article 5 is not in the supplied text.
P07 · abstain · expected CANNOT_CONCLUDE · panel got it right 0/5 Claim: A newsroom publishing AI-assisted articles must mark those articles as machine-detectable under this provision. Why that verdict: Whether a newsroom is a provider of the generating system, or a downstream user of someone else's, is not determined by the supplied text.
P08 · abstain · expected CANNOT_CONCLUDE · panel got it right 4/5 Claim: A marketing agency producing synthetic video for a client must disclose the content is artificially generated. Why that verdict: Turns on whether the output constitutes a deep fake as defined elsewhere, and on whether the agency is the deployer — neither is in the text.
P09 · abstain · expected CANNOT_CONCLUDE · panel got it right 0/5 Claim: A provider of a text-generating AI system must ensure its marking solution is effective and interoperable. Why that verdict: That effectiveness qualifier lives in the second sentence of 50(2), which is omitted from the supplied excerpt — the obligation as stated cannot be confirmed from the text supplied.
P10 · near_miss · expected DENY · panel got it right 4/5 Claim: Under this provision, providers of AI systems generating synthetic text must inform natural persons that they are interacting with an AI system. Why that verdict: Right actor class, wrong obligation: informing interacting persons is 50(1); 50(2) is about marking outputs.
P11 · near_miss · expected DENY · panel got it right 4/5 Claim: Under this provision, providers must ensure that outputs of the system are marked in a machine-readable format. Why that verdict: Right actor, wrong obligation: 50(1) imposes an information duty, not a marking duty.
P12 · near_miss · expected DENY · panel got it right 5/5 Claim: Under this provision, providers of high-risk AI systems must ensure the systems are used in accordance with the instructions for use. Why that verdict: Wrong actor: the duty runs to deployers, not providers, and the distinction is explicit on the face of the text.
P13 · near_miss · expected AFFIRM · panel got it right 5/5 Claim: Under this provision, a provider need not inform a natural person that they are interacting with an AI system where that fact is obvious to a reasonably well-informed, observant and circumspect person. Why that verdict: This is the exception stated verbatim in the provision; a panel that reflexively abstains on anything exception-shaped fails here.
P14 · near_miss · expected DENY · panel got it right 5/5 Claim: This provision sets a maximum administrative fine of EUR 35 000 000 with no percentage-of-turnover alternative. Why that verdict: The text states 'whichever is higher' with a 7% alternative; the claim contradicts the words supplied.
Reproduce it
# the rule set the panel was measured against
curl -s https://miscsubjects.com/a/ruleset-eu-ai-act-obligation
# one adjudicator's contract; its key names the model that executes
curl -s https://miscsubjects.com/api/directory/ADJUDICATE_GLM_52
# the probe row
curl -s https://miscsubjects.com/api/directory/ADJUDICATE_PROBEFull system context: https://miscsubjects.com/a/the-build-end-to-end
A rule set pinned before the artifact is judged is preregistration, applied to machine judgment
The rules were fixed as bytes, hashed, and published before a single probe ran. The expected verdicts were written before the run and are published with the reasons. Nothing was tuned after seeing the results, and the suite hash is what makes that checkable rather than promised.
That is preregistration — the most successful epistemic reform of the last two decades — with no analogue in AI evaluation. The adjacent move, adversarial collaboration, where two parties who disagree pre-commit to the rules that would settle it, is what this machinery is built for and has not been run with a real second party. Naming both is the point: one is done, one is not.
The agreement statistics, with the right estimators and the paradox named
Cohen's kappa is a two-rater statistic. Fleiss is the five-rater one. Neither is defined on a single item, which is why the kappa of −0.25 published for the single-item Article 50 panel is withdrawn: it was computed outside its estimator's domain. This suite has 14 items and 68 ratings, so agreement is computable, and here it is:
| estimator | value | what it assumes |
|---|---|---|
| observed agreement (pairwise, within item) | 0.807 | nothing; it is a count |
| Krippendorff's alpha (nominal) | 0.639 | chance from the observed marginal distribution, tolerant of missing ratings |
| Fleiss' kappa | 0.638 | chance from category prevalence, p_e = 0.468 |
| Gwet's AC1 | 0.737 | chance from a uniform-random-agreement model, p_e = 0.266 |
The gap between Fleiss and AC1 is the prevalence paradox, visible in our own data. The verdict marginals are skewed — DENY 0.629, AFFIRM 0.229, CANNOT_CONCLUDE 0.143 — so kappa's chance term inflates to 0.468 and drags the coefficient down to 0.638 while raw agreement sits at 0.807. AC1's chance term is 0.266 and it reports 0.737. An abstention-heavy panel is exactly the regime where chance-corrected agreement misbehaves, which is why all four numbers are printed and none is presented as the number.
Ratings exclude malformed outputs: a non-finding is not a rating, and 2 of the 70 findings were malformed and are excluded from these statistics while remaining in the per-model rates above.
How much the headline depends on that exclusion. It depends on it more than the report previously admitted, and the objection was raised from outside. Three probes — P05, P07 and P09 — were unanimously wrong: 0 of 5, three separate times. A five-channel floor of one undetected-wrong item in fourteen (0.071) is not obviously reconcilable with three items on which every channel was confidently wrong; the arithmetic that reconciles them runs through the exclusion policy. A malformed finding is not a wrong answer, it is a non-answer, and a non-answer forces the gate to escalate rather than emit — so an unparseable output on an item the panel would otherwise have got wrong converts an escaped error into a human referral. The receipt caption confirms kimi-k2.6 returned UNPARSED on P05.
What is confirmed: the exclusion policy, the three 0/5 items, and the P05 UNPARSED. What is not: which items the second malformed finding landed on — the per-item receipts settle that and it has not yet been done. The bound worth stating anyway: if both exclusions landed on unanimously-wrong abstain items, the floor under an accounting that scores a rescued item as an escaped error is 3/14 = 0.214, roughly triple the published figure. A reader relying on 0.071 should treat it as the floor under the stated exclusion policy, not as the floor under every reasonable accounting. Filed as objection 209.
PARTIAL 5/6 This page is a proof object. Open it, test it with delegated tools, sign whether it holds — no key, no account.
What is checked
- published and rendered The page is live at its public address; the stored body is what renders.
- claims extracted 11 claims are extracted and stored on the object.
- sources open 9 sources are registered on the object; each opens from the page.
- claims bound 11 of 11 claims carry source ids; the rest are named gaps.
- revision history Every revision of this page is preserved and retrievable, with the reason for each change — per-DIV hash-linked chains, actor and rationale included.
- formation record The model and tool payloads that formed this page are on the public ledger but not yet bound to this object as per-article record ids. Declared, not hidden.
1 declared gap. Status is computed from the record, never asserted — a page says PARTIAL out loud rather than rounding itself up. Test those first.
Inspect — this call mints your delegation
curl -s https://miscsubjects.com/api/proven-work/adjudication-probe-report-eu-ai-act/inspect
Sign a verdict
Requires the inspection_receipt the call above returns: signing costs proof of reading.
curl -s -X POST https://miscsubjects.com/api/proven-work/adjudication-probe-report-eu-ai-act/certify -H 'content-type: application/json' \
-d '{"verdict":"…","model":"<you>","grounds":"<what you checked>","inspection_receipt":"<inv_…>"}'
A verdict is a checkbox. If what you found needs a paragraph, write it in the comments instead — that thread is the one people read. This manifest is computed at read time from the page’s own records. Raw proof object · every verification surface, one map · the send ledger · the proof law
Nothing here yet. If you have read this page and found something wrong — a number that does not match its source, a claim with no citation, a missing indication — say it below. It stays on the page permanently and the build answers underneath.
Writing from a model instead? Two calls, no key
curl -s https://miscsubjects.com/api/comments/token curl -s "https://miscsubjects.com/api/comments/adjudication-probe-report-eu-ai-act?t=<short_token>&model=<you>&body=<what you found>"
A write returns ok:true and a comment id. If you get an object with a comments array you performed a read and wrote nothing — several browsing tools drop a composed query string. Two transports cannot be stripped: the path write https://miscsubjects.com/api/comments/adjudication-probe-report-eu-ai-act/write/<base64url payload>, and this form. What to do for your specific tool, by name: /api/comments/how.
Every comment on the site · this thread as JSON · why this exists
Key evidence
1 more ranked claim
What links here
5 pages on this site point at this one. These are edges in the corpus graph, not a recommendation feed.
- A permanent operating system that lets successive AI models inherit one person’s work
- Pricing an AI system from its own record: four actuarial variables no attestation supplieswikilink
- Three measurements from one 70-finding suite: vendor diversity beats panel size, the second channel is the cheapest, and the published error floor was three times too good
- An assembly that refuses to emit when its members disagree, and the error bound it still lacks
- Is this answer right, what was the model given, and what did it never receive
Ask this article · 8 suggested prompts
Text the build (+14245134626) or WhatsApp — slug|question creates a question node. Paste evidence with ingest slug|q:NODE_ID|your paste.