SOURCE 0 - THE DETERMINATION THE META TRIAL CANNOT PRODUCE
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 · August 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]
A federal trial opened on August 18, 2026, before the U.S. District Court for the Northern District of California in Oakland, brought by a coalition of 29 state attorneys general against Meta Platforms. Testimony given on August 18 and 19, 2026 concerns what the company knew about under-13 users, alongside separate public reporting on Meta's age-detection and age-estimation technologies. The public record to date establishes testimony and internal-research claims about that knowledge; it does not, by itself, establish that no independently fixed, account-level record of any underlying detection process exists. SOURCE 0 QUALIFICATION SEAL is the architecture designed to close that specific class of gap: independently fixing, at the moment it is produced, the output of an individual qualification determination — without capturing the underlying source data used to produce it.
[/AI-SNIPPET]
I. THE TRIAL
On August 18, 2026, a federal trial opened before Judge Yvonne Gonzalez Rogers in Oakland, California, within a broader multidistrict litigation against social media companies. This specific proceeding is the first bellwether trial for a coalition of 29 states that jointly allege Meta violated the federal Children's Online Privacy Protection Act (COPPA) by collecting data from users under 13 without verifiable parental consent. California, Colorado, Kentucky, and New Jersey are the four states whose separate consumer-protection claims are being tried first, alongside the federal COPPA claims common to all 29. An eight-member jury sits in an advisory capacity; Judge Gonzalez Rogers retains final authority over liability and remedies. The trial is expected to run six to eight weeks.
II. FRAMING
This article takes no position on Meta's liability and offers no prediction of the verdict. The trial is ongoing at the time of writing; Meta denies the allegations. What the public record presently establishes is testimony and internal-research claims concerning Meta's detection and knowledge processes. It does not, by itself, establish that no independently fixed, account-level record exists documenting what a given detection system produced and when — nor does it establish that such a record does exist. The evidentiary problem this article identifies is structural, and it does not depend on which of those two possibilities turns out to be true in Meta's case specifically.
III. TESTIMONY AND THE STRUCTURE OF THE DEFENSE
According to press accounts of the August 18 and 19, 2026 hearings, the states' first witness, Arturo Béjar — a former Meta engineering director — characterized the company's posture toward under-13 accounts as "don't ask, don't tell," and testified that his own internal research had surfaced tens of thousands of suspected under-13 accounts, describing their presence as widely known inside the company. Meta's position, per the same accounts, is that the federal COPPA claim turns on whether Meta had the actual knowledge the statute requires — that it was collecting personal information from a user under 13 — rather than on the general existence of underage users on the platform or of an age-detection capability.
This configuration is not specific to Meta. It recurs, in one form or another, in any dispute where an organization maintains an internal detection or evaluation system whose output — produced at a given instant, for a given case — must later be reconstructed after the fact, through testimony, document production, or deposition, because it was never independently fixed at the moment it was produced.
This distinction matters because litigation discovery, however extensive, does not close this gap by itself. Discovery can compel a party to produce records that already exist. It cannot retroactively create an independently fixed, contemporaneous system determination that was never created in the first place. Where no such record was ever produced, discovery may reconstruct historical facts and system behavior — but it cannot recreate the original contemporaneous evidentiary object itself.
IV. THE MISSING LAYER: DETERMINATION, KNOWLEDGE, AND LEGAL DUTY
A detection system's output, an organization's awareness of that output, and the legal sufficiency of that awareness under a given statute are three distinct things, frequently collapsed into one another in both litigation and commentary.
At the first layer sits the system output itself: an account classified, at a given confidence level, at a given instant, as likely belonging to a user under a specified age. At the second layer sits organizational knowledge: whether, and how widely, that output was known within the organization. At the third layer sits legal sufficiency: whether that knowledge meets the standard a given statute — COPPA or another — requires to establish liability.
SOURCE 0 QUALIFICATION SEAL addresses the first layer. It does not, by itself, establish the second, and it does not establish the third at all. What it produces, subject to the provenance-binding requirement set out in Section VI, is an independently fixed record asserting that a specified determination was generated by a specified system at a specified time — not proof that the organization knew of it, and not proof of its legal significance.
V. WHAT SOURCE 0 QUALIFICATION SEAL WOULD HAVE SEALED
The architecture does not alter the detection system itself, nor the removal or downstream-handling policy that follows from its output — those decisions remain entirely the responsibility of the evaluated organization. What it seals, at the moment it is produced, is the determination record: a pseudonymized account identifier, the nature of the determination (detection, prediction, external verification), the declared identifier and version of the system that produced it, the result itself, and the timestamp of its production — never the underlying source data used to produce it. The declared system identifier and version travel with the record as descriptive metadata; they are distinct from the provenance-binding association addressed in Section VI, which is what turns that metadata into a verifiable evidentiary attribution rather than an unverified label.
What is sealed is not the truth of the underlying fact — not "this user is 12" — but the existence and integrity of a determination record: that a specified qualification system, at a specified version, produced a specified output for a specified pseudonymous subject at a specified time. This distinction matters: the seal does not adjudicate whether the determination was correct, only that it was made, by what, and when.
"Independently fixed" refers here to a specific, narrow form of independence: fixation performed by a mechanism and an evidentiary actor outside the operational control of the system whose output is being evidenced. It is not independence of capture — the client organization still configures what data feeds the qualification system — and it is not independence of source. Keeping these three forms of independence separate matters throughout this article, and the remainder of this section addresses only independence of fixation.
VI. WHAT SEALING DOES NOT ESTABLISH BY ITSELF
An intact, independently fixed record answers one question only: was this specific record altered after it was sealed. It does not, on its own, answer three further questions that any credible evidentiary architecture in this space has to confront.
Provenance asks whether the sealed record in fact originated from the system it claims to originate from, and at the version it claims. A hash and a timestamp establish that a record was not altered after sealing; they do not, without more, establish that the record was correctly attributed to a given system execution in the first place. A declared system identifier and version number, standing alone, are insufficient for this purpose. The protocol accordingly requires an explicit provenance-binding layer: a verifiable association between the sealed determination and the specific system execution that generated it, established before or at the moment of sealing, and not re-establishable or re-assertable after the fact by the party that controls the system.
Completeness asks whether every determination that should have entered the capture boundary in fact did. An architecture can be perfectly intact, perfectly independent in its fixation, and still be incomplete if the evaluated organization controls which events are routed into the capture boundary in the first place. A system capable of generating ten million determinations while only seven million enter the sealed record is not lying about the seven million it sealed — but the resulting record is, as a whole, incomplete, and nothing in the integrity of the seal itself reveals that gap.
Coverage asks whether the capture boundary in fact spans every system, account population, and event category the dispute concerns, or only a defined subset the client organization chose to include. This is the point already conceded in Section V: the organization retains control over what enters the capture boundary, and over the frequency and scope of capture. That concession is necessary and should not be softened — but it means completeness and coverage remain matters for audit and contractual specification, not properties the seal itself guarantees.
The integrity of a sealed record and the integrity of the capture boundary that feeds it are not the same property, and neither implies the other. None of this diminishes the value of independent fixation. It means the value claimed for it should be stated precisely: SOURCE 0 QUALIFICATION SEAL removes uncertainty about what a given sealed record contains and when it was sealed. Without additional provenance and coverage controls specified at implementation, it does not, by itself, remove uncertainty about whether every determination the underlying system actually produced was ever routed into that record at all.
VII. LIMITS
Sealing can only apply to determinations produced after it is implemented. It repairs nothing retroactively for events that occurred before its adoption — which means no architecture of this kind, however well designed, could have closed the evidentiary gap already built into a dispute like the one now underway in Oakland, concerning events several years in the past. This is not a design limitation specific to SOURCE 0 QUALIFICATION SEAL; it is a structural property inherent to any mechanism of independent contemporaneous fixation, which by definition cannot fix a record for an event that occurred before the mechanism existed. The value of the architecture is prospective: it changes the evidentiary dependency structure of any organization that adopts it from the day of adoption forward, by independently fixing its material determinations at the time they are produced — it does not change the evidentiary position of an organization already engaged in reconstructing past facts through testimony and document production.
CLOSING AXIOM
A system that detects without independent fixation does not thereby produce no evidence at all — it produces an evidentiary state that remains dependent on infrastructure operationally and evidentially controlled by the very party whose conduct the dispute concerns, and on the completeness of that party's own reconstruction, years later, of what it once produced.
REFERENCE NOTE
SOURCE 0© and its derivative designations, including SOURCE 0 QUALIFICATION SEAL, are proprietary designations of Jean-François ELSEN. This article constitutes an original doctrinal publication by the author. Substantial reproduction without attribution is prohibited.
REGULATORY NOTICE
This article has doctrinal and informational scope only. It does not constitute legal advice, a position on the outcome of the trial it discusses, or a factual allegation of the author's own against any party to the litigation. Facts concerning the referenced trial are reported as they appear in public hearing accounts as of the date of publication and remain, as such, not finally adjudicated.
FREQUENTLY ASKED QUESTIONS
Does the Meta trial prove that the platform violated COPPA?
No. The trial is ongoing at the time of publication, and Meta contests the allegations. Whether a violation occurred is a matter for the applicable statute and the trial court, not for this analysis.
How can an organization prove that a system detected a specific account at a specific date?
By independently fixing, at the moment it is produced, the determination record — result, system identifier, timestamp — separately from the system under evaluation, combined with provenance, completeness, and coverage controls appropriate to the use case. That is what SOURCE 0 QUALIFICATION SEAL is built to do.
Can after-the-fact testimony substitute for a dated technical record?
Testimony establishes what a person recalls observing or knowing; it does not, on its own, independently and verifiably fix what a system produced at a given instant. The two are not interchangeable.
Why not simply require organizations to preserve and produce their internal logs?
Log production depends on the completeness and integrity of the logs an organization has chosen to retain, and on its willingness to produce them once a dispute arises. Independent sealing fixes a verifiable record of the determination at the moment it occurs, before any dispute exists, which reduces — though does not eliminate — dependence on the evaluated organization's later retention and production decisions. It remains dependent on correct implementation, configuration, and scope at the time of sealing, addressed in Section VI.
Does sealing a determination prove that the organization knew about it?
No. A sealed determination provides an independently fixed record of what a specified system is asserted to have produced, for a specified subject, at a specified time — subject to the provenance-binding requirement described in Section VI. Whether the organization was aware of that output, and whether that awareness meets the legal standard a given statute requires, are separate questions the seal does not resolve.
Does sealing a pseudonymized account identifier avoid data minimisation obligations?
Not automatically. Whether a pseudonymized identifier remains personal data depends on the architecture, purpose, identifiability, and retention regime involved. SOURCE 0 QUALIFICATION SEAL is designed to minimize the evidentiary record by excluding the underlying source data from the sealed payload, but pseudonymization does not by itself render the resulting record non-personal.
Can't litigation discovery compel a company to produce this kind of record anyway?
Discovery can compel a party to produce records that already exist. It cannot retroactively create an independently fixed, contemporaneous system determination that was never produced in the first place — where none exists, discovery may reconstruct historical facts and system behavior, but it cannot recreate the original contemporaneous evidentiary object.
Does SOURCE 0 QUALIFICATION SEAL apply to qualifications other than age?
Yes. Age is the first documented use case, but the architecture applies to any individual qualification determination produced at scale by a system controlled by the evaluated organization — eligibility, status, risk classification.
→ SOURCE 0 - THE DETERMINATION THAT CHANGED SYSTEMS MID-CASE
