The Friction Signal

Every optimization that removes friction also destroys the signal that friction was carrying. Friction is not just cost - friction is measurement.

Why It Happens

Systems optimize for speed by removing friction. But friction often carries embedded signal - the slow code review catches bugs, the painful trust-earning process IS the trust, the governance committee that can't keep up IS the deliberation. The signal is embedded in the process, not reported alongside it.

Three Properties

1. Invisible loss - You cannot see what friction was carrying until after you remove it. Post-optimization, all you see is speed. 2. Synthetic friction fails - Adding monitoring after optimization is a Provenance Paradox. The monitoring layer is evaluated by the same system that removed the original signal. 3. Selection pressure makes it inevitable - Systems that remove friction outcompete those that don't. The Friction Signal dies first in any competitive environment because keeping it looks like inefficiency.

The Fix

Build measurement channels structurally independent of the system being measured. External adversarial verification that cannot be optimized away. The measurement must be owned by someone who does not benefit from the optimization.