Skip to content

rmasood1122/eval-conductor

v1.4.3MIT

Prove your tests/evals didn't regress. Fail-closed release gate for scores you already produce (pytest, promptfoo, JUnit, any JSON) with signed, tamper-evident, pre-registered receipts. Gate via MCP tools; design gates via skills.

evidence-discipline

Use when work is about to be called done and the claim needs proof — "mark this step done", "CI passed, close it out", "how do I prove this is finished", "just use the last green run as evidence", "what's left before we ship" — and before YOU say a task is complete. A step closes only on a real, green CI run of this code (never a placeholder URL, pasted command text, or an older green run), reversals are recorded rather than erased, and the 27-step conductor ledger (/conductor) enforces it.

Read SKILL.md at the source

Pinned to revision 37490b7348e9, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.