Philip III to the Count of Añover, Lerma, 20 May 1610

TASK: take a partial decipherment further: Philip III to the Count of Añover, Lerma, 20 May 1610
This page: https://dbourdeau.github.io/cyphersolver/further/anover1610.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/anover1610.html (read it first: how the text was read, the key, the reading)
  Date:       1610
  Outcome:    key from adjacent plaintext · partial
  Read now:   86.5% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/anover1610 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [needs-physical-access: needs a new source] The transcription of f. 53r against the manuscript (Memoria de Madrid 424541), and of the sibling parallels A01-A14 etc. - blocker: needs-physical-access; the viewer answers scripted requests with an Access Denied page (a bot check, recorded on 13 and 14 Nov 2026, not got round), so it needs a person at a browser or the contributor's images as files. Two independent AI transcriptions of f. 53r agree on every digit string (the contributor's and Brice Dudout's, frozen 3 Nov 2026 by his record); one doubt stands: L05 `bo 32` or `60 32` (por fits the sense only)
  2. [needs-physical-access: needs a new source] The last sign of line 4, `clu` = tu in the contributor's reading (capi-tu-lado, control B02), written `du` by Brice Dudout, whose `du` is glossed *conde* twice in I 243,18 - blocker: needs-physical-access; one sign or two can only be settled on the images of both letters; asked of both in issue #499, no answer yet
  3. [open-codes: doable now] U01 (buena), 101, 114 and 241 (context-only codes), e = mu, fo = so (persona), the nulls 28~/58~ and the otraas anomaly - blocker: open-codes; tried on 14 Nov 2026 against the glossed letter I 243,18 (MdM 425791, Lerma 30 Apr 1610; section at the end): none of them occurs in it. This gap is workable, not blocked from outside: the further letters of the series (below) may carry these codes with a gloss
  4. [no-key-material: needs a new source] Devos 1950 and any complete nomenclator sheet of the series: not seen by anyone - blocker: no-key-material

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: I 242,33, 42, 47, 48 (and 71 as a control) matched by the contributor; I 243,18 aligned by Brice Dudout; their decipherments were not seen here
  [x] clear-pages: the letter has no decipherment bound in; its reverse carries an archival note about Angola
  [x] known-keys: Tomokiyo's page on Spanish seventeenth-century ciphers and DECODE searched by the contributor: no key for this series
  [x] print: Retortillo Atienza 2019 and the Correia thesis searched by the contributor; Brásio, Monumenta Missionária Africana V p. 587 opened by him (a different letter of 31 May 1610 on Pinda); a web search here found no printed reading. Devos 1950 is identified but no copy was seen by anyone (it treats Philip II's ciphers)
  [x] key-rebuild: the contributor's table (the material of this folder)
  [x] retry: the open codes run against Brice Dudout's alignment of the glossed I 243,18 on 14 Nov 2026: none occurs, no value changed; the unglossed I 242,35, 59 and 60 were not used: no transcription of them has reached the project (the contributor reports work on them in his dossier, not seen here, which settles no value of I 242,29); whether they are the three leaves left in catalogue 1988 is not mapped

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