# The Otter Surfaces A companion to [[05.20.26 - The Otter and the Dust Bin]]. That piece made peace with going under: a project that is not being built is underwater, surfacing curious and otter-like when the right association bobs along. This one is about the other half of the animal's life. An otter cannot live below. It comes up to breathe, to eat, to check where the shore is. Prototyping is the coming up. A vision held too long without contact does what anything held underwater does: it warps. You remember the customer instead of meeting them. The imagined product grows more elegant and more wrong. The prototype is the correction - each build in real hands is a breath at the surface, a sounding taken against the actual bottom. Vibe Reader keeps proving this on schedule. Roaming, the History tab, the data-durability reckoning ([[Vibe Reader Product Log|log, 2026-08-26]]) - all of it came from routine use surfacing what speculation never would. The discipline underneath: stay hands-on enough that the prototype's definition mirrors the real usage of the product. That means watching what people actually do with it, where they actually trigger it, and what they trust it with. The prototype is the instrument that positions against the vision, and the vision is refined and iterated toward through that tension. The vision is the far shore. The prototype is the swimming. You navigate by the difference between where you thought the shore was and where the last surfacing showed it to be. The case for prototyping is buoyancy rather than "failing fast." It is the practice that keeps a builder above the water and engaged with the reality of customers while the vision stays live below, refining with every dive and every breath. A product defined only in documents is a product defined by memory. A product defined by its prototype is defined by contact, by time breathing above the water, and being witnessed by a few observers.