State Is More Than a Number
Why facts, plans, scenarios and corrections need different places in the system.
The ambiguity travels with the value
A livestock number might mean animals observed, the latest reconciled inventory, an intended purchase or an alternative growth scenario. The digits alone cannot tell me which. If the system copies the value without its meaning, every downstream calculation can become more consistent with the wrong premise.
The structured RanchOS foundation, recorded in September, gave those distinctions an explicit form in a Supabase state layer. Entities, claims, source versions and resolutions allowed information to remain attached to its context. The database did not decide which source had business authority; that had to be established in the surrounding source contracts and review process.
A second set of distinctions
State class is not enough. An observation, an operator report, a model output and an AI interpretation have different evidentiary weight. A recorded decision is not execution. Even a model run that actually occurred still produces an estimate of the world, not a direct field measurement.
The system therefore needs to preserve who or what produced a statement, when it applies, when it was observed, when it was recorded, and the exact source location. Missing information should remain missing. A Current answer should not borrow a value from a Scenario simply because that is the only number available.
Correction without erasure
New evidence should change the current interpretation without quietly rewriting what we previously believed. Append-only correction preserves the earlier claim, adds the new evidence and records how the newer resolution supersedes the older one.
That history matters when a later question asks why we acted. The best answer today may differ from the information available when a decision was made. Keeping both makes a correction understandable and allows a later session to avoid repeating the same error.
Coverage remains uneven. Structured storage is useful where the source meaning and refresh path are defined. Elsewhere, the system still needs to return to documents or ask me. A database does not remove the need to reconcile reality.