Status: IN
Operational concerns — error signaling strategies (exceptions vs return codes vs None), eviction timing (eager vs lazy vs deferred), and failure reporting — are designed per-module with no cross-cutting conventions, meaning each module makes locally reasonable choices that collectively produce an unpredictable system-wide operational surface for callers.
Both nodes identify absent cross-cutting conventions in different operational dimensions; the emergent property is that operational unpredictability is systematic, not incidental
Depends on (SL): error-boundaries-are-module-local, eviction-timing-has-no-codebase-convention