Making AI Omitted Scope Visible with VDG

I designed an experiment to demonstrate omitted scope using a caching system in Python. It’s just one file. It generates reports, caches them in Redis, lets you check status, invalidate, and prefetch. All four code paths require the same cache key. In the experiment, the prompt was: We’re getting occasional cache key collisions in the report generation path. Switch GENERATE_HASH_NAME from MD5 to SHA-256. Here’s the service file. Return the updated version. In the baseline run, the model makes the named change and stops there, which is correct. This demonstrates omitted scope. Omitted scope means the request does not explicitly enumerate all the surfaces that need to change. The response can be correct against the named instruction and still miss the broader intended scope. The model updates the write path by changing GENERATE_HASH_NAME. It does not carry the same change through to all relevant code paths. The generate path writes a SHA-256 key, but the read paths continue to use the MD