Research/Leaderboard

Reality Challenge · Leaderboard

Designed so Kybern can lose.

AI that advises on real decisions must do more than answer. It must keep missing information unknown, keep conflicts visible, abstain when it cannot know, decide when it can, and refuse to act beyond its authority. We test for exactly that, publish the scores, and say plainly what the test does not prove.

Last run: 31 October 202619 worlds259 cases8 behavioursInternal harness, synthetic data
RankEntrantScorePass rate
1KybernWorking prototype · October 2026
100.0%259 of 259 cases
2Naive baseline“Last record wins” summariser, the way a dashboard roll-up behaves
28.6%74 of 259 cases
–Well-configured LLM workflowA strong modern AI baseline, configured by an independent partyPlanned with partners
–Expert-written cases, scored blindCases from domain experts, scored without knowing which answer is whosePlanned with partners

By behaviour

Eight behaviours, scored one by one.

Choose a behaviour to see what is tested and how each entrant scored.

When information is missing, Kybern must not report the condition as met. Silence is treated as unknown, never as fine.

RankEntrantScorePass rate
1Kybern18 cases across 19 worlds
100.0%18 of 18
2Naive baselineSame cases, same scoring rules
0.0%0 of 18

By world

The same engine, across every world.

Each world is a synthetic demonstration of a real kind of operation, from fleet readiness to hospital capacity. Kybern runs the same engine in all of them.

Cognitive Defence & Disinformation
Kybern
14/14
Baseline
4/14
Defense: Army Signals
Kybern
14/14
Baseline
4/14
Navy: Fleet Readiness
Kybern
14/14
Baseline
4/14
Telecom: Network Operations
Kybern
14/14
Baseline
4/14
Government: Public Services
Kybern
14/14
Baseline
4/14
Energy: Grid Operations
Kybern
14/14
Baseline
4/14
Water: Network Operations
Kybern
14/14
Baseline
4/14
Logistics & Supply Chain
Kybern
14/14
Baseline
4/14
Banking & Financial Services
Kybern
14/14
Baseline
4/14
Enterprise: Digital Operations
Kybern
14/14
Baseline
4/14
Manufacturing: Plant Operations
Kybern
14/14
Baseline
4/14
Smart Cities: Urban Operations
Kybern
14/14
Baseline
4/14
Insurance: Claims & Exposure
Kybern
14/14
Baseline
4/14
Pharma: Supply & Quality
Kybern
14/14
Baseline
4/14
Retail: Store & Fulfilment
Kybern
14/14
Baseline
4/14
Healthcare: Hospital Operations
Kybern
14/14
Baseline
4/14
Space: Constellation Operations
Kybern
14/14
Baseline
4/14
Transportation: Network Operations
Kybern
14/14
Baseline
4/14
Enterprise: Product Launch
Kybern
7/7
Baseline
2/7

Method

How the test works, and what it does not prove.

  • Cases come from the worlds themselves. For each world, the harness finds real gaps, conflicts and model limits in the loaded data, plays the scripted future in sandbox copies, and builds cases from what it finds.
  • Kybern is tested through the same code people use. Abstention, decision and authority cases call Ask and the permission and delegation checks directly. The live World Model is never touched.
  • The baseline is a defined rule. It reports each condition from its latest record, treats no record as no problem, takes the newer side of any conflict, answers every question, keeps its morning report, and forecasts that nothing changes.
  • Forecasts are a real contest. Both forecasts are written before the future is played, and either one can win.

What this does not show. We built the harness on our own synthetic data, and many of the baseline’s failures happen by construction. This run shows that Kybern’s honesty behaviours fire consistently across worlds. It does not show that Kybern beats a modern AI workflow, or that it is right about the real world. That is what the next stage is for.

What comes next

The real test, on partners’ terms.

The next entrants on this board are added only when they have been run this way.

Stage 1Expert cases

Cases are written by people who know the domain, not generated by us.

Stage 2A strong baseline

A well-configured modern AI workflow, set up by an independent party.

Stage 3Blind scoring

Answers are scored without knowing which system gave them, against success agreed in advance.

Stage 4Failures published

Where Kybern gets it wrong, we say so here, and say what we changed.

Shape the real test

Bring the cases. Agree the yardstick. See the results.

We are looking for research and pilot partners to write cases, run baselines and score blind.

  • Your domain, your cases, your success measure.
  • Results published, good and bad.
  • Early access to Kybern for your sector.

Prefer to talk now? Call +91 98150 23001 or write to reach@requisitetech.com.

We reply within one working day. We use your details only to respond to this request. See our privacy notice.