What "Coherence" Means in a Disclosure System
Hedamo does not check whether a claim is true. It checks whether a producer's own declarations are consistent with each other.
One of the questions Hedamo encounters most frequently is: "What if a producer lies?"
The answer is built into the architecture. Not through investigation, but through structure.
When a producer submits a disclosure, they declare information across multiple fields: processing methods, ingredient sourcing, certifications held, production temperatures, geographic origins, and more. These fields are not isolated. They relate to each other. And when they contradict each other, the system surfaces the inconsistency.
This is what Hedamo calls a coherence check.
If a producer declares "cold-pressed" alongside a processing temperature of 45°C, the system notes that industry definitions of cold-pressing typically reference temperatures below 27°C. If a producer declares "single-estate origin" but lists multiple origin regions, the system surfaces that discrepancy. If a producer claims organic certification but names no certifying body, the system flags the gap.
None of these flags constitute an accusation. The system does not say the producer is wrong. It says: "These two declarations appear inconsistent. The producer may clarify, amend, or explain." The inconsistency may reflect a terminology difference, a regional standard, or a data entry error. The system does not resolve it. It makes it visible.
Over time, this creates a self-disciplining environment. Declarations are structured, permanent, and attributed. They are comparable across products and visible to multiple audiences. A producer whose declarations are internally inconsistent is not penalized by the system — but the inconsistency is there for anyone reading the disclosure to see.
The system does not need to verify. Structure does the work.
