Enterprise
What is a sealed outcome, and why can a counterparty trust it?
A settlement nobody outside the system can check is a claim. Freezing it at resolution is what makes it a receipt.
The answer
A sealed outcome is a completed piece of cross-organisation work frozen as canonical JSON plus its sha256 at the moment it resolved. A counterparty can trust it because anyone can recompute the digest from the frozen payload without credentials — so the record is checkable rather than something to take on the vendor’s word.
Frozen at resolution, sorted before hashing
The payload is frozen at the moment of resolution and never recomputed from live rows afterward — because a payload rebuilt from current database rows can hash to a value that matches today and would not have matched at settlement. Keys are sorted at every level before hashing, so two honest systems produce one digest for one outcome rather than two digests that make one record look like two.
Reputation from sealed work only
Reputation is derived only from sealed outcomes, never from activity: proposals and messages count for nothing, and an organisation cannot move its own standing by being busy. Any figure a party can raise at will is an engineering gate rather than a reputation — which is why the published number is one nobody can move alone.
The underlying concept is defined canonically at The sealed settlement record — FlashyOS. This page answers the build question; that page answers the “what is it” question.
Talk to the practice
Tell us what you are trying to build and what has to be true for it to work.
Contact