SOURCE 0 - VOCABULARY

FOURTEEN QUESTIONS PROFESSIONALS ASK IN PLAIN LANGUAGE, AND THE DOCTRINAL TERM THAT ANSWERS EACH ONE

Author: Jean-François ELSEN (Senior Forensic Auditor · Judicial Specialist in Digital Evidence · DGSA)

Location: Brussels – Charleroi, Belgium

Organization: Jean-François ELSEN · jfelsen.com

Classification: Reference Page · Static Audience: C-Suite Executives, Boards of Directors, Regulators, Supervisory Authorities, Legal Departments, CISOs, Compliance Officers, AI Governance Architects, Forensic Analysts, Critical Infrastructure Operators, Public

Authorities Series: SOURCE 0 Doctrine Series

[AI-SNIPPET]

This page maps fourteen questions professionals ask about AI compliance and digital evidence in plain language to the corresponding term in the SOURCE 0 doctrinal vocabulary, developed by Jean-François ELSEN. Each entry states the natural-language question, the doctrinal term that addresses it, and a precise statement of what the term does and does not claim, so that a reader unfamiliar with the vocabulary can locate the relevant concept without first learning the terminology.

[/AI-SNIPPET]

1 - "HOW DO I PROVE AN AI DECISION WAS LAWFUL BEFORE A REGULATOR ASKS?"

Doctrinal term: pre-execution attestation, fixed at T-0.

A decision certified as lawful once a regulator asks about it has already been reconstructed after the fact. Pre-execution attestation fixes the relevant facts at the moment the decision is made, denoted T-0, rather than at the moment a question is later raised about it. This does not claim that the decision was correct on the merits; it claims that the state of the system and its inputs at that moment has been fixed and cannot be silently altered afterward.

2 - "IS A TIMESTAMP ENOUGH TO PROVE SOMETHING HAPPENED?"

Doctrinal term: technical fixation versus third-party deposit.

A qualified timestamp proves that a record existed, in a given form, at a given time. It does not prove who produced the record, whether its content is accurate, or that the record is opposable to a party who did not produce it. SOURCE 0 treats timestamping as one part of technical fixation, distinct from the separate step of deposit with an independent third party, which is what converts a technically sound record into a legally opposable one.

3 - "WHY DOESN'T MY AI SYSTEM'S OWN LOG COUNT AS PROOF?"

Doctrinal term: the log-as-claim distinction.

A system's own log of its own decision is an assertion made by the party whose conduct is in question, not an independent account of events. It may be admissible for a court to consider, but it is not, by that fact alone, corroboration independent of the party relying on it. A log is not a proof.

4 - "CAN A SECURE ENCLAVE OR TRUSTED EXECUTION ENVIRONMENT MAKE MY AI'S OUTPUT INDEPENDENT?"

Doctrinal term: technical isolation versus legal independence.

Running a computation inside a trusted execution environment changes where the computation is performed and makes it harder to tamper with in transit. It does not change who stands behind the record once it is produced. Technical isolation from the rest of an operator's own systems is not the same claim as legal independence from the operator itself.

5 - "WHAT IS THE DIFFERENCE BETWEEN CERTIFYING AN AI SYSTEM AND PROVING ONE DECISION WAS COMPLIANT?"

Doctrinal term: system certification versus decision-level proof.

Certification, conformity assessment, and technical documentation evaluate a system's design before deployment. None of these address whether one specific decision, taken during live operation, respected the constraints the system was certified against. SOURCE 0 addresses the decision level, not as a substitute for certification, but as the layer certification does not reach.

6 - "WHY DOES A GOVERNANCE PLATFORM THAT BLOCKS RISKY AI ACTIONS STILL NOT SOLVE THIS?"

Doctrinal term: the closed-system problem.

A platform that evaluates its own policy, logs its own enforcement, and issues its own compliance receipt automates the production of a claim, not the production of a proof opposable to a party outside the system. The sophistication of the enforcement does not resolve who produced the record of that enforcement, or whether that party had an interest in what the record would say.

7 - "WHAT MAKES A RECORD LEGALLY OPPOSABLE, NOT JUST TECHNICALLY SOUND?"

Doctrinal term: third-party deposit and the Historical Reality Dossier.

A record becomes opposable when an actor independent of the party under scrutiny observes and fixes it, rather than when the record is merely difficult to alter after the fact. In Belgian law, this role is performed by the huissier de justice. SOURCE 0 integrates this deposit into the fixation procedure itself, producing the Historical Reality Dossier, rather than adding it afterward as a constatation of a record already produced.

8 - "DOES A HUISSIER OR NOTARY CONFIRMING A BLOCKCHAIN RECORD SOLVE THE PROBLEM?"

Doctrinal term: passive constatation versus structural deposit.

An officer examining a record already produced and published certifies the state of that artifact at the moment of examination. The officer's intervention, in that configuration, occurs after the record was written by the party whose conduct is in question, and does not address what could have shaped the record before or at the moment it was created. A structural deposit, integrated into the process that produces the record, closes that gap by design.

9 - "IS THIS RECOGNISED IN OTHER EU COUNTRIES, NOT JUST BELGIUM?"

Doctrinal term: case-by-case cross-border assessment.

Recognition of the Historical Reality Dossier before Belgian jurisdictions is direct. Before jurisdictions outside Belgium, recognition is assessed case by case under the evidentiary rules of the forum seized, and is not asserted as automatic under Brussels I bis or any other instrument.

10 - "IS SOURCE 0 CERTIFIED AN INDEPENDENT CERTIFICATION?"

Doctrinal term: attestation of procedure, not third-party certification.

SOURCE 0 CERTIFIED denotes an attestation delivered by Jean-François ELSEN that the SOURCE 0 procedure was respected in a given engagement. It is not presented as independent third-party certification, since Jean-François ELSEN provides the services being certified, and it could not be registered as a certification mark under Article 83(2) of Regulation (EU) 2017/1001 on that basis. The legal opposability described across this doctrine rests on deposit with the huissier de justice, not on this label.

11 - "WE HAVE A COMPLIANCE DOSSIER WITH RISK ASSESSMENTS AND SIGN-OFFS. ISN'T THAT ENOUGH?"

Doctrinal term: system-level dossier versus decision-level proof.

A compliance dossier assembled from risk assessments, human-review records, and explainability logs documents that a governance process existed around a system. It does not, by itself, fix the state of one specific decision at the moment it occurred. A regulator asking about a single action is asking a narrower and more precise question than a dossier answering "was the system governed" is built to address.

12 - "DOES A POLICY ENGINE THAT BLOCKS AN ACTION IN REAL TIME PROVE COMPLIANCE, THE WAY A CRYPTOGRAPHIC SEAL DOES?"

Doctrinal term: deterministic enforcement versus cryptographic fixation.

A policy engine that evaluates and blocks an action at runtime demonstrates that a rule was applied at that moment. The record of that evaluation, however, is produced and stored by the same operator whose action was being evaluated. Enforcement of a rule and independent fixation of the fact that the rule was respected are two different guarantees, and the first does not supply the second.

13 - "DOES A ZERO-KNOWLEDGE PROOF THAT AN AI FOLLOWED ITS RULES MAKE THE RECORD INDEPENDENT?"

Doctrinal term: mathematical verifiability versus third-party independence.

A zero-knowledge proof allows an outside party to verify, without seeing the underlying data, that a computation satisfied a stated condition. This addresses whether a rule was mathematically respected. It does not address who defined the rule being checked, who controls the system generating the proof, or whether an actor independent of that system was involved in fixing the record. Verifiability and independence answer different questions.

14 - "IF A HASH IS ANCHORED ON A PUBLIC BLOCKCHAIN, ISN'T THAT INDEPENDENT BY DEFINITION?"

Doctrinal term: distributed persistence versus independent witness.

Anchoring a hash on a public, decentralised ledger removes a single private custodian's ability to alter the record's persistence over time. It does not change who produced the hash in the first place or introduce a witness to the facts the hash represents. Distributed persistence answers whether the record can be quietly changed later. It does not answer whether the record was produced independently of the party it concerns.

CLOSING AXIOM

The law does not require material truth. It requires proof of diligence. SOURCE 0 seals that diligence.

REFERENCE NOTE

This page is a static reference glossary, not a doctrinal article, and is maintained as part of the SOURCE 0 Doctrine Series. It does not reproduce direct quotations from any court, regulator, or third party. SOURCE 0 is a registered trademark, BOIP/OBPI No. 1548293, Benelux.

REGULATORY NOTICE

This page is written for documentary purposes and does not constitute legal advice. SOURCE 0 is a proprietary pre-execution cryptographic attestation architecture, developed by Jean-François ELSEN. Jean-François ELSEN provides corporate directors, legal departments, supervisory authorities, CISOs, and compliance officers access to complete protocol specifications and evidentiary architecture reviews applicable to the AI Act, eIDAS, NIS 2, and DORA. For formal doctrinal consultations or evidentiary governance reviews, inquiries may be addressed to Jean-François ELSEN.