Ricche Technical Note 003
Evidence-Based Verification Methodology
Ricche Technical Note 003 — Manfred Fuss, Founder, Ricche Ltd · June 2026.
Introduction
Evidence-based verification is the practice of deciding what to trust on the basis of evidence rather than on the basis of confidence. Within Ricche it is an operating discipline rather than an ideal: a statement, conclusion, signal, observation, or system condition is trusted only to the degree that it can be supported, examined, and — where its weight warrants — reproduced.
People, processes, and organisations routinely conflate the two. A decision system that returns a result quickly, or an analyst who presents one fluently, can earn belief that the underlying evidence does not justify. This is not occasional carelessness; it is a structural tendency of any process that rewards a confident answer over a verified one.
Confidence is a presentation. Correctness is a property.
Ricche keeps them apart by construction. Confidence is never an input to a decision; it is an output a claim earns only after verification. The sections that follow set out how that separation is held in practice — how evidence is weighted, how verification is carried out, how uncertainty is named, and where the method stops. The account is deliberately conceptual: it describes the discipline, not the systems that apply it.
Five ordering rules govern the method when its goals compete. They are written as precedences because, in a live decision, these goals routinely conflict — and the order in which the conflict is resolved is what determines whether the result can be trusted:
- Truth before speed
- Verification before confidence
- Evidence before opinion
- Reproducibility before narrative
- Auditability before assertion
The evidence hierarchy
Not all evidence is equal. A claim can be supported at different levels of strength, and a useful discipline is to ask which level it actually rests on. Ricche weighs evidence on an ascending hierarchy:
- Level 1 — Assertion. A statement offered without support. It may be correct, but on its own it carries no evidential weight.
- Level 2 — Observation. A claim grounded in something seen or recorded. Stronger than assertion, but it can be incomplete, selective, or misinterpreted.
- Level 3 — Measurement. An observation made precise and quantified. Measurement reduces ambiguity, provided the method and its conditions are sound.
- Level 4 — Independent Verification. A finding confirmed through a separate path that does not inherit the original's assumptions, inputs, or method. Re-running the same computation on the same data is repetition, not verification; genuine independence means a second path that could have failed where the first succeeded. Ricche treats a claim as independently verified only when the confirming path could, in principle, have returned a different answer.
- Level 5 — Reproducible Evidence. A result that can be re-derived under stated conditions, by others, more than once — not merely re-cited.
- Level 6 — Operational Proof. Evidence that holds up under real conditions over time, including edge cases and stress, rather than only in isolated tests.
Each level is a threshold, not a label: the strength of evidence must match the weight of the claim, and a conclusion that has only reached observation is not permitted to be expressed as though it had been reproduced.
Verification principles
The hierarchy says how strong a piece of evidence is. It does not say how the checking is done. Verification is an activity, and Ricche conducts it according to a small set of working rules:
- Hold the claim as unconfirmed by default — acceptance is withheld until a claim has been tested, however authoritative its source appears. Plausibility is not confirmation.
- Confirm by a different path — verification is sought from a path that does not share the original's assumptions, so that a shared error cannot pass unnoticed.
- Attempt to break it, not only to support it — effort is spent trying to make the conclusion fail, because a claim that survives a genuine attempt to disprove it is worth more than one that was only ever defended.
- Test at the boundaries — checking concentrates on the conditions under which the claim would stop holding, not the conditions under which it obviously holds.
- Carry the residual doubt forward — what remains unverified is recorded alongside what was confirmed, so a conclusion never travels without its caveats.
- Re-open on change — a verified conclusion is revisited when its inputs or conditions move, because verification has a shelf life rather than a permanent grant.
Handling uncertainty
Honest verification needs an explicit vocabulary for the state of a claim, because the state determines what may be done with it. Ricche works with four states, each carrying a different consequence, and uses them consistently wherever it reports verification:
- Unknown — the evidence needed to decide has not been gathered, or does not exist. The claim may be investigated but may not be relied upon, and it cannot be used to support a downstream conclusion.
- Partially Verified — some supporting evidence exists, but it is incomplete or not yet independent. The claim may be used with stated caveats and at reduced weight, never as settled.
- Verified — the claim is supported by sufficient, examinable evidence at a level appropriate to its weight. It may be relied upon, and the evidence that earned the status stays attached to it.
- Disproven — the evidence contradicts the claim. It is retired or revised, and the fact that it was once held is kept, so the change of view is itself on the record.
Why 'Unknown' is honest
Naming a state "Unknown" is frequently more honest, and more useful, than asserting unsupported certainty. An acknowledged gap can be assigned, investigated, and closed; a concealed one cannot.
Ricche therefore treats "Unknown" as a first-class, reportable result, not a failure to answer. A process willing to say what it has not established is easier to trust on what it claims to have established — and a verification process that never returns "Unknown" is usually not verifying, only asserting.
Auditability
Verification has little value if it cannot itself be examined. The standard Ricche applies is deliberately blunt: a conclusion that cannot be reconstructed from its record is treated as unverified, however it was reached. In practice that means a later, independent reviewer must be able to follow how a conclusion was arrived at, which in principle requires:
- Recorded evidence — the basis for a conclusion is captured at the time, not reconstructed from memory afterwards.
- Traceability — a conclusion can be followed back to the specific evidence and reasoning it rests on.
- Reviewability — that trail is legible to a competent reviewer who was not involved in reaching it.
- Historical accountability — superseded conclusions remain inspectable, so a change of view can be understood rather than silently overwritten.
Practical application
The discipline is easiest to judge by how it behaves at specific decision points. Three recurring cases:
A reported state versus an observed state. When a component reports that it is healthy, that report is a claim, not evidence of health. The method requires the condition to be confirmed through a path independent of the component's own self-report before the "healthy" state is trusted; where it cannot be independently confirmed, the state is recorded as Unknown rather than assumed good. The cost is occasional redundancy; the benefit is that a confident but incorrect self-report cannot quietly become an accepted fact.
A finding that is convenient. When a result supports a conclusion that is already preferred, it receives more scrutiny, not less — agreeable evidence is the kind most likely to be waved through, so its convenience is treated as a reason to check it harder. Wherever possible a claim is framed so that it could be disproven before its conclusions are acted upon.
A decision made under time pressure. Speed does not suspend the method; it changes what is recorded. A decision taken quickly still captures the evidence it rested on and the state of that evidence at the time, so it can later be reviewed on what was actually known when it was made rather than on how it happened to turn out. This is where "truth before speed" is tested, and it is the case the discipline exists for.
These are illustrations of how the discipline behaves, not descriptions of any specific system.
Limitations
No methodology can eliminate uncertainty. Evidence can be incomplete, conditions can change, and even reproducible results hold only within the bounds in which they were established. A disciplined method reduces the likelihood and the cost of error; it does not promise their absence.
Verification reduces risk. It does not guarantee perfection, and it should not be presented as if it does. A claim of completeness or finality would itself be unsupported — and therefore inconsistent with the method this note describes.
Conclusion
Verification is a process, not a status — the continuing work of testing what is believed against what can be shown. Its product is not certainty but calibrated trust: belief held in proportion to the evidence behind it.
Everything above serves one discipline. Evidence is weighted by how strongly it is established; checking is done by trying to break a claim, not only to support it; uncertainty is named rather than hidden; and conclusions are kept reconstructable so they can be challenged later. What the discipline rules out is the manufacture of evidence to fit a conclusion already reached — the single failure that makes a result look authoritative while leaving it unreliable. A methodology is ultimately only as credible as its willingness to return an uncomfortable answer, and that willingness is the standard Ricche holds itself to.