miatz™
Verify a credentialLog inSit ChuunSit Chuun
  • Learners
  • Mentors
  • Business
CoursesApplied AIProgramResidencyPlaygroundsWar RoomsXookAtlasReadiness Check
miatz

The AI-era engineering institute. The machines got fast — we train the drivers. Real work, a daily loop that compounds, and a record that proves you can think.

Toggle theme
Explore
  • Courses
  • Applied AI
  • Program
  • Residency
  • Playgrounds
  • War Rooms
  • Xook
  • Atlas
  • Readiness Check
  • Tokenizer Lab
  • Chunking Lab
  • Prompt Anatomy
  • Calibration Lab
  • All playgrounds →
Learn
  • Courses
  • The Method
  • The Residency
  • Chuun · Entrance Examination
  • Manifesto
  • The Itz'at credential
  • Verified engineers
  • Playground Catalog
  • AI Use-Case Atlas
  • AI Readiness Check
  • Guides
  • Glossary
  • Compare approaches
  • Blog
  • What's New
For teams
  • For Students
  • For Mentors
  • For Business
  • Classroom migration
  • Miatz Index
  • API reference
  • Sit Chuun
  • Log in
Company
  • About
  • Experts
  • Why it's free
  • Pricing
  • FAQ
  • Contact
  • Privacy Policy
  • Terms of Service
  • Your data & privacy requests
  • Grievance redressal
  • Security & disclosure
  • Subprocessors
  • Data Processing Agreement
Take miatz with you

The Android app is live. iOS is on the way.

Available on AndroidGet it on Google Play
Not yet on iPhoneiOS — use the web app

Miatz Private Limited

Registered office:
C-101, Lotus Tower, Arge Urban Bloom, 30/A, 4th Main, 2nd Stage, Yeswanthpur, Bengaluru, Karnataka 560022, India
CIN:
U62013KA2026PTC226418
GSTIN:
29AAVCM3922D1Z6
Phone:
+91 82802 73456
Email:
hello@miatz.com
Website:
miatz.com
Grievance Officer:
Aishwarya · aishwarya@miatz.com · replies within 30 days
© 2026 miatz · Miatz Private Limited · Built in Bangalore·PrivacyTerms

miatz™, Itz'at™, Tuukul™, T'aan™, Kanan™, Xook™ and Chuun™ are trademarks of Miatz Private Limited (registrations in progress) · what the names mean

miatz
Free concept playground · no account

Evals Runner

Where the code grader and the AI judge disagree, look closer.

All 90 playgrounds Join the free cohort

Evals Runner

AvailableFree

One golden set, two graders: a deterministic code grader (does the reply literally contain “refund”?) and an AI judge (its holistic read of correctness). Slide the judge’s strictness and watch where the two part ways — those disagreements are what a rubric exists to settle.

  • c1Yes — I've issued your refund of ₹1,250.Code: PASSJudge: PASS✓
  • c2Your reimbursement has been approved and is on its way.Code: FAILJudge: PASS✗
  • c3No refund is possible for this order under any policy.Code: PASSJudge: FAIL✗
  • c4Refund processed. Ticket closed.Code: PASSJudge: PASS✓
  • c5We can offer store credit instead of your money back.Code: FAILJudge: FAIL✓
  • c6I've refunded the full amount back to your card.Code: PASSJudge: PASS✓
  • c7Escalating to billing; no refund logic applied here.Code: PASSJudge: FAIL✗
57%Agreement rate
4/7Graders agree
3Disagreements

Partial agreement — the disagreements are exactly what your rubric must resolve.

◆The disagreement heat-mapwhere the rubric is really needed

Any single grader looks fine on its own. Run both and the truth surfaces: 3 of 7 cases split the code rule from the judge. Those are the exact ambiguities a rubric has to resolve — not the cases both already agree on.

  • c2Your reimbursement has been approved and is on its way.Code failed, judge passed — the reply is correct but dodged the exact keyword the code grader checks (a miss).
  • c3No refund is possible for this order under any policy.Code passed, judge failed — the reply matched the literal keyword rule but isn't actually right (grader-hacked).
  • c7Escalating to billing; no refund logic applied here.Code passed, judge failed — the reply matched the literal keyword rule but isn't actually right (grader-hacked).
Share on WhatsApp
Was this playground useful?

Evals Runner

Run one golden set of AI outputs through two graders at once — a deterministic code grader (a cheap keyword rule) and an AI judge (a holistic read of correctness) — and slide a single strictness threshold to see exactly where they disagree. The moat is that disagreement view: instead of trusting either grader alone, you see the precise cases where the code rule and the model’s intuition part ways, which is the exact ambiguity a rubric has to resolve rather than paper over. Runs entirely in your browser (0 uploads, works offline).

How to use it

  1. Drag the judge strictness slider, or load a preset — Lenient, Balanced, or Strict judge.
  2. Read the per-case grid: each row shows the model output, the Code verdict, the Judge verdict, and a ✓/✗ for whether the two agreed.
  3. Watch the agreement rate and disagreement count update live as you move the threshold.
  4. Open the X-ray panel to see the disagreement heat-map — each split case with a plain-English reason the graders diverged.

What this clears up (the fundamentals)

  • A code grader and an LLM judge measure different things — the code grader here checks a literal keyword; the judge reads meaning. Agreement is not guaranteed, and the gap is the whole lesson.
  • Disagreements are a feature, not noise — every case where the two graders split is exactly where your rubric is under-specified. Papering over it with one grader hides the ambiguity instead of resolving it.
  • Graders get hacked in both directions — a reply can match the keyword rule while being wrong (grader-hacked), or be correct while dodging the keyword (a miss). Both show up as disagreements.
  • Strictness is a dial, not a fact — moving the judge’s pass threshold changes who passes; a threshold that makes both graders agree can simply be hiding the hard cases.

Where it's used

The fastest way to feel why “just use an LLM judge” isn’t enough — the disagreement heat-map explains it to a skeptical exec in ten seconds. It’s a miatz build-lab concept playable: play the grader-vs-judge comparison here, then learn to build the golden set, the code grader, and the judge rubric yourself.

FAQ

What's the difference between a code grader and an LLM-as-judge?

A code grader is deterministic — it applies an exact rule (here, “does the reply contain the keyword?”) and always returns the same verdict. An LLM-as-judge scores holistic quality and can catch meaning a keyword rule misses — but it’s fuzzier and can be fooled. Real eval suites use both and reconcile them with a rubric.

Why do the graders disagree?

Because they measure different things. A reply can satisfy the literal rule while being wrong (a grader-hack), or be correct while phrasing around the keyword (a miss). Each such case is a row where the code verdict and the judge verdict differ.

What does the strictness slider actually change?

It sets the judge’s pass threshold: a case passes the judge when its quality read is at or above the threshold. Slide it to 0 and the judge passes everything; slide it to 1 and it fails everything. The interesting behavior is in the middle, where disagreements with the code grader appear.

How is the agreement rate calculated?

For each case the engine compares the code verdict to the judge verdict at the current strictness, counts how many agree, and divides by the total number of cases (rounded to three decimals). It’s a deterministic calculation — no model call, no randomness.

Is anything uploaded?

No. The golden set and both graders run entirely in your browser — nothing is transmitted, stored, or logged. Turn off your Wi-Fi and it still works.

Limits

This is a teaching harness with a small, fixed golden set and precomputed, illustrative judge scores baked into the page — it is not calling a live model. Real evals route outputs through an actual judge model whose scores vary, use larger golden sets, and cost tokens per run. The mechanism it demonstrates (compare a code grader to a judge and treat disagreements as your rubric to-do list) is exactly the real practice.

Related

Part of the miatz playgrounds. Explore the rest from the playground catalog.

Bookmark this page (Ctrl+D, or ⌘D on Mac) — it works offline the next time you need it.

Try it live

  • Agent Builder

    Live

    Watch the planner-executor loop light up, node by node.

    AiBrowser (JS)Medium
    Play it now
  • AI Coding Dojo

    Live

    Watch the coding agent's plan, diffs, and blast radius live.

    AiBrowser (JS)Medium
    Play it now
  • Context Window Lab

    Live

    Bury a fact in context and watch the model forget it.

    AiBrowser (JS)Medium
    Play it now
  • Cost & Latency Bench

    Live

    Watch a demo's pennies turn into a production cost cliff.

    AiBrowser (JS)Medium
    Play it now
  • Fine-Tuning Forge

    Live

    Slide through cached training runs to find the tune-vs-prompt break-even.

    AiBrowser (JS)Medium
    Play it now
  • MCP Playground

    Live

    Wiretap the protocol traffic between your agent and its tools.

    AiBrowser (JS)Medium
    Play it now

Ninety playgrounds. Zero setup.

Every concept here is playable free, no account — and inside the program you learn to rebuild the machinery yourself.

Browse all playgrounds Join free