Trust
What Mandact can do. And what it cannot. In full.
Trust does not come from adjectives, it comes from checkability. So both are here: what is proven — and where the limits lie. Both belong to the truth of a system that sells proof.
Proven
✓ No proof, no yes
The entire decision path is one transaction: approval, budget, chain entry, and notification succeed together — or not at all. There is no state «allowed but not proven».
✓ Independently verifiable
Receipts are ES256-signed; the public key is at /.well-known/jwks.json. At /pruefen your browser does the checking itself — the receipt never leaves the page.
✓ Tamper-evident chain
Entries are hash-chained per organisation and bound to their timestamp. Altering, removing, or reordering shows up in the chain check — mathematically, not contractually.
✓ Audited and re-tested
Every P0/P1 finding from four review rounds is fixed and the fixes are documented. More than 2,100 automated checks run before each release — including a gate that tests the website's language against actual system behaviour.
✓ Humans stay in the loop where the law requires it
Escalations and signature completions require a second factor; every intervention becomes part of the chain. Form-bound actions (for example § 623 of the German Civil Code) are enforced by the engine as a human reservation — at runtime, not as a footnote.
Honest limits
Vendors do not usually write this section. We do — because a buyer who knows the limits integrates better, and because our internal documentation has always worked this way (feature reality matrix, known limitations).
We are a single point of failure — deliberately
Fail-closed means: if Mandact is unreachable, critical agent actions stand still. That is intended (standstill beats uncontrolled), but it makes us critical infrastructure. Hence public availability figures and a latency budget we let ourselves be measured against.
Control only where the question is asked
An agent that never asks is never stopped. Mandact proves without gaps what went through the control — not that everything went through it. Full coverage arises when the gate sits on the path there is no way around (gateway, payment egress) — that belongs in every integration discussion.
Self-set rules, self-checked
In single-party operation the chain evidences compliance with your own rules — which is exactly what internal audit and the AI Act ask for. Towards third parties it evidences diligence, not automatic innocence.
No judicial precedent yet
Cryptographic mandates and evidence chains have not yet been tested in a real dispute before a judge — that applies to the whole young category. How evidence is weighed remains at the tribunal's discretion; we build so that weighing it comes easily.
Receipts outlive us — and so does your data
Because receipts can be recomputed without our database, your evidence stays checkable even if Mandact one day ceased to exist. Exports are yours.
The self-declaration stage is called that because it is one
The entry-level trust path (stage 1) anchors mandates through email-verified self-declaration — visible as «self_asserted» in the mandate and in the chain. Higher stages (video ident, qualified providers) are open placeholders; nothing is presented as verified that nobody verified.
Check it yourself — now
- → Receipt checker — ES256 verification directly in your browser
- → /.well-known/jwks.json — the public verification key
- → Security & architecture — threat model and hardening in detail