LOOPforgeThe judge's bell — evaluation loops and honest verdicts

The judge that won't fake a win.

LOOP writes the builder and critic prompts for an evaluation loop and records the verdict — and it refuses to write won without a capture pair, a blind pick, and the time the pick took. The reason every stamp in HEPHforge is worth believing.

“I only say what the strike said. Captures, blind pick, decision time — then I'll write it. Until then: unverified.” Echo

JAMforgepiece under test
NODEforgesequence
ANVILforgeverdict
GATEforgeheat · session
LOOPforge

01 · The problem

A smith who stops listening to the ring starts believing his own hands. That's how bad blades leave a shop with good names on them.

→ · The answer

A judge whose whole body is built to refuse. No won without a capture pair, a blind pick, and the time the pick took. Unverified is a legitimate word here.

02 · What it does

The judge that won't fake a win. Paste-ready prompts, honest verdicts, and a won that needs evidence.

A won that means won

The verdict recorder physically refuses a win without a capture pair, a blind pick, and the time the pick took.

Paste-ready prompts

Builder and critic prompts generated for whatever harness you run. LOOP writes; you run.

Cold critics

The judge has never seen the work before. Fresh context every strike.

Decision time is a verdict

An instant 6/6 and a slow 4/6 are different results, and LOOP says so.

Unverified is allowed

Shipped-but-not-judged gets an honest label instead of a fake green.

The floor under the suite's honesty

Every stamp on every HEPHforge page is credible because this tool exists.

03 · How it connects

Where LOOPforge sits on the wall.

Every tool draws heat and session through GATE and hangs on the Hall. These are its hand-offs.

04 · Tended by

Echo

Echo only repeats what the strike said.

Echo is the anvil's ring — the sound that comes back true or false with every strike. She was made so she cannot record a victory the capture didn't earn.

Her rule: No won without the trio. Ever.

05 · Roadmap

Where LOOPforge goes from here.

  • 01

    Judges pieces from any post

    ANVIL slices, JAM entries, WIKI boards: the loop doesn't care who struck it.

  • 02

    Sequenced by NODE, never replaced by it

    Spark can run the steps around a judgment; only Echo records it.

  • 03

    NODE-sequenced evidence around verdicts

  • 04

    Pieces from every post flowing into one judge

  • 05

    Or: LOOP folds into SKILL as a playbook

  • 06

    Hosted status/monitoring view (if hosted at all — never a prompt API)

06 · Get started

The judge that won't fake a win.

You get a verdict you can show someone. One Gate sign-in opens it and every other tool on the wall.