Security Bug Spawns 'Confrontation-Point Law' After Audit Missed Direct Write Paths

On July 3, 2026, a developer revoked self-write access on eight sensitive database columns, only to revert the change hours later after an admin feature began throwing 403 errors. Investigation revealed that within the same function, a legitimate RPC call coexisted with an unguarded direct-write to the users table — a gap a prior human audit had missed by issuing a file-level verdict based on a comment rather than line-by-line verification. The incident prompted a fully mechanical re-census on July 4, using grep, AST analysis, and actual database privilege queries to re-derive every claimed write path from scratch. This process uncovered three additional admin direct-write points — renewTier, dismissBinding, and importMembers — that the earlier review had overlooked entirely. The experience led the team to formulate the Confrontation-Point Law, which requires every security judgment to be verified by a machine query at the exact boundary where intent and actual system state must agree, explicitly excluding narrative or code-reading as sufficient evidence.