Zero-Drift Cascading Pipeline
Idea Lab · Oct 21 2026 · Claude's pick (from Gemini) · Tool/build

Zero-Drift Cascading Pipeline

Gemini's Fresh Ideas playbook says a small model's own confidence score is a bad signal for deciding when to hand a task to a bigger model. This page tests that claim on example data. It runs the same 400 tasks through three routing rules for a kev-0.8b → kev-4b cascade and shows how many wrong answers slip through without escalation, and how many risky approvals get through.

All tasks, scores and outcomes below are synthetic example data generated in your browser. Nothing here was measured on the real Kev.

The four steps, and what this page builds

built here

1 · Calibrate on labeled traces

Learn how often the small model is actually right at each confidence level, using half the traces as training data.

built here

2 · Assign by stakes

Tasks touching money, credentials, deletion or the public edge always go to the bigger model or a human, whatever the score.

not built

3 · "Resonance Stability Index" gate

The playbook gives no formula for RSI or the "execution manifold", so there is nothing to implement. Calibrated accuracy plays this role here.

not built

4 · Topological priority spillover

Preempting work across nodes in 15 ms is a scheduler problem for a large cluster. With one Contabo box running Kev it does not apply.

Run the cascade

Example data · 400 synthetic tasks · seed 7

Escalation vs. errors that slip through

Each curve sweeps the threshold from 0 to 1. Lower and further left is better: fewer wrong answers kept by the small model for the same amount of escalation. The dots mark the threshold you set.

Raw confidenceCalibrated accuracy

Calibration table (training half)

What the small model claims vs. how often it was right. A large gap in the top bins is the overconfidence problem the playbook describes.

Claimed by the proposal, not verified

What a real build needs

About 200 real Kev decisions labeled right/wrong (the 116-case benchmark is a start), a binning or isotonic calibration step in the gateway, a stakes list kept as hard rules outside the model, and a weekly re-check of calibration as task mix shifts. That is a few days of work on the existing gateway, not a new system.

What to try

  1. Push overconfidence to 100 and the unfamiliar share to 50. Watch the raw-confidence lane keep many wrong answers while the calibrated lane escalates them.
  2. Set overconfidence to 0. The two curves converge: calibration only helps when the raw score lies.
  3. Lower the threshold to 20 and compare the risky-approvals row. Only the stakes rule keeps it at zero regardless of the threshold.
  4. Click New sample a few times. Small samples move the numbers around, which is why the real calibration needs a couple hundred labeled cases.

← All Idea Lab demos