A deterministic engine
Clinical status is computed by a deterministic, versioned and audited engine. There is no live generative model at the point of care that could hallucinate a finding. This is a structural property of the architecture, not a policy promise.
A registry generated from the code
The reviewer registry a physician certifies is emitted from the running engine — one row per rule, with its parameter, threshold, source, and the question it puts to the reviewer. Because it is a projection of the code, it cannot drift from it. You can regenerate it from the delivered source and diff it against the copy we sent.
Provenance on every result
Every result names the guideline and the threshold that produced it, and — once certified — the clinician who certified that threshold. Where a Ministry configures its own national threshold, that value carries its own certifier's name rather than the shipped default's. And where a guideline recommends an action but is silent on how often, the engine still needs an interval — so that interval is declared a Ravisant operational parameter, named as ours, and put to the certifying physician as an explicit question rather than published under a guideline body's name. Stale or unattributed data is gated, not silently scored.
Gates that block the build
Conformance runs inside a continuous quality gate on every change — the same machine that blocks the code if any test fails — so "tested" can never quietly become "untested." Counts published in our documentation are generated from a register, not typed by a person.
Reproducible evidence
The delivery package includes the assurance runs together with the exact commands that produced them. Re-run them against the delivered source and you should obtain the same numbers. If you do not, that is a defect and we want to hear about it.
Where certification actually stands, today
Clinical certification of the reference set is a condition of delivery — a thing we contract for, not a property of what exists this morning. As at 19 August 2026, medical review of the 46-rule set is under way with our consulting physician and is not complete. Technical and legal certifications are likewise conditions of delivery, each by a named external expert, each annexed to the transfer, and each disclosing any commercial relationship with Ravisant on its own face. We would rather you read that here than discover it in diligence.
Regulatory classification is your regulator's call, not ours
We hold a full classification analysis and will share it with your regulatory affairs team. How this platform is classified under your national framework is a determination for your regulator and your counsel; we will support that work with whatever evidence it requires, and we will not pre-empt it. The platform supports clinical decision-making and does not replace clinical judgement: a clinician remains the decision-maker on every finding it surfaces.
Disclosed limits
The package states plainly what it is not, and lists the documents deliberately withheld together with the reason for each. What we acquire from that discipline is the only thing worth having in a sovereign transaction: a buyer who can check.