roadmap(#235): research Thoughtworks AI Evals vs our existing pipeline - #301
Merged
Conversation
User call-out 2026-05-01. Research-only row asking whether AI Evals methodology (pre-deploy validation + post-deploy runtime monitoring, quality gates) adds anything beyond what we already have: Tier 1/2 E2E + score-history + CUSUM + token-spike. Likely NO-GO since we already implement the methodology, just under different naming. ~1-2 hr write-up when picked up.
BaseInfinity
added a commit
that referenced
this pull request
May 5, 2026
#301) User call-out 2026-05-01. Research-only row asking whether AI Evals methodology (pre-deploy validation + post-deploy runtime monitoring, quality gates) adds anything beyond what we already have: Tier 1/2 E2E + score-history + CUSUM + token-spike. Likely NO-GO since we already implement the methodology, just under different naming. ~1-2 hr write-up when picked up.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds ROADMAP row #235 — research-only item asking whether Thoughtworks' "AI Evals" methodology (decoder article) adds anything beyond what our existing E2E pipeline already does.
Likely outcome (will confirm during research)
Mostly NO-GO — we already implement the methodology under different naming:
tests/e2e/run-tier2-evaluation.sh+evaluate.sh(10-criterion rubric, 5 trials, 95% CI)score-history.jsonl+cusum.shdrift detection +hooks/token-spike-check.shcost anomalySame pattern as #76 (Promptfoo NO-GO) and #77 (constrain-to-playbook NO-GO).
Effort
~1-2 hr write-up to
.reviews/research-235-ai-evals.mdwhen picked up. Zero API needed.Test plan