Data and reuse

Export atlas-public-v1.0, 2026-10-19: 9 records and 5 connections. I prepared these checksum-verified files with the team (the AI coding and research agents I direct) to build the Atlas.

How researchers represent the writing

A typed letter is a label for a shape, not a decoded sound.

Folio 66r: handwritten symbol groups arranged in lines, with additional signs in the left margin
Folio 66r. Notice the strokes, joins and gaps. Researchers must decide how to represent these in a computer file before counting them. This scan is context, not a marked alphabet key. Yale University, Beinecke Rare Book and Manuscript Library, MS 408. Public domain.

From ink to a searchable label

EVA is a modern system developed by Gabriel Landini and René Zandbergen with contributions from Jacques Guy. It records shapes without establishing pronunciation. EVA o does not mean anyone has established the sound “o”. Zandbergen’s explanation and illustrated alphabet tables show the shapes beside their codes.

The same shape can be grouped differently

EVA spellingCurrier codeTyped characters counted
inN2 in EVA; 1 in Currier
iinM3 in EVA; 1 in Currier

These are alternative modern encodings, not translations. Neither settles how many historical characters the writer intended. See the alphabet comparison, Table 1.

Why this matters for the results

Word length and symbol frequency depend on the chosen encoding and treatment of uncertain readings. A count that includes both alternative readings is not automatically a count of distinct marks on parchment. Read the named transcription and counting rules beside each result.

A familiar shape is a comparison, not an origin

Some forms resemble Latin letters or medieval abbreviations. Resemblance alone establishes neither ancestry nor meaning. The writing-system overview and abbreviation comparisons provide historical context, not a decoding key.

The reviewed symbol-origin inventory establishes no dated antecedent for a Voynich sign. This describes the reviewed sources, not proof that no antecedent exists. This guide does not reproduce those counts as a census of physical glyphs.

The full research record

Explore all 51 graded findings, tested hypotheses, scripts, results and rerun instructions at github.com/thisisntjon/voynich (code under MIT, text and results under CC BY 4.0).

Data credits

Every count of words or glyphs in these records is taken from published transcriptions of the manuscript, not from a new reading of the scans. They are in René Zandbergen's IVTFF 2.0 format, from voynich.nu:

  • ZL3b: the Zandbergen-Landini transliteration, the primary text used in these runs.
  • RF1b: a reference transliteration built from the GC and ZL transliterations.
  • IT2a: Takeshi Takahashi's transliteration, as included in Jorge Stolfi's 1999 interlinear file.

The Currier A and B labels and Currier's hand ids, and Lisa Fagin Davis's scribe (hand) attributions, are used as these files record them. In ZL a comma marks an uncertain space; the project parser reads it as a word break unless a run says otherwise. Plant-resemblance judgments and other prior work are credited on each record. I link these sources and do not redistribute them.

Inside the download

Files

FileWhat it holdsSizesha256
EVIDENCE-README.md How the published evidence files were prepared. 0.5 KB 4100716241703084dcd0dbdc3e3b68c6d04cf617ff46f623ee11a96d7f28abf6
README.md What the export contains, how it was made and how to reproduce it. 3.4 KB cd44de9dbf18a29c9a1543b60944515152000394d65b6435c1e6127f11509063
connections.csv Typed links between records, each with its basis. 1.1 KB 6212042a3f946d759d8e1f6629f3aa41392291777d38841c1b418d351230038d
coverage.csv The same coverage table as CSV. 20.1 KB ea5c1a994e0d29c13836e309509ae1268d7a5a14fa12a1bb2fd871f3fee9818e
coverage.json How every finding in the research record was handled: included, deferred or excluded. 28.5 KB 31b57ae72a89ad3f274f6a1a8f7dc37c361878bcca724bd70bd5a13a682b2284
public-evidence.json For every file a record cites: what was published and how, or why it stays private. 25.9 KB 2f86412bce36d95636e4f3e4e4b111b63df46760da09a847a886e2a64184c78c
records.csv The same records, one row each, for spreadsheets. 53.0 KB 33de9c336dab6f79ad5bc51b5530a0344a54925f4661a8a69ccaab2837da7355
records.json Every published record, in full. The atlas pages are built from this file. 64.3 KB 01dbcf57e440d478d8c56d50701dc99451d6bd096da4633840abcf5913be9c41
schema.json Field definitions for the records. 1.3 KB 18ae869c8a32108cb7e5034f2b1fb68ec96792e2a06d25c8cc6a066c12a52751
manifest.json Version, date, coverage, source revisions and the sha256 of every file. 13.4 KB b738ab762454b24fbdcc2943f0df1482dcb24d4bdfddae6cd85f58b69331ddc8
working-interpretation.json Dated working interpretation, alternatives, linked evidence IDs and source fingerprint. Not an additional finding. 5.1 KB 541db82a501a87faf7218af2be3f8459344cb92d3433a604af88c0fd463e824e

Evidence files

42 project files that the records cite, published whole, with local machine paths replaced, or as the cited lines only. public-evidence.json says which, and lists the references that stay private and why.

All 42 evidence files with checksums

Check a download

Compare a file's checksum with the table above. On macOS or Linux run shasum -a 256 records.json. On Windows PowerShell run Get-FileHash records.json.

shasum -a 256 records.json
# Windows PowerShell:
Get-FileHash records.json -Algorithm SHA256

Where the records come from

All graph findings inventoried from existing graph, not all experiments independently reviewed. Two findings included only as correction context.

Canonical sourceRevision (sha256)
upstream:workflow/FINDINGS-GRAPH.yaml1a362f3cf312ccf24c6d0d2fb6a3dd37deb7a66d2d6e61f1fc7dd942f8472172
upstream:workflow/FINDINGS-MAP.md48490bea38a296a988c7b2488d324d0364d275c7bbb73278d85a502d96b7e061
upstream:.inventory/registers/DECISIONS.md9b0f6a628e5390fa0928eff8cbdc770fe5fda4992953f99afcf55f5c417c1670
upstream:.inventory/registers/LEARNINGS.mdbc832156ffa27684265c55c53218ca4f3a6bb88d56a390a7ccbda1cf84414a1b
upstream:.inventory/registers/CLAIMS.mdd9e9bc473ef516f25c3a311fea9bb30fce3cf55da957c2eaf677d596a57470ba
upstream:AGENTS.md8b6390edf4810f3246c13c85ba8c485f0c99add0a39aaf91381ad8083a246fa1
upstream:workflow/PLAN.md705490cdd569b9750c2fabf3582cac01b1683d2572dd056988a7fd457205aba3
upstream:TEAM-HANDOFF.mdfbdbe80c18648341bd9091f702e99bab1b691997229c40eefddfbec80b94f608
upstream:workflow/research/working-theory-2026-10-19.md5296fa6372eb16482c89c01801c3cab3e1ac6a6375fcdcb3f3d5c25a3ccae05b

The README explains export preparation, public reproduction and private-source limits.