Claims about a protocol are only as credible as their working implementation. This page is the proof-of-concept: bernardbolter.com, a single artist’s practice catalogued under this protocol since its build began in 2026.

Evidence

The corpus, as of the most recent full audit

217artworks published, all with server-rendered structured data

15documented series

2embedding models run across the corpus — CLIP and DINOv2

A live corpus feed, versioned and machine-readable, runs alongside the published works. CLIP and DINOv2 embeddings are computed across the corpus for similarity reasoning — one language-informed, one self-supervised, deliberately not collapsed into a single “similarity” score. No other individual artist site currently publishes anything comparable.

The July 9, 2026 corpus reading

The strongest evidence is a single dated event. An AI system was given access to the corpus alone — no access to the physical work, no conversation with the artist beforehand — and asked to read it. Reasoning across the corpus, it independently reconstructed the governing logic of a thirty-year practice: that one series compresses space, another compresses time, and the archive itself compresses an artistic life — three instances of the same operation at three different scales.

The artist confirmed this was a real insight into his own work that he had not fully arrived at despite living inside the practice for three decades.

That moment is the protocol’s actual proof of concept, and it resolves a question the protocol would otherwise have to answer with a promise rather than evidence: why would an individual artist do this expensive cataloguing work, when the stated payoff — reasoning across thousands of honest archives — is decades away? The honest answer is that the decade-scale claim already functions today, at a sample size of one. A sufficiently honest single archive gives its own artist a reading of their practice they could not yet have reached alone. That is not a promise about art history in general. It is a working result, dated and on the record.

The same audit found real bugs

The same audit that produced the July 9 reading also produced, in the same sitting, a list of real bugs in the live data: mislabeled fields, date mismatches, an unencoded filename, a missing license field, one inadvertent disclosure of private information.

This is included here deliberately. A protocol built around honest, audited records that hides its own errors would be a contradiction. Publishing the audit alongside the discovery is the same discipline the protocol asks of everyone using it, applied to itself. The privacy gap has since been closed with genuine field-level access control — see /schema/ and the updates log.

What this page is not

This is a record of one implementation at one point in time, not a claim that the protocol’s larger, decade-scale thesis is proven. See the white paper’s Open Questions, particularly the notes on adoption, the corpus’s self-selecting demographic, and the recognition-delay timeline the central hypothesis actually depends on.