feat: a design-time coverage review, measured and left off

A reviewer role reads the requirements and recommendations against the Checks
when the Target architecture is first submitted. Three runs of case 03: it did
not stop the validator sending the design back, and the designs it reviewed
ended with 87 and 93 Checks against 52, so they cost more. It stays behind
DESIGN_COVERAGE_REVIEW, off (iteration 6 step 13).

Also: the schema review no longer reads `true` or `false` in backticks as a
setting name.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-10 12:33:06 +01:00
parent 1cf1234143
commit ee1ba38867
13 changed files with 401 additions and 6 deletions

View File

@@ -59,6 +59,10 @@ MAX_PARALLEL_SPECIALISTS=4
CHECKPOINTER=sqlite
CHECKPOINT_DB_PATH=checkpoints.db
# A model reads the requirements against the Checks when the Target architecture is
# first submitted, and returns what no Check verifies. One model run per Execution.
DESIGN_COVERAGE_REVIEW=false
# Jev decision service, through the TypeSafe AI Python SDK (typesafe-sdk).
# Leave the key unset to run without it: every decision then takes its fallback.
# TYPESAFE_API_KEY=