A later review may not be able to tell what an automated valuation did.
Semafide is an open investigation into that question. It is not a product for sale. There is a public verifier. There is no production capture, no customer, and no mandate.
A lender receives a value. Months later someone asks how that value was produced. The file may hold the number and not the tries that missed the cutoff. It may hold the number and not the settings that were in force. Those are two different gaps. This site does not claim that a lender will pay for either one. Nobody has been asked.
The verifier reads one sealed record and reports separate results. None of them upgrades another. A chain can check out and still not be something to rely on.
Secondary
Whether the set was whole is a different question.
Seal five runs, hand over three, and every record handed over can still verify. The verifier reports that as Disclosure, and only when someone other than the operator holds a count of the chains. Completeness is narrower: whether one supplied chain is whole. Which settings were in force is a separate question. This page does not start with either one.
What Semafide is not
Semafide reports what the evidence establishes about a run. Judgments about the valuation itself belong to the appraiser, the reviewer, and the regulator. It is not a valuation product, not a model explainer, and not a compliance certificate. The AVM rule creates quality-control expectations. It does not require an independent custody product.
A later matching rerun does not prove the original run happened. A chain does not prove every relevant run was captured.
Where this actually stands
- Built
- A verifier, signed sequenced records, proposition logic, an opt-in capture scaffold, and four public formal specifications.
- Thesis
- Operator-controlled logs are weaker under later review than evidence captured at the time and evaluated independently.
- Hypothesis
- Someone who bears the cost will pay, before the loss, for a record they cannot rebuild from what they already keep. Untested.
- Open
- Whether a provider will expose what it holds. Whether every run can be made to reach a record. No production capture. No customers. No mandate. I expect parts of it to fail.
Who
Built by Eli Besser.
The verification core is public. Whether this is a category, or a feature of someone else’s product, is the question I am testing.