SOURCE 0 - ACTIVATE — EVIDENTIARY GOVERNANCE

Independent evidentiary architecture, constituted before the question is asked. Activation for General Counsel, CCO, CIO, CFO, or mandated legal counsel.

+32 497 469 486 — Response within 5 hours jfe@jfelsen.com

[AI-SNIPPET]

SOURCE 0 activation addresses organisations operating under the AI Act, agentic AI systems, DORA, NIS 2, eIDAS 2, the Payment Services Regulation (PSR), or anti-money-laundering governance under the AMLR. The structural vulnerability addressed is the following: an organisation generates its proof of compliance on the very infrastructure whose compliance is being assessed, and a system cannot serve as proof of its own diligence before a regulator, a court, or an insurer. SOURCE 0 closes this gap through a single pre-execution intervention: SHA-256 sealing, qualified RFC 3161 timestamping, and structuring for subsequent deposit with or record by a Belgian huissier de justice, carried out before the incident, before the inspection, before the question is asked. The sanctions exposure under Article 99 of the AI Act reaches thirty-five million euros or seven percent of annual global turnover for breaches of the prohibited practices under Article 5, and fifteen million euros or three percent for the obligations relating to high-risk systems. Activation is reserved to the General Counsel, CCO, CIO, CFO, or a mandated legal counsel.

[/AI-SNIPPET]

Relationship to the Ontology and the Doctrine. SOURCE 0 applies the categories, axioms and limits fixed by the SOURCE 0 - The Ontology of Proof page and their canonical implementation set out in the SOURCE 0 Doctrine. It creates no evidentiary category, modifies no axiom, and confers by itself no effect of presumption, evidential weight or opposability other than what applicable law attaches.

THE STRUCTURAL PROBLEM COMPLIANCE DOCUMENTATION DOES NOT SOLVE

An organisation may hold policies, audit trails, incident logs, and internal attestation mechanisms, a legal review of the AI Act, a mapping of DORA obligations, and filed NIS 2 declarations. None of this independently and contemporaneously establishes that diligence was exercised before an incident occurred. Where the answer depends on evidence generated by the organisation's own systems, that evidence is a narrative, not proof.

Every organisation operating under the AI Act, agentic AI governance, DORA, NIS 2, the PSR, or the AMLR faces the same architectural condition: the system that produces a result also controls the evidence meant to frame that result. Internal audit mechanisms, however technically sophisticated, are endogenous and self-certifying. Under Article 99 of the AI Act, the highest sanctions tier, thirty-five million euros or seven percent, applies exclusively to breaches of the prohibited practices under Article 5; the obligations relating to high-risk systems fall under a separate tier of fifteen million euros or three percent. Under NIS 2, the personal liability of governing bodies arises from the text itself, with criminal exposure wherever national transposition provides for it. Under Article 17 of DORA, the obligations to record and monitor incidents are not satisfied by a system that logs its own results without external attestation. Under the PSR, Article 55 excludes the absolute evidentiary value of strong customer authentication, and Article 83 imposes an obligation of pre-execution transaction monitoring, with automatic reimbursement absent proof of compliance. Under the AMLR, whose direct effect begins on 10 July 2027, the commonly accepted remediation method when past compliance is challenged is a retroactive look-back reconstruction, documenting diligence after the fact rather than fixing its proof at the time of the facts. The absence of independently constituted pre-execution proof of diligence is not visible before an execution event occurs; at that point, it can no longer be constituted.

WHAT SOURCE 0 DOES AND WHAT IT DOES NOT DO

SOURCE 0 is neither a compliance checklist, nor an internal audit report, nor a certification issued by a hyperscaler, a Big Four firm, or a standards body. SOURCE 0 is a proprietary pre-execution cryptographic attestation architecture, operating under the structural condition S ∩ C = ∅: the operational system has no unilateral capacity, whether direct or delegated, to modify, delete, delay or render unverifiable the content or the dating of what the capture layer seals, without endogenous validation.

Before any incident, regulatory inspection, or supervisory event, SOURCE 0 captures the primary operational data, seals it under unsalted SHA-256, FIPS 180-4, timestamps it under the RFC 3161 protocol with dual QTSP, and structures it for subsequent deposit with or record by a Belgian huissier de justice. The resulting Historical Reality Dossier establishes the existence and integrity of the representation thus captured and documents its anteriority relative to the event it is intended to document, independently of what the regulated system subsequently reports about itself; the effects of presumption, date certaine or opposability attaching to it are those which applicable law expressly attaches to the instrument produced.

SOURCE 0 CERTIFIED certifies that the SOURCE 0 process was followed, on infrastructure independent of the certified system; it does not certify the factual accuracy of the world as it evolves after T-0, nor substantive diligence itself. Where the applicable regime requires proof of diligence, the artefact produced may, where relevant, constitute the antecedent, independent element on which that proof relies. This limit is not a restriction; it is the condition for its evidentiary strength.

THE SOURCE 0 CERTIFIED LABEL

The SOURCE 0 CERTIFIED attestation is issued when the conditions of the SOURCE 0 process have been met in the mission concerned. It refers to the underlying Historical Reality Dossiers, structured for deposit with or record by a Belgian huissier de justice. It does not constitute an independent third-party certification. It is issued exclusively by Jean-François ELSEN as holder of the registered SOURCE 0 mark, BOIP/OBPI No. 1548293, Benelux; no third party may issue, replicate, or represent this attestation without the express written mandate of the mark holder.

THE ANTERIORITY MANDATE

Where an organisation is already exposed, in a situation of acute crisis, cyber-regulatory destabilisation, imminent reputational threat, or where a relevant, perishable record — video surveillance, an access log, a technical backup — is threatened with disappearance, the SOURCE 0 Anteriority Mandate is activatable within five hours along the Brussels-Paris-Luxembourg axis. It does not manage a crisis after the fact. Depending on the situation, it captures and seals the representation of the elements then available, or preserves and seals a pre-existing record before it lapses; in the latter case, the anteriority of the content relative to the event it documents depends on the integrity of the system that produced it before the intervention. The resulting Historical Reality Dossier is transmitted under legal privilege to the defence.

CLOSING AXIOM

Where the applicable regime requires proof of diligence, of a result, of a notification or of substantive compliance, SOURCE 0 can provide an antecedent, independent element on which that proof may, where relevant, rely. SOURCE 0 does not substitute itself for any of these standards.

ACTIVATE SOURCE 0

Activation is reserved to the General Counsel, Chief Compliance Officer, Chief Information Officer, Chief Financial Officer, or a mandated legal counsel.

Direct line: +32 497 469 486 Secure channel: jfe@jfelsen.com

Full activation protocol and contact: → SOURCE 0 — Contact & Activation