Scipion de Fiesque at the Emperor’s court, 1567–69

TASK: take a partial decipherment further: Scipion de Fiesque at the Emperor’s court, 1567–69
This page: https://dbourdeau.github.io/cyphersolver/further/fiesque1567.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/fiesque1567.html (read it first: how the text was read, the key, the reading)
  Date:       1567–69
  Outcome:    known key applied · partial
  Read now:   81.0% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/fiesque1567 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [no-key-material: needs a new source] View 6 right (11 Oct 1567) c05-c06, two words, and about ten [?] words on that page - blocker: no-key-material; transcribed and checked sign by sign on native crops 23 Oct; the groups give no word under the key and no decipherment or print of this letter exists
  2. [no-key-material: needs a new source] View 23 left (15 Nov 1567): the bearer's name (9 signs) and about 17 signs before "court" - blocker: no-key-material; decoded 23 Oct; a name not in the key, and the contemporary decipherment abridges and is cramped there
  3. [no-key-material: needs a new source] Phrase holes left after the round-2 image checks: f. 79v c01-c03, f. 80 c01, c08 (17 Jul 1568); f. 100r c18 end, three words in c24-c26 (4 Sep 1568); v038l c17 subject (15 Feb 1568); f. 39r c08, c22-c23 end, c29 verb (6 Mar 1568); v150l [?conclurre], [?cest] (10 Sep 1569) - blocker: no-key-material; each checked on native crops (round-2 sections of read/_reread_log.md); no contemporary decipherment, clear copy or print exists for these letters
  4. [no-key-material: needs a new source] Single-word holes left in the 17 letters after the r2m pass (90 bracketed places, from 161; each listed with its figures in the r2m section of read/_reread_log.md): groups that give no word under the key (e.g. 11 Oct 1567 view 8 left c21 "et que […] bagues", 27 Mar 1568 the seven signs at the end of the clear line, 4 Sep 1568 view 110 right line 5 after "le seigneur Ernest"), struck or unwritten words (14 Aug 1568 "devers […]"), and words that rest on a look-alike the figures do not settle ([?fort], [?bon escient], [?soubz], [?poinct], [?pouviez]) - blocker: no-key-material; checked on native crops 23 Oct 2026 (r2m); no contemporary decipherment, clear copy or print of these letters, and the look-alike and code-sign values cannot be settled without one
  5. [illegible: needs a new source] Margin decipherments, cramped words: 4 Jun 1568 [?presenté], 21 Aug 1568 "[…]nt" and [?l'on tient pour seur], 6 Nov 1568 [?a assemblé] - blocker: illegible; re-read on native crops 23 Oct 2026, the margin hand is cramped or overwritten at these places and the decode is broken there too
  6. [no-key-material: needs a new source] Lone signs standing as codes, values not settled: ϖ (l'Empereur or le Roy), ∞ alone, =ii, pp/ꝥ (the King of Spain by sense), H# alone, the group ffx-3y, the arrow, "lele"; 16 = ce or vostre - blocker: no-key-material; not in Tomokiyo's table, read from context; key.tsv unchanged (Dz = con now settled)

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: all 183 views were looked through by the contributor; here views 22, 23 and 99 opened, and view 23 left found untranscribed; 23 Oct views 5, 9, 21, 24 checked for a decipherment of views 6 and 23 left (none)
  [x] clear-pages: view 23 right is the contemporary decipherment of views 22 right and 23 left (read in full 22 Oct); the margins of views 65, 103 and 125 right decipher those letters, view 37 right's its two lines (read 22 Oct); no other cipher view has a margin decipherment (contact sheet of all 34)
  [x] known-keys: Tomokiyo's reconstructed table for this volume is the key; no other key of Fiesque's embassy is known
  [x] print: La Ferrière, Lettres de Catherine de Médicis iii (Catherine's replies only), Cryptiana, DECODE and the contributor's prior-work list; nothing printed of Fiesque's cipher
  [x] key-rebuild: contributor inferred 23 values from context; the calibration shows one code (Φ) mis-valued in one place; 23 Oct Dz valued con from eleven words in five letters
  [x] retry: the whole volume decoded again here with the contributed key and scored (measure.py); 22 Oct every letter built into sentences from the decode, with image checks on views 6, 37, 109, 159; 23 Oct (round 2) views 6 right and 23 left transcribed, and the phrase holes of ff. 39r, 79v-80, 100r and views 38 left, 150 left re-read on native-resolution crops; 23 Oct (r2m) the single-word holes of the other 17 letters re-read on native crops of 24 views (161 -> 90)

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/fiesque1567/NOTES.md in full, and the
   key, transcription and reading files it names; lang/README.md (shared language models).
   Work in targets/fiesque1567/. 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/fiesque1567/. 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+fiesque1567&page=fiesque1567.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.