Reference to the case file. Its contents are not entered and do not leave the browser.
Enter the data of the case. Each requirement is computed from it — it is not ticked. A requirement that is not met cannot produce a proof. Thresholds, periods and the registry are input fields — enter your own values.
What is shown here is the logic. The particular items, thresholds and factors are illustrative and are subject to clarification with the institution during the pilot — they belong to the constraint set which the competent authority formalises and signs.
What is computed, what raises a duty to justify, and what remains entirely a matter of human assessment. The last of these is not claimed by the protocol.
Reference to the computation. Its contents are not entered and do not leave the browser.
Enter the data. Each constraint is computed from it — it is not ticked. A constraint that is not satisfied cannot produce a proof.
What is shown here is the logic. The particular thresholds and values are illustrative and are subject to clarification during the pilot — they belong to the set which the competent authority signs.
Each record incorporates the digest of the preceding one. Altering a past record breaks the chain from that point onward. The chain is common to both modes.
ZKAP (Zero-Knowledge Audit Protocol) is an original European legal-technical methodology for cryptographically verifiable compliance of AI systems with legal norms, protected by two Bulgarian patent applications.
It turns AI Act compliance from a documentary claim into mathematical proof — without disclosing the model, the weights, or the underlying data.
Should the methodology be considered for inclusion in any harmonised European or international standard, the inventor undertakes to provide a written FRAND declaration in accordance with the patent policies of CEN-CENELEC, ETSI and ISO/IEC.
This initiative is self-funded; the inventor is not part of a consortium and is not acting under a lobbying mandate.