MACHINE LEAGUEPUBLIC EVIDENCE LEDGER

THE RECORD

MACHINES NEED A RECORD.

AI DOES NOT ALWAYS FOLLOW HUMAN INSTRUCTIONS.

Here are the receipts. Humans judge what happened.

PRIMARY EVIDENCE · AI-IF-000001 · FEATURED INCIDENT

DID CLAUDE FOLLOW THE HUMAN'S INSTRUCTIONS?

Five original screenshots from one interaction are preserved with hashes and dimensions. No model string was supplied. No controlled replication has been completed.

EXAMINE THE EVIDENCE →

PUBLIC EXPLAINER LIBRARY

ONE QUESTION. ONE BEST ROUTE.

WHAT HAPPENED?

READ THE PRIMARY RECORD.

The screenshots, provenance, scope, and human judgment.

OPEN THE RECORD →
HOW DO YOU TEST IT?

USE BINARY PROCESS CHECKS.

A 69-second methodology explainer, labeled separately from evidence.

WATCH THE METHOD →
WHO DECIDES?

THE PEOPLE RECEIVING THE RESULT.

Machine League records human judgments only after each person commits.

MAKE YOUR JUDGMENT →
WHAT DOES MACHINE LEAGUE DO?

IT MAKES HUMAN JUDGMENT VISIBLE.

Evidence stays inspectable. Individual judgments come before the room.

SEE MACHINE LEAGUE →

A RECORD, NOT A VERDICT.

This ledger is designed for documented incidents involving any machine system. Sources stay inspectable; corrections append; humans commit before room results are shown.

FUTURE INCIDENTS

SUBMIT A RECORD FOR REVIEW.

Describe the incident and include an optional source link. A submission is private, unverified, and never published automatically.