Core claim: You do not need to hand someone your source code to prove who wrote it, when, and that it has not been altered since — a cryptographic fingerprint of a change, chained to the fingerprints before and after it and anchored to an independent clock, carries that proof on its own, which means provenance evidence can be shared with an auditor, a buyer or the public without exposing a single line of the code itself.

“Proof” and “disclosure” are two different acts

The instinct, when someone asks “prove you wrote this,” is to open the repository and let them read it. That conflates two things that do not need to travel together: showing the content, and proving a fact about the content. A fact like “this exact file existed, attributed to this author, at this timestamp” can be proven with nothing more than a hash of that file — a short fingerprint that changes completely if a single byte does, and reveals nothing about the bytes it summarizes. Hand someone the fingerprint and the fact is provable; hand them nothing else and the content stays yours.

This is the design decision underneath an OLOBOLO evidence chain: every entry — a change being authored, a review decision, a test run, a release being sealed — is recorded as metadata only. Hashes, actor identity (human or AI agent), references, counts, timestamps. Source code, prompts, spec text, review comments and test output never enter the chain at all; they are not redacted afterward, they are simply never the input. A due-diligence data room built from the chain is, by construction, shareable under NDA without the NDA doing any of the real work — there is no proprietary content in the pack to leak in the first place.

The chain proves itself, and a clock outside it proves the rest

A fingerprint only proves something if nobody can quietly swap it out later, and if there is a trustworthy answer to “when.” OLOBOLO’s chain gets both from construction rather than from a promise. Each entry’s hash is computed from the entry before it, so the entries form an unbroken, tamper-evident sequence from the first commit forward: changing or removing anything upstream breaks every hash that follows it, which is why a diff of two exports is enough to catch a rewrite attempt rather than something a reviewer has to trust on faith. Anyone — not just OLOBOLO’s own tooling — can recompute the whole sequence with an independent, zero-dependency verifier and get a pass/fail answer with no account and no network call. The chain does not ask to be trusted; it asks to be recomputed.

The “when” comes from outside the chain entirely. Each sealed release’s chain head is anchored with an RFC 3161 timestamp from an independent time-stamping authority — the same protocol banks and patent offices use to prove a document existed at a given moment. The resulting receipt is verifiable with nothing more exotic than openssl ts -verify against the authority’s own certificate chain, so proving “this hash existed by this date” does not require believing OLOBOLO either. What this combination proves, precisely: that the recorded metadata existed, unchanged, at the anchored time, in an unbroken sequence back to genesis. What it does not prove: that what was recorded was true when someone typed it in — that half of the picture still comes from review gates and CI evidence feeding the chain, not from the chain’s cryptography. A credible evidence system says both halves out loud instead of only the flattering one.

Where “prove without showing” earns its keep

This distinction stops being an abstraction the first time someone actually asks the question. A counterparty’s technical due diligence wants to know the AI share of a codebase and how it was reviewed — they do not need, and usually are not allowed under your own confidentiality obligations, to read the code itself to get that answer; a chain export and a seal give them the figures, recomputable, without a data room full of source. A court exercising the disclosure mechanism article 2 describes under the Product Liability Directive (EU) 2024/2853 is asking “show us how this was built and controlled” — a request an evidence chain answers with metadata about the building and controlling, not with a source dump that turns a liability question into an IP exposure. An open-source maintainer defending a prior-art or originality claim can point to a hash that has been externally time-stamped since before the dispute existed, without publishing unreleased work to make the point. In every case, the same shape repeats: the question being asked is about the process, not the content, and proof of process should never require handing over content it was never about.

The code stays yours. The proof that you wrote it, when you wrote it, and that nobody has touched it since — that travels on its own, in a form anyone can check without asking you to be believed.

This follows the K2 template set by article 1, “Who wrote your code? The provenance gap in AI-built software”: if provenance evidence must be recorded at the moment of change to be worth anything, the same design that makes it trustworthy — hashes and metadata, chained and externally anchored — is also what makes it safe to share.

Sources

  • RFC 3161, “Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP)” — IETF: https://www.rfc-editor.org/rfc/rfc3161 (Proposed Standard; the timestamping protocol OLOBOLO’s external anchors use and that openssl ts -verify checks against).
  • in-toto Attestation Framework v1, Statement layer specification — in-toto project: https://github.com/in-toto/attestation/blob/main/spec/v1/statement.md (the statement format OLOBOLO’s provenance predicate is projected into, referenced in the chain format’s ATTESTATION.md).
  • RFC 8785, “JSON Canonicalization Scheme (JCS)” — IETF: https://www.rfc-editor.org/rfc/rfc8785 (the canonicalization basis for the chain’s hash inputs, per the published FORMAT.md).
  • Product Liability Directive (EU) 2024/2853 — EUR-Lex: https://eur-lex.europa.eu/eli/dir/2024/2853/oj (CELEX 32024L2853); applies to products placed on the market or put into service after 9 December 2026 (Art. 2(1)). The disclosure mechanism referenced above is discussed in more depth in article 2.
  • OLOBOLO chain format (FORMAT.md) and provenance attestation predicate (ATTESTATION.md) — the open-source reference implementation, cited as the primary specification of our own product’s metadata-only design and hashing scheme, not as third-party commentary about it.