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/2886.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. 2886 of the cyphersolver project
This page: https://cyphersolver.com/solve/2886.html
You are helping a public research project read historical cipher letters that nobody has read yet.
THE CIPHER
Title: Two lines of cipher signs on the title page of a copy of ad-Dani's at-Taisir, by the scribe Abu Sa'id ibn Humaid (Hamid) ash-Shafi'i al-Muqri' (Berlin, Ms. or. oct. 3629)
Date: 21 Rabi' II 615 AH / 17 Jul 1217 (date of the copy; Sellheim dates the cipher lines '615/1217 ?')
Correspondents: scribe Abu Sa'id ibn Humaid (Hamid) ash-Shafi'i al-Muqri' (attribution by Sellheim: 'wohl'); no addressee
Place: unknown
Language: Arabic (presumed from the Arabic manuscript; not established) (expected)
Held at: Staatsbibliothek zu Berlin, Orientabteilung, Ms. or. oct. 3629 (acc. 1933.30; 'Ahlwardt vor 579'), f. 1a and margin of f. 72b; Sellheim, VOHD XVII A 1 (1976) no. 12; f. 1a, between the title and the author's name: 2 lines, '43(?) Buchstaben in Geheimschrift', partly smudged; 7 of them repeated in the margin of f. 72b. Printed facsimile of the two lines: Sellheim, Tafel 55, Abb. 69.
Images/records:
- Sellheim 1976, Tafel 55 (Abb. 69), SBB digital: https://digital.staatsbibliothek-berlin.de/werkansicht?PPN=PPN1879946874&PHYSID=PHYS_0461
- Sellheim 1976, p. 23 (description of no. 12), SBB digital: https://digital.staatsbibliothek-berlin.de/werkansicht?PPN=PPN1879946874&PHYSID=PHYS_0051
- Plate image, full size (IIIF): https://content.staatsbibliothek-berlin.de/dc/PPN1879946874-00000461/full/full/0/default.jpg
WHAT IS KNOWN
Status: Sellheim (1976) p. 23: 'zwischen Titel und Verfasserangabe die beiden Zeilen mit 43(?) Buchstaben in Geheimschrift ... (zum Teil verwischt) und von denen sieben am Rande von Bl. 72b wiederholt sind (s. unten S. 177, sowie Abb. 69 u. 92)'; he gives no reading. Plate caption: '69. Geheimschrift, 615/1217 ? (s. S. 23 u. Abb. 92)'. Seen on the plate at full size: two lines of about 20 separate signs each, several looking like numerals with dots, bare, above the Arabic author line. Sellheim points for comparison to an abjad numeral cipher of c. 1800 in Ms. or. oct. 3938 (Abb. 92), which is written out in clear above its cipher. Not on DECODE.
Outcome so far: not yet attempted by the project
Prior-art check: open as far as checked (15 Nov 2026): Sellheim 1976 describes and reproduces it without a reading; web searches on the shelfmark and on Sellheim's plate found no decipherment; Cryptiana and Lasry's key list have no Arabic-script items; not on DECODE. Not opened: Ullmann 1972, Wuestenfeld 1879.
Check first: View f. 1a and f. 72b of Ms. or. oct. 3629 on Qalamos / SBB (not reachable from this network) to get a clean count of the signs; test the abjad numeral cipher of Sellheim Abb. 92 and Wuestenfeld, 'Ueber eine arabische Geheimschrift' (Nachrichten Goettingen 1879); check M. Ullmann, Natur- und Geheimwissenschaften im Islam (1972), the pages on secret alphabets that Sellheim cites.
Class B: part of a key or a known cipher family of the same office is in print or on DECODE.
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); and
lang/README.md (shared language models).
Put all your work in targets/<writer><year>/ (a new folder, e.g. sega1593): transcription, key, decipherment, scripts. Write a NOTES.md that says
what the document is, the system, the key, the reading, and what is open and why. 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 (Arabic (presumed from the Arabic manuscript; not established)). 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/<writer><year>/ 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+2886&target=catalogue+2886
(other kinds of contribution: https://github.com/dbourdeau/cyphersolver/issues/new/choose). Include:
- Target: catalogue 2886
- 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. Two lines of separate, unjoined signs, several resembling numerals or letters with one to three dots, each line closed by a group of dots; they stand above the Arabic author line 'ta'lif ash-shaikh al-imam al-hafiz Abi 'Amr 'Uthman ibn Sa'id ... ad-Dani'. No decipherment is written on the plate, and Sellheim's description (p. 23) calls them Geheimschrift and gives no reading. (Sellheim, Materialien zur arabischen Literaturgeschichte I (VOHD XVII A 1, Wiesbaden 1976), Tafel 55, Abb. 69, on digital.staatsbibliothek-berlin.de (PPN1879946874, image 461), downloaded at the host's full size 2307 x 3264 px; the figure cropped and enlarged; checked 2026-11-15 by claude session 15 Nov 2026, Arabic sweep part B)
What is known
Status and prior art. Sellheim (1976) p. 23: 'zwischen Titel und Verfasserangabe die beiden Zeilen mit 43(?) Buchstaben in Geheimschrift ... (zum Teil verwischt) und von denen sieben am Rande von Bl. 72b wiederholt sind (s. unten S. 177, sowie Abb. 69 u. 92)'; he gives no reading. Plate caption: '69. Geheimschrift, 615/1217 ? (s. S. 23 u. Abb. 92)'. Seen on the plate at full size: two lines of about 20 separate signs each, several looking like numerals with dots, bare, above the Arabic author line. Sellheim points for comparison to an abjad numeral cipher of c. 1800 in Ms. or. oct. 3938 (Abb. 92), which is written out in clear above its cipher. Not on DECODE.
Outcome so far. Not yet attempted by the project. Prior-art check: open as far as checked (15 Nov 2026): Sellheim 1976 describes and reproduces it without a reading; web searches on the shelfmark and on Sellheim's plate found no decipherment; Cryptiana and Lasry's key list have no Arabic-script items; not on DECODE. Not opened: Ullmann 1972, Wuestenfeld 1879..
Check first. View f. 1a and f. 72b of Ms. or. oct. 3629 on Qalamos / SBB (not reachable from this network) to get a clean count of the signs; test the abjad numeral cipher of Sellheim Abb. 92 and Wuestenfeld, 'Ueber eine arabische Geheimschrift' (Nachrichten Goettingen 1879); check M. Ullmann, Natur- und Geheimwissenschaften im Islam (1972), the pages on secret alphabets that Sellheim cites.
Scores
- Importance
- 3 of 5
- Solvability
- 2 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 Sellheim's description and his plate, viewed at full size during the Arabic sweep part B, 15 Nov 2026 (research/sweep_2026-11-15_arabic/); the manuscript itself not viewed (Qalamos unreachable from this network)
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.