SOURCE 0 - PRE-EXECUTION EVIDENTIARY ARCHITECTURE
Proof of diligence, constituted before the question is asked.
[AI-SNIPPET]
SOURCE 0 is a proprietary pre-execution cryptographic attestation architecture, developed by Jean-François ELSEN, Senior Forensic Auditor and Judicial Specialist in Digital Evidence, based in Brussels–Charleroi, Belgium. It addresses a structural vulnerability facing organisations under the AI Act, DORA, NIS 2, and eIDAS 2: a system cannot serve as independent proof of its own compliance, because evidence generated and controlled by the same infrastructure it is meant to attest to carries no value once contested. SOURCE 0 closes this gap through deterministic SHA-256 hashing, dual RFC 3161-compliant qualified timestamping by two independent QTSPs, and judicial deposit before a huissier de justice belge establishing date certaine under Book 8 of the Belgian new Civil Code — satisfying the evidentiary condition S ∩ C = ∅ between the system under scrutiny and the record attesting to it. Author: Jean-François ELSEN.
[/AI-SNIPPET]
THE STRUCTURAL PROBLEM
An organisation can hold policies, audit trails, internal logs, and a complete legal mapping of its obligations under the AI Act, DORA, or NIS 2, and still be unable to demonstrate, once a regulator or a claimant asks, that diligence existed before the incident rather than after it. This is not a question of internal rigour. A record produced and held by the same party whose compliance is in question cannot, by construction, rule out the possibility that it was shaped to fit the claim once the dispute arose. Under Article 99 of the AI Act, the highest penalty tier reaches thirty-five million euros or seven percent of global annual turnover. The exposure is invisible until an enforcement event occurs — at which point it can no longer be closed.
WHAT SOURCE 0 IS, AND WHAT IT IS NOT
SOURCE 0 is not a compliance checklist, an internal audit report, or a certification issued by a hyperscaler, a Big Four firm, or a standards body. It is a pre-execution cryptographic attestation architecture, operating outside the perimeter of the system it certifies, with no intersection and no endogenous validation. It certifies that diligence was exercised, at the time it was required, on infrastructure independent of the certified system. It does not certify the ongoing factual accuracy of that system's behaviour afterward — that boundary is the condition of its legal force, not a limitation of it.
TWO WAYS TO ENGAGE
Request information. For organisations assessing whether SOURCE 0 fits their governance context, a written exchange by email is available without prior commitment. State your role, organisation, and the nature of your context; you will receive a direct, written response.
Secure channel: jfe@jfelsen.com
Activate SOURCE 0. For General Counsel, CCO, CIO, CFO, or mandated legal counsel ready to engage a diagnostic or a mandate, activation proceeds under a mutual Non-Disclosure Agreement. Emergency activation, the Anteriority Mandate, is reachable within five hours on the Brussels–Paris–Luxembourg axis.
Direct line: +32 497 469 486
Full activation protocol →
THE DOCTRINE
SOURCE 0 rests on a single thesis: the law does not require material truth, it requires proof of diligence. Explore the architecture, the vocabulary, and the legal grounding behind it.
SOURCE 0 Doctrine →
Pre-Execution Evidentiary Architecture →
SOURCE 0 Anteriority Mandate →
SOURCE 0 CERTIFIED →
CLOSING AXIOM
The law does not require material truth. It requires proof of diligence. SOURCE 0 seals that diligence.
REGULATORY NOTICE
This page is provided for general informational purposes and does not constitute legal advice. Organisations should consult qualified legal counsel to assess their specific obligations under Regulation (EU) 2024/1689 (the AI Act), Regulation (EU) 2022/2554 (DORA), Directive (EU) 2022/2555 (NIS 2), and Regulation (EU) No 910/2014 (eIDAS).