Read further · read 99.9% · known key applied · partial

Cardinal Morosini to Rome, 1587–89

Thirty-five cipher enclosures of the papal nuncio and legate in France in one key (DECODE R18–R58 and R17). The key is the one Meister printed in 1906 as no. 40, which George Lasry identified from his statistical recovery of part of it; because the figures run together in units of one to three digits, the decryption is under-determined and was resolved with a language model of 16th-century Italian. All thirty-five decrypted end to end: the Estates of Blois, the murder of the Guises, Henri III’s march on Paris. Two sheets in a second key have their own page.

Date
1587–89
Read now
99.9% of the cipher tokens give sense
Write-up
morosini1588.html
Files
targets/morosini1588
Open gaps
needs the archive ×3hard to read on the scan ×2no key knowntoo short to break

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://dbourdeau.github.io/cyphersolver/further/morosini1588.html

Or copy the block below into the chat. It is the whole task: the reading, every open gap, what has been tried, the steps, and how to report back.

TASK: take a partial decipherment further: Cardinal Morosini to Rome, 1587–89
This page: https://dbourdeau.github.io/cyphersolver/further/morosini1588.html

You are helping a public research project finish reading historical cipher letters. This one is read in part:
the key works, but some pieces are still open. Your job is to close one or more of the open gaps below.

THE READING
  Write-up:   https://dbourdeau.github.io/cyphersolver/morosini1588.html (read it first: how the text was read, the key, the reading)
  Date:       1587–89
  Outcome:    known key applied · partial
  Read now:   99.9% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/morosini1588 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [illegible: needs a new source] R35: the stretch after "si" (202v l. 8) and the last line (203r l. 19) - blocker: illegible; a hole in the paper (seen on the image 23 Oct 2026) and damaged paper
  2. [no-key-material: needs a new source] short unread stretches inside the 35 readings, figures clear but no word parse fits or nothing written (openings, closings, the encipherer's slips, off-list or undotted codes such as R18 [162], R19 [16], R31 [191], R42 [266]) - blocker: no-key-material; every hole of all 35 records checked on the DECODE images by 23 Oct 2026 (r2m, r2p), about 100 filled, each remaining hole listed with its blocker in texts/_reread_log.md
  3. [illegible: needs a new source] holes under blots, paper holes, spread ink and show-through (R22 132r-133r, R28 142r/143v, R30 162r-162v, R31 173r-174v, R32 throughout, R33 190v/191r, R55 516r l. 16, R17 235r l. 5 and others in the logs) - blocker: illegible
  4. [too-short: needs a new source] holes of one to three figures (single letters, a lone 7 or 0) - blocker: too-short
  5. [needs-physical-access: needs a new source] Rome's decipherments of these ciphers (ASV Segr. Stato Francia 27, cited by Hübner 1870) - blocker: needs-physical-access; not imaged online
  6. [needs-physical-access: needs a new source] missing leaves (R46 between 382v and 383r, R47 after 385v; R17 233v and R22's last leaf not imaged) - blocker: needs-physical-access
  7. [needs-physical-access: needs a new source] item 22/29 - blocker: needs-physical-access; no DECODE record for it; not imaged, so its key is not known

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: all 36 enclosures R18-R58 opened; R23-R26, R50 identified as other material; R53/R54 in a second key (now morosini1589); R17 in Francia 18 found to be in this key
  [x] clear-pages: every record's DECODE "cleartext" images viewed (22 Oct 2026): covering letters in clear and address leaves, no decipherment; no interlinear glosses on the cipher pages
  [x] known-keys: Meister no. 40 (1587) and Lasry's DOC_3175 reconstruction applied; the same key read R17
  [x] print: Tempesti, Vita di Sisto V (1754) II books VI-XIII paraphrases many letters (used for names and sense only); Hübner, Sixte-Quint (1870) locates Rome's decipherments in Francia 27 (not imaged); no edition of the legation
  [x] retry: 22 Oct 2026, every record re-parsed word by word on the figures, doubtful figures checked on image crops (55 corrections from the images), readings aligned word by word with the figures; 23 Oct 2026 R27, R35, R51, R57 holes re-checked on the images and regraded (all read); 23 Oct 2026 (r2m, r2p) every hole of all 35 records checked on the images: about 100 filled, the rest each with a blocker

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/morosini1588/NOTES.md in full, and the
   key, transcription and reading files it names; lang/README.md (shared language models).
   Work in targets/morosini1588/. Add your findings to NOTES.md under a dated heading without rewriting what is there, and
   update the "## Remaining gaps" line of every gap you close. Keep WORKLOG.md there: one dated line per step
   (hypothesis, value tried, solver run, crib, control), failures included. Do not edit docs/ (the site is generated).
   If you cannot run a shell, fetch the files from the links above and keep your work in files you send with the issue.
1. Pick a gap. Start with the ones marked "doable now" (open-codes, not-attempted, left-open): the images and the key
   are online, so they need only work. A gap marked "needs a new source" (no-key-material, too-short, illegible,
   needs-physical-access) can be closed only by something new: a key
   or a deciphered sibling found elsewhere, a better image, a printed edition or calendar, a photograph from the archive.
   For those, search for that material first, and say where you looked even when you find nothing.
2. Start from the existing key and transcription in the folder. Do not rebuild the key from scratch, and do not
   re-read parts that are already read unless you find an error in them.
3. For a code group or sign value: list every place the group occurs, show how each reads with the value you propose,
   and say what still does not fit. For a passage: re-read it at the image and give the folio and line. For a missing
   letter or leaf: say where it is held and how it can be reached.
4. Measure again. Apply the key to the whole text, write the reading file, and count the share of cipher tokens that
   give sense (not an estimate). The reading is "complete" only when (1) at least 95% of its cipher tokens give sense;
   (2) no gap is left untried; (3) every letter in it is covered; (4) what stays open is scattered code groups or names,
   or pieces blocked from outside. Otherwise it stays "partial": say which gaps are still open and why.
5. Be honest. Mark every uncertain word with [?], leave unread groups as their numbers or signs, and never fill a gap
   with a plausible guess. A gap retried and still open, with what was ruled out, is worth reporting.

REPORT BACK
With a clone: open a pull request with your changes to targets/morosini1588/. Say in the description which gaps you worked on,
  the share read before and after, and how you want to be credited (name, initials or handle, and a link).
Without one: open an issue: https://github.com/dbourdeau/cyphersolver/issues/new?template=further-reading.yml&title=Further+reading%3A+morosini1588&page=morosini1588.html
  Give the write-up, the gap you worked on (its line in Remaining gaps, or the code group, folio and line), what you
  propose, the evidence (every occurrence, the images or sources), the share read before and after, your step log,
  and the tools and 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.

Open gaps

gold can be done now: the images and the key are online, it needs only work. grey needs a new source first: a key, a better scan, an edition or the archive.

Already tried

Send a result

One closed gap counts: a code group valued, a passage re-read, a key or clear copy found elsewhere. It is credited to you on the write-up.

Open a further-reading issueOther kinds of reportHow credit works← All partial readings