Gap Scan

A logical gap is required behavior that survives only because somebody remembered to implement it. Types, linters, and ordinary diff review often cannot expose an omission elsewhere in the system.

Gap Scan makes absence visible by evaluating one falsifiable rule across an enumerated population. It is a matrix engine, not a universal definition of good code:

• the caller, repository, or built-in catalog defines the property being examined;
• the skill enumerates every relevant instance and applies the same predicate;
• blanks, unknowns, and unjustified differences become visible;
• every reported finding must be verified in the underlying code or artifact.

Do not claim absolute completeness. The result is complete only relative to the frozen scan contract and the enumerated population.

Self-contained execution