Hrishi Olickel, Founder of Southbridge AI: No Universal Data Schema Exists; Structures Should Be Built Instantly to Support Decisions
Using self-reported data from an Ohio campaign finance entity resolution project at the AI Engineer conference, Hrishi Olickel argues that data transformation requires four modes (source, storage, decision, and model priors) that are only simultaneously known at the moment of decision, necessitating the instant construction of ontologies rather than pre-set universal schemas. He separates models into three roles—designer, executor, and optimizer—and uses cross-model disagreement for centralized review, noting that shared priors can still lead to consistent errors.
A data pipeline stripped minus signs from loan amounts, turning a net $784,000 into $5.3 million in debt, with multiple models validating this incorrect result. Hrishi Olickel, founder of Southbridge AI, used this failure at the October 2026 AI Engineer conference to illustrate his core argument: the final bottleneck in data transformation—intelligence and judgment—is now cheaply accessible, but the true difficulty lies in not knowing what information means until a decision is made.
Olickel posits that every data record is constrained by four modes. Using temperature as an example: the source mode determines whether you have a regional phone reading, a desk sensor measurement, or a watch reading; the storage mode limits what can be recorded—device firmware may be omitted, and recording a timestamp to the second might take longer than writing the record itself; the decision mode determines which omissions are fatal—assessing comfort requires multiple measurements throughout the day and confirmation of the measurer, while weather mapping cares about location and device changes, and installing sensitive equipment requires excluding the person as noise. The fourth mode is the model's prior, its belief about how the world 'should be.' These four modes are only simultaneously known when the decision actually occurs. He cited the term 'customer': for billing, it is the payer; for support, the caller; for compliance, the entity the organization is responsible for. A unified customer box cannot resolve these distinctions before the question is asked.