Catching agent repo drift before evals

After covering basic linting checks in my previous post , there is another layer worth adding before the more costly behavioral evals. You can catch repo drift and convention violations with deterministic checks before paying for slower behavioral eval runs. Reference integrity check One place to start is reference integrity, for example: referenced code still exists referenced code still contains real implementation # reference integrity if [ -n " $resolved_ref " ] ; then case " $ref " in * .ts| * .js| * .tsx| * .jsx ) if rg -q '^\s*(export\s+)?(async\s+)?(function|class|interface|type|const|let|var|enum)\s' " $resolved_ref " ; then log_pass " $relctx -> $ref exists and has declarations" else log_error " $relctx -> $ref exists but has no clear declarations" fi ;; esac else log_warn " $relctx references ' $ref ' which no longer exists" fi This is useful because files can still exist after a refactor, but stop being useful references for your agent. Architecture drift checks Agents tend