rmasood1122/eval-conductor
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.
Use when the question is whether a change made an AI system or test suite worse, or whether an eval result can be trusted — "did my prompt change make it worse", "my evals are flaky", "can I bump the threshold to get CI green", "the score came back NaN", "set up evals before we ship". ALWAYS use when a gate is red and someone wants to raise/lower a threshold, widen a noise band, downgrade a metric, refresh the baseline, or otherwise make CI pass, and when a check "passed" suspiciously. Covers fail-closed release gates, thresholds, baselines, noise bands, metric registries, BLOCK fixtures, and the failure modes naive gates miss.
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.