SOURCE 0 - THE LOG-AS-CLAIM PROBLEM

WHY AN AI SYSTEM'S OWN RECORD OF ITS DECISION IS NOT, BY ITSELF, LEGAL EVIDENCE

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: Authoritative Public Release · July 2026

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]

An AI system's own log of its own decision is, under Belgian law as under most European systems of evidence, a claim made by the party under scrutiny, not evidence independent of that party. Belgian civil procedure applies a principle of free evaluation of evidence, under which a judge may consider an electronic record, but the record must still demonstrate integrity, reliability, and traceability before it carries weight, and a system that produces, times, and stores its own record of its own conduct has not, by that act alone, satisfied the reliability that comes from an account independent of the party it concerns. A log is not a proof. This article sets out why a self-generated record occupies a different evidentiary position than a record fixed and deposited independently of the party whose conduct it documents, and what an organisation actually needs to produce when a regulator or a court asks not what the system did, but how it can be sure.

[/AI-SNIPPET]

1 - THE CLAIM A LOG MAKES, AND THE CLAIM IT CANNOT MAKE

An AI system that logs its own decisions makes one claim reliably: that at a given moment, its own internal process produced a given output, under a given configuration, and that the record of this event has not been altered since it was written. This is a claim about the system's own account of itself. It is not, without more, a claim that a court or a regulator is obliged to accept as an independent account of what occurred. The distinction matters because the two claims are routinely presented as interchangeable, and they are not: a log demonstrates internal consistency, not external corroboration.

Belgian civil procedure does not exclude electronic records from consideration. Under the principle of free evaluation of evidence, a judge may weigh an electronic log alongside any other element of proof. But free evaluation is not automatic acceptance. The judge must still be satisfied that the record is tamper-proof, that the logging system operates with sufficient guarantees of its own accuracy, and that the record traces specific inputs to specific outputs in a way that can be checked. A log that meets these three conditions is admissible. Admissible is not the same as decisive, and a log produced entirely within the operator's own infrastructure, however well it meets these three conditions technically, remains the operator's own account, offered by the party whose conduct is in question.

2 - WHY A SELF-GENERATED RECORD REMAINS A CLAIM

The reasoning is structural, not a matter of degree of technical sophistication. A record's evidentiary weight depends in part on who is positioned to have altered it, and when. A hash function, an append-only store, or a trusted execution environment can make a record extremely difficult to alter after it is written. None of these mechanisms address a different question: whether the party that wrote the record had, at the moment of writing, an interest in what the record would say. An operator logging its own AI system's decisions is, by definition, the party whose compliance the log is meant to demonstrate. The technical guarantee of non-alteration after the fact does not resolve the question of what happened, or could have happened, before or at the moment of writing.

This is why legal commentary on AI audit trails has begun drawing an explicit distinction between logs as claims and logs as evidence: a machine-generated record states what a system says it did, and a court, an auditor, or a regulator is entitled to treat that statement as an assertion requiring independent corroboration, not as a self-authenticating fact. The distinction is not adversarial toward the technology. It is the same distinction the law has always drawn between a party's own business records and the report of an officer with no stake in the outcome. Treating a system's own output as self-sufficient once produced, rather than as a claim requiring independent corroboration before it is relied upon, is the same structural error regardless of the setting in which the output is used: the party relying on it remains exposed for having accepted its own system's account without a witness independent of that system.

3 - WHAT CONVERTS A CLAIM INTO EVIDENCE

Converting a claim into evidence with independent standing requires an actor outside the system whose conduct is at issue. In Belgian practice, this role is performed by the huissier de justice, a ministerial officer authorised to produce findings that a court accepts without requiring further proof of their accuracy. A huissier does not endorse the content of what is observed; the officer's function is to observe and record independently of the party being observed, which is precisely the element a self-generated log cannot supply about itself.

The distinction between a passive constatation performed after a record already exists and a structural deposit integrated into the process that produces the record in the first place is not a technicality. A finding made on a log already produced by the party under scrutiny still rests on that party's own account of the moment the log was created; the independent officer certifies the state of an artifact, not the absence of interest in its content at the moment it was written. A structural deposit, occurring as part of the fixation itself, removes that gap by design rather than addressing it after the fact.

4 - WHERE SOURCE 0 IS POSITIONED

SOURCE 0, the pre-execution cryptographic attestation architecture authored by Jean-François ELSEN, is built to close this specific gap rather than to improve the technical guarantees already available around self-generated logs. Primary data is sealed at T-0, under the structural condition S ∩ C = ∅, such that the capture layer is not reachable by the operator of the system being observed. This fixation is then carried through judicial deposit with a Belgian huissier de justice as part of the procedure itself, producing a Historical Reality Dossier whose evidentiary standing does not rest on the operator's own account of its conduct.

This is not presented as a claim that SOURCE 0 replaces the technical mechanisms discussed in this corpus — qualified timestamping, hashing, tamper-evident storage all remain relevant to the integrity of the underlying data. SOURCE 0 addresses the separate question of whether the record, once produced, is opposable to a party who was not involved in producing it. Recognition of the Historical Reality Dossier beyond Belgian jurisdiction is assessed case by case and is not asserted as automatic under Brussels I bis or any other instrument. 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 independent standing described in this article rests on the deposit with the huissier de justice, not on the label itself.

CONCLUSION

A log is not a proof. An AI system's own record of its own decision, however cryptographically sound, remains an assertion made by the party whose conduct is in question, admissible for a court's consideration under Belgian free evaluation of evidence but not, by that fact alone, independent corroboration of what occurred. Converting that record into evidence with independent standing requires an actor outside the system, positioned before or at the moment of fixation rather than after it. Organisations that treat a system's own log as self-sufficient before a regulator remain exposed for the same structural reason a party is exposed for relying, unverified, on its own account of events before a court.

CLOSING AXIOM

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

REFERENCE NOTE

This article discusses the general principle of free evaluation of evidence under Belgian civil procedure and the requirements of integrity, reliability, and traceability applied to electronic records, together with the statutory role of the huissier de justice under Belgian law and Book 8 of the Belgian new Civil Code. The article does not reproduce direct quotations from any court or disciplinary body; all positions are stated in paraphrase. SOURCE 0 is a registered trademark, BOIP/OBPI No. 1548293, Benelux.

REGULATORY NOTICE

This article 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.