From c293f53d90931e2121ba012510335a9458e5f5bd Mon Sep 17 00:00:00 2001 From: Sheldon Finlay Date: Sat, 28 Mar 2026 12:20:31 -0400 Subject: [PATCH] docs: make runtime verification claim accurate Only claim what the evaluator actually does: runs tests, builds, and checks for errors. Don't overstate MCP server discovery. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3a212e5..40a5996 100644 --- a/README.md +++ b/README.md @@ -97,7 +97,7 @@ Before the loop starts, the planner generates contracts for each story. These de ## Runtime Verification -The evaluator verifies code actually runs, not just that it looks correct. It uses whatever testing tools are available in your environment — test runners, linters, build tools, and any MCP servers you have installed (e.g., browser automation, simulator interaction). The more verification tools available, the more thorough the evaluator can be. +The evaluator doesn't just read diffs — it runs tests, builds the project, and checks for runtime errors using whatever tools the project already has (test runners, linters, build commands). ## Design Principles