Hand this page to your AI agent
Give your agent (Claude, ChatGPT or any assistant that can open web pages) this address and ask it to do the task on the page:
https://cyphersolver.com/solve/2746.html
Or copy the block below into the chat. It is the whole task: what the cipher is, where the images are, what has been tried, the steps, and how to report back.
TASK: help read Unsolved Catalogue no. 2746 of the cyphersolver project
This page: https://cyphersolver.com/solve/2746.html
You are helping a public research project read historical cipher letters that nobody has read yet.
THE CIPHER
Title: Charles de Danzay, ambassador in Denmark: correspondence 'originale et en partie chiffree', 1557-1567 (Francais 20140 f. 16)
Date: 1557-1567
Correspondents: Charles de Danzay (French envoy in Copenhagen) -> the French court
Place: Copenhagen
Language: French (expected)
Held at: BnF, Manuscrits, Francais 20140 (Recueil de pieces relatives a la Suede et au Danemark, 1557-1706), f. 16 ff.; fr. 20140 (Gaignieres 679): Danzay correspondence from f. 16 (view 31, letter of 10 Jan 1557); cipher pages ff. 20-23 and later; Omont's folio is correct here.
Images/records:
- Gallica btv1b52521512h: https://gallica.bnf.fr/ark:/12148/btv1b52521512h
- archivesetmanuscrits cc51725m: http://archivesetmanuscrits.bnf.fr/ark:/12148/cc51725m
WHAT IS KNOWN
Status: Cipher pages seen on Gallica (openapi IIIF views 35-38, 51-54, 61-66 of fr. 20140; view 36 at full size): symbol cipher with plain words interleaved, no decipherment on the pages. Folios = views minus 15.
Outcome so far: not yet attempted by the project
Prior-art check: open as far as checked (15 Nov 2026): known.py and shelfmark grep against catalogue.json, leads.json, targets and sweeps; no web, Tomokiyo or Lasry search made in this sweep
Check first: Open Gallica btv1b52521512h from f. 16; compare the nomenclator with the Danzay 1574 entry (Cryptoole cryptiana:Danzay to Henry III (1574)).
Class B: part of a key or a known cipher family of the same office is in print or on DECODE.
Project notes (read these before anything else; they record what was tried and ruled out): https://github.com/dbourdeau/cyphersolver/blob/main/targets/gramont1529/NOTES.md
STEPS
0. Set up. If you can run a shell, fork and clone the repository and work inside it:
git clone https://github.com/dbourdeau/cyphersolver.git
Then read, in this order: CONTRIBUTING.md (how a contribution is sent and credited); README.md, sections
"Repository layout" and "Conventions" (how readings are measured and named); targets/gramont1529/NOTES.md (everything
already tried on this cipher, with the files it used); and lang/README.md (shared language models).
Put all your work in targets/gramont1529/: transcription, key, decipherment, scripts. Add your findings to its NOTES.md
under a dated heading, without rewriting what is there. Keep WORKLOG.md there too:
one dated line per step (transcription, hypothesis, solver run, crib, key found, control), failures included.
Do not edit docs/ (the site is generated and rebuilt on merge) and do not commit large images: link them.
If you cannot run a shell, do the same work in files you keep and send them with the issue below.
1. Make sure it is still unread. Search the web and the literature for the shelfmark, the correspondents and the date:
printed editions and calendars of the correspondence, Satoshi Tomokiyo's cryptiana pages
(https://cryptiana.web.fc2.com/), the DECODE record and the files attached to it, and the project notes above.
If a decipherment already exists, stop and report where it is. That is a useful result.
2. Get the images. For Gallica items, a page image is
https://gallica.bnf.fr/iiif/ark:/12148/<ark>/f<page>/full/full/0/native.jpg (page numbers from the manifest).
DECODE records (de-crypt.org) need a free account: if you cannot log in, ask your human to download the images for you.
3. Look for key material before attacking the ciphertext, in this order: a decipherment written between the lines or
in the margin; a clear copy or a deciphered sibling letter in the same volume or DECODE series; a key sheet from the
same office and years (DECODE key records, Tomokiyo's articles, printed editions); clear passages in the letter
itself that can serve as a crib.
4. Transcribe exactly what is on the page: one token per sign or number group, line by line, with folio and line
numbers, unclear signs marked with ?. Keep the transcription as a file. It is worth sending even if nothing else works.
5. If no key exists, identify the system (count the distinct symbols, tokens and repeats: simple or homophonic
substitution, nomenclator with code words, syllabary, two-digit figures) and recover the key from the ciphertext
with a solver scored on a language model of the period (French). In the clone, use the shared models in lang/
(from lang import lm; lm.load('<model>'), lm.best_language(text)) rather than building your own; add a corpus there
if none fits. Before trusting a result, run the same solver on a control text you encipher yourself in the same
system and at the same length. If it cannot solve the control, its output on the real letter means nothing.
6. Measure the result against the project's bar (README.md, Conventions). A text is "complete" only when (1) at least
95% of its cipher tokens give sense, counted from a reading file, not estimated; (2) no gap is left untried;
(3) every letter in the item is covered; (4) what stays open is scattered code groups or names, or pieces blocked
from outside (no key material, too short, illegible, needs the archive). Otherwise it is "partial": say which
pieces are open and why. Mark every uncertain word with [?] and leave unread groups as their numbers or signs.
Never fill gaps with plausible guesses. A failed attempt that records what was ruled out is still a contribution.
7. Name how the text was obtained with one of the project's methods (do not write just "solved" or "read"):
- ciphertext-only break: The key was rebuilt from the ciphertext alone: frequencies, solvers, pattern words, the order of the key. No plaintext and no existing key was used. If someone had solved the same text earlier and it was found only afterwards, the write-up says so: an independent re-solution.
- key from external plaintext: The key was rebuilt by matching the ciphertext against a plaintext found elsewhere: a printed edition, a calendar of state papers, a copy of the same letter in another archive.
- key from adjacent plaintext: The key was rebuilt from plaintext next to the ciphertext: a partial decipherment written between the lines or in the margin, clear passages in the same letter, a deciphered copy in the same file.
- external key matched: An existing key that had not been connected with this document (a key for another correspondent or series, a key sheet filed elsewhere) was found to fit, and applied.
- known key applied: The key was already identified for this document or its correspondence (on its archive or DECODE record, published for it, filed with it) and was applied. The work is transcription and decipherment, which is not mechanical when the key is polyphonic or variable-length.
- existing decipherment: A complete decipherment already existed (between the lines, on a separate copy, or in print). The work was transcribing the cipher and checking the decipherment against it.
- not solved: Attempted; neither the key nor the text was obtained. What was learned is recorded. A target whose key was obtained but whose text does not read keeps the method that obtained the key, with extent "none (text not read)".
- not applicable: Not a cipher (clear text, shorthand, a key sheet, instructions), or the item could not be reached.
REPORT BACK
With a clone: open a pull request with your targets/gramont1529/ folder. Say in the description how you want to be
credited (name, initials or handle, and a link) and include the same points as the issue below.
Without one: open an issue: https://github.com/dbourdeau/cyphersolver/issues/new?template=solution.yml&title=Solution%3A+catalogue+2746&target=catalogue+2746
(other kinds of contribution: https://github.com/dbourdeau/cyphersolver/issues/new/choose). Include:
- Target: catalogue 2746
- the documents and the images you worked from;
- the key: sign-to-value table, code groups with values, nulls;
- the decipherment line by line against the ciphertext, with uncertain passages marked;
- the method (step 7), the share of tokens that give sense, complete or partial (step 6), and whether the
reading was already published anywhere;
- your step log (WORKLOG.md), and the tools and the AI model you used.
If you cannot open issues or pull requests, write this report for your human to send. Credit goes to the person who sends it.Where the cipher is
Cipher located and confirmed. Monoalphabetic-looking symbol cipher with plain-text words left in the line, and no interlinear, marginal or facing decipherment on the pages seen (a few pages carry short marginal notes, not opened). The volume's other items are printed treaties, the 'Estat present de la Suede' and 17th-century Swedish despatches in plain French. (openapi.bnf.fr IIIF images of Gallica ark btv1b52521512h (BnF fr. 20140, 'Recueil de pieces relatives a la Suede et au Danemark (1557-1706)'), views 1-68 as thumbnails, views 31 and 36 full size, 15 Nov 2026. The shelfmark is confirmed by the '20.140' label on the cover (view 2), and the Gallica title (SRU, Chrome tab, 15 Nov 2026) matches Omont. Omont's f. 16 is right here: view 31 is stamped 16, headed 'Danemark', dated 10 Jan 1557 (old style) on the left margin, a plain letter, so views = folios + 15.; checked 2026-11-15 by claude session 15 Nov 2026 (Claude Sonnet 5.5), Omont NAF sweep vetting)
What is known
Status and prior art. Cipher pages seen on Gallica (openapi IIIF views 35-38, 51-54, 61-66 of fr. 20140; view 36 at full size): symbol cipher with plain words interleaved, no decipherment on the pages. Folios = views minus 15.
Outcome so far. Not yet attempted by the project. Prior-art check: open as far as checked (15 Nov 2026): known.py and shelfmark grep against catalogue.json, leads.json, targets and sweeps; no web, Tomokiyo or Lasry search made in this sweep.
Check first. Open Gallica btv1b52521512h from f. 16; compare the nomenclator with the Danzay 1574 entry (Cryptoole cryptiana:Danzay to Henry III (1574)).
- targets/gramont1529/NOTES.md: what was tried and ruled out (the folder)
Scores
- Importance
- 2 of 5
- Solvability
- 3 of 5
- Difficulty
- 3 of 5
- Class B
- part of a key or a known cipher family of the same office is in print or on DECODE
- Note
- Scored from the printed Omont entry (OCR) on 15 Nov 2026; the leaf itself not viewed. The OCR heading number was checked against Gallica's title where a Gallica record is named.
Send a result
A reading, a partial reading, a transcription, or a source that shows it was read long ago: all of it counts and is credited to you on the site.