How an investigation team turned a USB drive into a verifiable case file, and why its lawyer could prove it alone, offline, eighteen months later.
The facts in this story are a reconstruction: the names, brands, companies and people are fictional. The mechanics, however, are real from end to end.
The USB drive
One Tuesday in March, an accountant, let us call her Inès, contacts the investigations desk of a European media outlet. She works for an industrial company we will call Vercor. She believes several public contracts were overpriced, and she has brought material to show it: a USB drive containing a little over four hundred files. Contracts, estimates, invoices, emails.
The team's first decision is not spectacular: it creates an investigation in the application and classifies it as 'protected source'. That label follows every document, note and link, and determines what each person can see.
The upload looks like a simple drag and drop. Beneath it, the KARL Core memory layer does less visible work: each file receives its fingerprint on arrival and is retained exactly as received, in write-once storage. A record is never rewritten; it can only be read. Three files trigger a duplicate alert: another newsroom team already holds them. Nobody is blocked, but everyone knows. That is exactly the kind of fact that otherwise emerges six months later.
The text is extracted, indexed and searchable with highlighted excerpts. Every search remains bounded by what the user is entitled to see, including totals.
Ninety-three claims
An investigation is not just documents. It rests on sentences. The team therefore writes factual claims, one by one: 'Vercor overcharged the Pasteur secondary school contract by €2.3 million.' Ninety-three in the end.
Each claim is linked to the relevant material through a qualified link: this item supports it, that one contradicts it, another provides context, another does not allow a conclusion. The link requires a written rationale and can cite the exact page and passage. A claim is never overwritten: if it is reworded, the previous version remains, along with the reason.
Then the application does what a highlighter cannot: it calculates. The coverage matrix examines every claim through its links and places it in a category: covered, partially covered, uncovered, contradicted. One Thursday evening, a row turns red: the internal memo on page 9 contradicts the overcharging claim for lot C. The claim's author and reviewer are notified within a minute. Nobody waits for the next day's conference.
What follows is ordinary journalism, and that is precisely the point: lot C is restructured, one claim is withdrawn, and two others are narrowed to what the material actually says.
Friday at four o'clock
Before publication, the checklist has only four lines, sources verified, contradictions resolved, review complete, right of reply respected, and it does not tick itself.
Vercor is contacted on a Friday at 4 pm. Its response arrives on Tuesday; it is added to the file and the right-of-reply line is checked with its date. The call to the former procurement director leaves no digital trace: it is recorded in the free-form journal with a name, a time and a summary. The newsroom lawyer challenges a claim that 'the executives knew', giving written reasons. The claim carries that status openly for four days, while a second source is found. The new wording is approved, and the approval identifies the exact version, word for word, that was validated.
A discreet rule watches over all this: a link's visibility never exceeds the classification of the item it points to. A public claim cannot expose, even indirectly, a document classified as a protected source.
The seal
The investigation is published. It finds its audience. The case file is sealed: the application exports the entire investigation as an Evidence Pack, the original items under their fingerprints, every version of every claim, the complete decision journal, the rules in force, and a manifest that inventories every byte. A small trust file, the root, is sent to the newsroom lawyer through a separate channel.
Then time passes.
Eighteen months later
Vercor sues the outlet for defamation. The argument on the other side is familiar: the documents were allegedly 'arranged', the exchanges 'reconstructed'.
The lawyer, let us call her Ms Rivas, has no account on the platform, no access to the media outlet's servers, and no need for a network. On a disconnected laptop, she opens a standalone tool, the Evidence Pack verifier. She gives it two things: the sealed case file and the trust root received separately.
The verifier takes nobody at their word. It rereads every file and recalculates every fingerprint. It checks the manifest, replays the chain of trust from the root, and verifies the seal. A single altered byte and the verdict would be unequivocal: tampered with. Here the verdict is the opposite: intact and authentic, up to the known trust horizon.
Two details matter in its report. First, the omissions register: the file itself declares that three items exist but are absent from it, material that could have identified Inès, together with their fingerprints. The newsroom does not ask anyone to believe there is 'nothing else'; it proves the scope of what it shows, and why the rest remains silent. Then there is the verdict's honesty: it attests to the integrity, provenance and scope of the capture. It does not say the content is true. That was the journalists' work, and the file shows how it was done.
What to take away
The KARL Core memory layer provides the structure: an append-only journal, write-once retention and a chain of trust. The client application provides the actions: classify, link, contradict, check and seal. Each action leaves a verifiable trace that can be proved without us.
That final phrase matters twice. 'Without us' means without a server, without an account, and, if necessary, even if StratoFoundry no longer exists. Evidence that depends on its maker is only a promise.
The application used throughout this story does not yet have a public name. It exists, it runs, and this story is not a mock-up. We will reveal it very soon, with everything you have just read, and the rest.