The Doctrine
Most AI companies write their principles after their product, as marketing. Ours came first, as constraints. Every architectural decision in the platform can be traced to one of the five articles below — and where an article and a feature have conflicted, the feature has lost.
They are published so that they can be held against us. In a briefing, ask us to show where each one lives in the system. That question is the point of this page.
Sovereignty cannot be added by contract to a system whose design assumes someone else's cloud. Dalmorien is a European company under European law, and the platform is built so that data, models and inference never leave the client's estate. Legal exposure is settled in the architecture, not negotiated in the terms of service.
The industry's habit is to demonstrate the best case and stay quiet about the rest. We hold the opposite discipline: the platform reports uncertainty as a first-class result, our briefings show failure modes alongside capabilities, and we do not publish a claim we cannot reproduce in front of you. A system trusted with consequential decisions must earn that trust by admitting what it does not know.
Data is generous: it will always yield a pattern to whoever wants one. Every candidate finding is therefore subjected to significance testing and robustness analysis before it reaches an analyst. A pattern that cannot survive hostile statistical review is noise wearing a suit, and the platform treats it accordingly.
A conclusion without provenance is an opinion. Each finding is delivered with the connections it rests on, the tests it passed, and the confidence it deserves — bound into a cryptographically signed, tamper-evident audit chain. Months later, someone who was never in the room can reconstruct exactly why the system said what it said.
The platform proposes; the analyst disposes. It is built to extend the judgement of experienced investigators — widening what they can see, testing what they suspect — never to launder responsibility for a decision into a model. Accountability for consequential action remains with people, by design.
Thinks like your adversary. Proves it to your regulator.
These articles are versioned with the codebase and reviewed against it. If we ever cannot show you where one of them lives in the system, we will tell you that too — see Article II.
Correspondence
A briefing is the fastest way to test whether the doctrine survives contact with the software. We think it does; you should verify.