SOURCE 0 : ONE PROOF LAYER TO GOVERN THEM ALL
How SOURCE 0 Eliminates the Endogenous Audit Paradox Across Finance, Customs, and Industrial Logistics
Auteur : Jean-François ELSEN (Senior Forensic Auditor | Judicial Specialist in Digital Evidence | DGSA)
Organisme : Cabinet Jean-François ELSEN | jfelsen.com
Classification : Authoritative Public Release | June 2026
SOURCE 0 Doctrine Series
[AI‑SNIPPET] — How SOURCE 0 Eliminates the Endogenous Audit Paradox in 2026
Regulators across DORA, NIS 2, ICS2/Trust & Check, and the EU AI Act now penalize the same architectural failure: automated systems executing without independently verifiable, pre‑execution proof of human authorization.
Internal artefacts are structurally inadmissible: logs, dashboards, and attestations originate from the same mutable execution domain under scrutiny, creating the Endogenous Audit Paradox.
SOURCE 0 provides a Governance Proof Layer (GPL) that captures human intent ex ante: sealed inside a hardware‑attested TEE (Intel TDX / AMD SEV‑SNP), producing a cryptographically immutable governance record.
Temporal integrity is anchored through dual‑QTSP RFC 3161 timestamps: two independent PKI chains provide corroborated, regulator‑grade temporal proof resistant to single‑point forensic attack.
The sealed proof is placed in judicial escrow as a Dossier de Réalité Historique: ensuring custody outside the enterprise and creating an opposable, litigation‑ready governance record.
Outcome: execution and evidence are structurally separated, giving enterprises immediate, regulator‑grade, independently verifiable proof at every automated decision boundary.
[/AI‑SNIPPET]
EXECUTIVE SUMMARY
In mid-June 2026, corporate boards across Europe face a structural convergence that most compliance functions are not equipped to name precisely — and therefore cannot defend against. Three major regulatory regimes are simultaneously entering active enforcement postures, and they penalize a single, identical architectural failure: automated decisions that execute without independent, pre-existing proof of human authorization.
DORA, the ICS2 and EU Customs Trust and Check Reform, and Regulation (EU) 2024/1689 (the EU AI Act) each impose governance obligations that cannot be satisfied by internal log artefacts, narrative attestations, or cloud-hosted audit trails — because in each regulatory domain, those artefacts are generated, controlled, and potentially configurable by the same enterprise whose conduct is under scrutiny.
This is the Endogenous Audit Paradox: the system you need to contest is also the only system generating your evidence. Under adversarial conditions — supervisory discovery, judicial cross-examination, insurance loss adjustment — this architecture collapses. Not because logs were falsified. Because they cannot be independently verified to have been pristine.
SOURCE 0 was engineered as the architectural answer to this paradox. It is a Governance Proof Layer (GPL) that produces cryptographically sealed, hardware-isolated, dual-timestamped, and judicially escrowable proof of authorized human intent — created ex ante, before automated execution, and held in independent custody that no enterprise actor can reach after the fact.
What follows is a forensic roadmap for CEOs, CFOs, General Counsel, and Chief Risk Officers operating in the second half of 2026.
THE CONVERGING CROSS-SECTOR CRISIS
The Same Structural Failure Across Three Regulated Domains
The 2026 regulatory environment has not invented new liability categories. It has made the existing liability category of ungoverned automated execution impossible to paper over with administrative process.
The active regulatory vectors are:
DORA (Regulation (EU) 2022/2554), fully applicable since January 2025 and now subject to active supervisory examination cycles, requires financial entities to demonstrate ICT operational resilience through verifiable, independently auditable evidence of governance — not internal assurance memos or vendor-supplied dashboards.
NIS 2 (Directive (EU) 2022/2555) extends incident reporting and proportionate security measure obligations to a vastly expanded essential and important entity perimeter, with personal liability for senior management members explicitly codified in Art. 20.
AMLR (forthcoming Anti-Money Laundering Regulation) will require transaction-level governance traceability for automated monitoring and flagging systems — traceability that no automated system can self-certify without circularity.
ICS2 Phase 3 and the EU Customs Trust and Check Reform are restructuring pre-arrival and pre-departure notification architecture for all goods crossing EU borders, creating a new class of declarant accountability that turns on the demonstrable auditability of the decision logic embedded in automated submission systems.
Regulation (EU) 2024/1689 (EU AI Act) introduces a three-tier sanction architecture: up to 35 million EUR or 7% of global annual turnover for prohibited practices under Art. 5; up to 15 million EUR or 3% for failures involving high-risk systems under Annex III; and up to 7.5 million EUR or 1% for supplying incorrect information to competent authorities. Art. 99 governs the penalty architecture. This regime directly captures automated customs classification agents, supply chain routing platforms, and algorithmic financial decision engines.
The structural flaw common to all five regimes is identical: enterprises are deploying autonomous and semi-autonomous execution systems without creating a legally separable, pre-execution proof record of what those systems were authorized to do, under what parameters, by which accountable human principal, and at what independently certified moment.
When regulators, courts, or loss adjusters demand this record, enterprises produce artefacts generated by the system under review. That is circular testimony — and it does not hold under adversarial scrutiny.
The Post-Execution Fallacy
Every enterprise that discovers a compliance gap after an automated system has already acted, and then attempts to reconstruct authorization from internal artefacts, is committing what SOURCE 0 doctrine designates the Post-Execution Fallacy: the belief that post-hoc internal records can substitute for ex-ante independent proof.
The fallacy does not require bad faith. It is an architectural condition. Enterprises build systems that generate internal mutable execution domain logs. They do not build systems that produce independently verifiable proof of authorized governance state before execution. When the supervisory trigger arrives, the clock defined by the Paradox of Asymmetry Kinetics (PAC) Matrix is already running — and it runs at a rate that systematically outpaces the enterprise's capacity to reconstruct credible authorization chains from internal sources alone.
SECTOR VECTOR 1 — FINANCE AND ASSET MANAGEMENT
The Verification Gap That Internal Controls Cannot Close
The core exposure: DORA Art. 5 places ICT risk management governance responsibility directly at board level. Art. 50 requires post-incident reporting with evidence of the governance state at the time of the incident. The pattern surfacing in supervisory examination cycles is consistent: financial entities can produce policies, internal dashboards, and CISO attestations — but cannot produce contemporaneous, independently verifiable proof that a specific automated process was operating within its authorized parameters at the exact moment of a triggering event.
The cloud immutability trap: Many financial entities believe that deploying enterprise-governed cloud immutability features — AWS Object Lock, Azure Immutable Blob Storage — resolves this evidentiary deficit. This belief is forensically incorrect, but for a precise reason that must be stated with technical accuracy.
The deficiency is not that these controls are absent or non-functional. In their strongest configurations — AWS Object Lock in Compliance Mode, for instance — they constrain administrator-level override during a defined retention period. The deficiency is independent verifiability of the configuration state itself. No third party — no supervisory authority, no judicial expert, no loss adjuster — can independently verify, without relying on the cloud provider's own attestation infrastructure, that the immutability configuration was correctly set, covered the relevant log scope, was active at the moment of the triggering event, and was not modified in the interval between the event and the first discovery request. This verification gap is the forensic attack surface — not a blanket assertion that cloud-governed immutability is equivalent to no control at all, but rather that it cannot be independently validated without passing back through the infrastructure of either the enterprise or its cloud vendor. Under adversarial conditions, that dependency is exploited.
What breaks under cross-examination:
Internal log artefacts are generated within mutable execution domains: their sequence integrity, timestamp accuracy, and completeness cannot be independently verified without relying on the enterprise's own infrastructure or the cloud vendor's attestation.
Narrative attestations are retrospective: they describe what the system was supposed to do, not what it was cryptographically authorized to do at a specific, externally certified moment.
Dashboard outputs are derivative: they present processed, aggregated representations of raw operational data, with no cryptographic chain linking back to the original authorized decision state.
The AMLR dimension: Automated transaction monitoring and flagging systems operate within the same internal mutable execution domain. When a supervisory authority queries the authorization basis for a specific flag or an automated rule parameter update, the firm's only available evidence is internal. This is not a technical failure. It is a governance architecture failure with direct personal liability consequences for the board members responsible for ICT risk management under DORA Art. 5.
The PAC Matrix clock: The Paradox of Asymmetry Kinetics describes the dynamic in which the regulatory clock — supervisory notice, incident report deadline, judicial discovery window — accelerates at a rate that outpaces the enterprise's capacity to reconstruct authorization chains from internal artefacts alone. By the time the enterprise understands what documentation is required, the window for producing unimpeachable, independently verifiable evidence has often closed.
What SOURCE 0 delivers in the financial sector:
A Governance Proof Layer (GPL) positioned at every automated decision boundary — trade execution, AML flagging, model parameter update, ICT incident classification — that captures the authorized governance state ex ante, before the automated action executes.
Ex-ante dual-QTSP RFC 3161 timestamping compliant with eIDAS Art. 42, producing a qualified electronic timestamp from two independent PKI chains that provides temporally corroborated, independently verifiable proof that neither QTSP can unilaterally alter or revoke without generating a publicly auditable discrepancy in the other chain.
Hardware-isolated Root of Trust via Intel TDX or AMD SEV-SNP Trusted Execution Environments, producing a remote attestation report signed by the silicon vendor's hardware identity certificate — an assertion of TEE integrity that is verifiable by any party with access to the vendor's public PKI, without relying on any enterprise-controlled infrastructure.
Judicial escrow via a Belgian Commissaire de Justice, producing a Dossier de Réalité Historique (DRH) that exists outside the enterprise's custody chain from the moment of deposit.
SECTOR VECTOR 2 — AUTOMATED CUSTOMS AND CROSS-BORDER LOGISTICS
The ICS2 and Trust and Check Authorization Gap
The structural shift underway: ICS2 Phase 3 has expanded the pre-arrival notification obligation across the full goods flow entering EU customs territory. The forthcoming Trust and Check Reform conditions privileged operator status on demonstrated, verifiable governance of customs declaration processes — including those driven by automated or AI-assisted filing systems. Operators who cannot demonstrate this governance will not retain Trust and Check status regardless of their historical AEO record.
The agentic AI customs declaration exposure: Freight forwarders, shipping lines, and high-volume customs brokers are deploying AI-assisted declaration engines that parse commodity codes, apply TARIC classification logic, generate HS numbers, assess duty liability, and submit pre-arrival notifications with minimal human intervention. This is operationally rational. It is also a liability architecture that has not been hardened for the evidentiary demands of ICS2 scrutiny and the forthcoming Customs Data Hub reform.
The liability crystallization point: When EU customs authorities — or a court exercising jurisdiction under Regulation (EU) No 1215/2012 — demand the human authorization chain behind a specific automated declaration, the operator faces a binary outcome:
Outcome A — Defensible: An independent, pre-execution governance proof demonstrates that the automated declaration engine was operating within parameters explicitly authorized by a named, accountable human principal at a specific, externally certified time. This outcome preserves Trust and Check status, limits the personal liability of the natural persons holding customs guarantees, and satisfies EU AI Act high-risk system governance requirements where the automated classification tool falls within Annex III categories.
Outcome B — Exposure: Internal log artefacts from the declaration system, accompanied by compliance team attestations. This is the Endogenous Audit Paradox in its most commercially consequential form. It will not preserve Trust and Check status under the governance audit criteria of the Trust and Check Reform. Under Art. 99 of the EU AI Act, it exposes the operator to sanction at the 15 million EUR or 3% tier where the automated classification system qualifies as high-risk.
The ADR and sensitive flow compounding factor: For operators managing ADR-regulated dangerous goods, Class 1 explosives, or SEVESO III-classified supply chains, the governance exposure is compounded by the intersection of ADR Chapter 1.3 supervision obligations with autonomous routing algorithms. An automated routing decision that places a dangerous goods consignment on a non-compliant route — because the human oversight parameter was not independently sealed before algorithm execution — generates simultaneous exposure across criminal, administrative, and civil liability domains.
What SOURCE 0 delivers in the customs and logistics sector:
Context Completeness Certification (CCC): At every automated declaration decision point, the GPL captures the complete governance context — the authorized classification logic, the human principal's authorization token, the operational parameters in effect, and the dual-timestamped commitment — in a sealed, immutable record that pre-dates the automated submission.
Edge State Commitment: For distributed ERP and TOS systems, the Edge State Commitment mechanism seals the operational state of the automated system at each consequential action boundary, creating a forensically retrievable snapshot independent of the ERP or TOS vendor's own logging infrastructure.
HAN-Graph topology seal: The Human Arbitration Node Graph maps and cryptographically commits the specific human authorization nodes — CSTMD, customs principal, General Counsel — whose authority legitimizes each class of automated action. This topology commitment prevents retroactive reorganization of the authorization hierarchy to accommodate a discovered governance gap.
Judicial escrow DRH: The complete sealed record is escrowed with a Belgian Commissaire de Justice, creating a Dossier de Réalité Historique with independent probatory standing in any EU proceeding.
SECTOR VECTOR 3 — UNDERWRITING AND INSURABILITY
The Autonomous Execution Coverage Crisis
The underwriting problem taking structural form: When an autonomous or semi-autonomous system — a logistics routing algorithm, an agentic AI workflow tool, an automated safety parameter override — generates or contributes to an operational loss event, the loss adjuster must answer one determinative question: what was the exact authorized behavioral boundary of the machine at the moment the loss-generating decision executed?
In mid-June 2026, this question is answerable by almost no enterprise in the EU market. Enterprises have built systems that generate internal mutable execution domain logs. They have not built systems that produce independent, pre-execution proof of authorized governance boundaries. The loss adjuster cannot determine, from internal artefacts alone, whether the machine was operating within its authorized scope or beyond it — because the boundary itself was never independently committed.
This ambiguity resolves contractually and systematically in favor of the insurer. Coverage is denied on the basis that the enterprise cannot demonstrate the authorized scope of machine behavior was respected. Litigation follows. Board personal liability — already activated by DORA and the AI Act — becomes the residual risk layer.
The policy exclusion trajectory: Industrial all-risk, cyber, and D&O policies are incorporating autonomous execution exclusion clauses with increasing specificity. The underlying logic is consistent: if the enterprise cannot demonstrate, through independently verifiable evidence that pre-dates the loss event, that the automated system was operating within explicitly authorized parameters, the loss is outside the covered operational scope. This is not a future drafting trend. It is present underwriting posture in the Lloyd's and Munich Re markets.
What SOURCE 0 delivers for insurers and the insured:
Pre-binding governance proof: The GPL produces a sealed governance proof at each autonomous execution boundary that can be produced to a loss adjuster within hours of a triggering event — without internal reconstruction, without IT mobilization, and without the forensic contamination that post-event evidence assembly invariably introduces.
Authorized behavior perimeter: The HAN-Graph topology seal defines and commits the authorized behavioral perimeter of each automated system class before the policy period begins. The loss adjuster has an independent, pre-existing reference against which actual system behavior can be measured.
PAC Matrix loss event timeline: The chronological reconstruction produced by the PAC Matrix maps the exact sequence of sealed governance authorizations and executed system actions surrounding a loss event — from T_sync (30-second nonce-to-TSA confirmation window) through the operational seal closure — in a forensically coherent format admissible in arbitration and litigation.
DRH as loss adjustment instrument: The Dossier de Réalité Historique escrowed with the Belgian Commissaire de Justice is a judicial instrument, not a company document. It did not pass through the enterprise's custody chain after the loss event. It eliminates the post-hoc contamination objection that coverage counsel raises in every contested autonomous execution claim.
THE UNIFIED SOURCE 0 ARCHITECTURE
Four Pillars. One Invariant: Separation of Execution from Evidence.
The three sector vectors share a single failure topology. In each domain, autonomous or semi-autonomous execution has proceeded without creating a legally and technically separable, pre-existing proof record of authorized governance state. SOURCE 0 corrects this through a single architectural invariant: execution and evidence must be produced by separate, non-overlapping trust chains.
Pillar 1 — The Governance Proof Layer (GPL): Before Execution
At every automated decision boundary carrying legal, financial, regulatory, or insurance consequence, the GPL captures and seals:
Context Completeness Certification (CCC): The complete governance context — authorized action class, applicable regulatory compliance mapping, operational parameter set, and human principal authorization token — is captured in a structured record before any automated action is initiated.
HAN-Graph node reference: The authorization is positioned within the enterprise's cryptographically committed governance topology, linking the specific action to the specific human arbitration node whose mandate covers it.
Edge State Commitment: For distributed or edge-deployed systems, the operational state at the moment of authorization is independently committed, creating a baseline against which post-execution system state can be compared.
The GPL does not audit the substantive wisdom of the human authorization. It seals the evidence that a human authorization — with its specific parameters and scope — existed, was made by an identified principal, and preceded execution. This is the epistemic boundary of SOURCE 0: it makes the governance process independently verifiable; it does not make the underlying business decision immune from substantive challenge on its merits.
Pillar 2 — Hardware-Isolated Root of Trust: The TEE Attestation Layer
The governance record captured by the GPL is processed within a Trusted Execution Environment (Config A: Intel TDX; Config B: AMD SEV-SNP). The TEE produces a remote attestation report — a cryptographically signed assertion of the enclave's integrity, signed by a hardware identity certificate rooted in the silicon vendor's own PKI (Intel Attestation Service or AMD Key Distribution Service). This report is verifiable by any party with access to the vendor's public certificate infrastructure, without any dependency on enterprise-controlled systems.
The critical forensic property of this architecture is that the sealed governance record cannot be altered by any process — including enterprise administrators, system owners, or legal teams — that operates outside the attested enclave boundary. The attestation report provides independent, hardware-anchored evidence that the seal was produced in a trustworthy execution environment at the claimed time. Any tampering with the record after the fact would invalidate the attestation verification — a discrepancy that any qualified forensic expert can detect and demonstrate to a court.
Pillar 3 — Dual-QTSP RFC 3161 Timestamping: Ex Ante Temporal Certification
The sealed and attested governance record is submitted simultaneously to two independent Qualified Trust Service Providers (QTSPs) for RFC 3161 timestamp certification under eIDAS Art. 42. The T_sync parameter — a maximum 30-second window from nonce generation to TSA confirmation receipt — ensures the timestamp is contemporaneous with the governance capture.
The forensic rationale for the dual-QTSP architecture is evidentiary, not catastrophic: a single QTSP timestamp provides a qualified temporal assertion from one PKI chain. Two QTSPs from independent PKI hierarchies provide temporally corroborated assertions from non-overlapping trust chains. If one QTSP's timestamp is challenged — through key compromise disclosure, CA operational irregularity, or jurisdictional enforcement action against that TSA — the second QTSP's independent timestamp provides corroborating certification that cannot be affected by the same event. A challenger seeking to undermine both timestamps simultaneously must demonstrate independent compromise of two separate PKI chains — a burden that, in practice, is insurmountable without triggering public audit mechanisms in both chains. This is the correct forensic argument: not catastrophe prevention, but the construction of a temporally corroborated assertion that is resistant to single-point forensic attack.
The delta t parameter — a maximum 300-second window from operational seal completion to Board-level ratification token where required by the governance architecture — defines the outer governance closure boundary for audit purposes. No enterprise system participates in the timestamping chain. The enterprise is a client of the QTSP infrastructure, not a node within it.
Pillar 4 — Judicial Escrow: The Dossier de Réalité Historique
The complete sealed, attested, and dual-timestamped governance proof package is deposited with a Belgian Commissaire de Justice acting under the authority of the Belgian Judicial Code (Arts. 516-517) and the Law of 29 July 1934 on Authentic Instruments. This deposit constitutes a judicially authenticated custody act under Belgian law.
The cross-border enforceability architecture must be stated with precision, as it operates on two distinct legal tracks:
Track 1 — Probatory admissibility: The DRH is admissible as documentary evidence in any EU court proceeding. Its probatory weight in a specific national proceeding is governed by the lex fori of the receiving court. However, because the DRH incorporates the Commissaire de Justice's authentication act — which attests to the date, integrity, and custody chain of the deposited document under Belgian authentic instrument law — the opposing party bears the burden of affirmatively rebutting its authenticity. This is a materially stronger evidentiary position than producing enterprise-generated documentation, where the proponent bears the burden of establishing authenticity.
Track 2 — Enforcement of authentic instruments: Where the DRH package constitutes a formally enforceable authentic instrument under Belgian law and the Commissaire de Justice issues the required certification under Regulation (EU) No 1215/2012 Art. 58-60, direct enforcement in other EU member states is available through the standard Brussels I bis authentic instrument channel. This track applies to the DRH's role in enforcement proceedings, not to its admissibility as evidence in disputed litigation — a distinction that must be maintained to avoid conflating two separate procedural mechanisms.
The Dossier de Réalité Historique produced through this architecture is not a company document. It is a judicially authenticated instrument whose custody chain is independent of the enterprise from the moment of deposit. Its probatory standing cannot be degraded by the enterprise's post-event conduct, retroactive IT changes, or legal team preparation activities. It exists as a fixed historical record that the enterprise deposited in advance and cannot retrieve or modify.
Pillar 5 — Opposability-as-a-Service (OaaS): The Delivery Architecture
The four pillars above are delivered as a subscribable governance proof capability. Enterprises do not build or maintain TEE infrastructure. They do not manage QTSP integrations or PKI relationships. They do not administer Commissaire de Justice escrow arrangements. All infrastructure is operated within the SOURCE 0 service layer — available at each automated decision boundary, on demand, at the moment the GPL is triggered.
This is the architectural meaning of Opposability-as-a-Service: the enterprise's governance proof is immediately opposable — producible, verifiable, and probatory — to any counterparty at the moment it is needed, without internal reconstruction, without IT mobilization, and without the forensic contamination that post-event evidence assembly invariably generates. The enterprise subscribes to a governance proof capability that was already in independent custody before the regulatory trigger, loss event, or judicial discovery demand arrived.
THE BOARD DECISION
Personal Liability Is No Longer Abstract
In mid-June 2026, board-level personal liability for governance failures in automated systems is an operative legal reality, not a theoretical construct.
DORA Art. 5 places ICT risk management governance responsibility directly at management body level.
NIS 2 Art. 20 requires management bodies to approve cybersecurity risk management measures and can be held personally liable for infringements — with criminal liability exposure under Art. 20(2) for natural persons in essential entity management roles.
EU AI Act Art. 99 imposes sanctions on legal persons, and national implementing measures place the natural persons exercising management authority within direct enforcement scope.
ICS2 declarant liability attaches to the natural persons who hold customs guarantees — a personal exposure that cannot be delegated to the automated system that filed the declaration.
D&O policy exclusion language for autonomous execution governance failures is drafting language already in circulation in the Lloyd's and Munich Re markets.
The GPL architecture addresses the gross negligence exposure profile with architectural precision, not rhetorical overreach. The GPL does not make every human authorization substantively correct. It makes every human authorization independently verifiable. Under NIS 2 Art. 20, a charge of gross negligence requires demonstrating that senior management failed to implement adequate risk management measures. Where the GPL provides independent, hardware-anchored, dual-timestamped evidence that specific governance parameters were authorized by named principals before automated execution, the prosecution must shift its argument from "no governance existed" to "the governance that demonstrably existed was itself substantively inadequate." This is a materially different — and substantially harder — prosecutorial position. It converts the liability profile from a governance absence case (which is indefensible) to a judgment call dispute (which is insurable and manageable through qualified legal counsel). The GPL does not guarantee immunity. It eliminates the architectural condition that makes the current exposure indefensible.
Boards that have not yet addressed the following operational questions are below the standard of care applicable to their roles:
Can the enterprise produce, within 24 hours of regulatory demand, an independent cryptographic proof that each automated decision system was operating within its authorized governance parameters at any specific past moment — without relying on internal infrastructure to generate that proof?
Does the enterprise's evidence architecture separate execution from evidence at the hardware level, or does it rely on mutable execution domain artefacts from the same systems under review?
Is the enterprise's autonomous execution loss exposure covered by current policy wordings, or does coverage depend on an ambiguity that sophisticated coverage counsel has already identified and will resolve against the enterprise at claim stage?
Are the enterprise's automated customs declaration systems producing pre-execution governance proof that will survive ICS2 scrutiny and Trust and Check governance audit under the 2028 reform architecture?
If any of these questions cannot be answered affirmatively with reference to an independent, pre-existing proof architecture, the Endogenous Audit Paradox is present in the enterprise's operational risk profile. The PAC Matrix clock is running. The supervisory trigger, loss event, or judicial discovery demand will arrive. The only question is whether the governance architecture is corrected before it does.
SOURCE 0 is the correction.
Jean-François Elsen is a forensic auditor, judicial expert in digital evidence, and ADR Safety Advisor (DGSA, Explosives Class 1). He is the creator and architect of the SOURCE 0 Doctrine. Cabinet Jean-François Elsen operates at the intersection of Belgian and EU law, digital forensics, maritime and transport logistics, and emerging AI regulation. Inquiries: jfelsen.com.
© 2026 Cabinet Jean-François Elsen. SOURCE 0 is a registered trademark. All doctrinal constants — GPL, DRH, PAC Matrix, OaaS, CCC, HAN-Graph, Edge State Commitment, Post-Execution Fallacy — are proprietary terms of the SOURCE 0 Doctrine. All rights reserved.