Building Trustworthy APIs by Representing Data Gaps Honestly

When building APIs with incomplete data, the instinct to ship and fix later is dangerous—especially when wrong results look identical to correct ones. This article demonstrates how adding a third enum state ('pending') transforms the type system into a guardian of API honesty, preventing unverified estimates from masquerading as facts. The pattern generalizes to any domain where data maturity varies.