Ferdinand the Catholic to Jerónimo de Vich, 1511–12

TASK: take a partial decipherment further: Ferdinand the Catholic to Jerónimo de Vich, 1511–12
This page: https://dbourdeau.github.io/cyphersolver/further/vich1511.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/vich1511.html (read it first: how the text was read, the key, the reading)
  Date:       1511–12
  Outcome:    key from adjacent plaintext · partial
  Read now:   48.6% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/vich1511 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [no-key-material: needs a new source] N.60 decoded, not read (explicit-hole share 0.589 on v2_score after the r2i proofread; `n60_reading.md` partial) - blocker: no-key-material; about 600 unread groups (phi 34x, reg 18x, pub 14x, fez, dup, fob, for, pog, pir, gox, geb ...) absent from the deciphered siblings and without one value at all occurrences (pub suizos 11/13, fez gasto, dup contrario, fob fortalezas 5/7 each: not adopted); Terrateig 1963 (unseen) may print the decipherment
  2. [illegible: needs a new source] N.60 ink blots and paper holes (L0827, L1219, L1402 one sign each; L1525-L1527) and doubtful single signs (L1315, L1316, L0534) - blocker: illegible; PARES zoom-10 resolution
  3. [no-key-material: needs a new source] N.45 (~424 [..]) and N.57 (24 [..]) holes - blocker: no-key-material; unkeyed groups (hno, hug, mun, myn, sig, phi, sab, rih, mug ...) and number signs, none in a deciphered sibling
  4. [illegible: needs a new source] Look-alike signs: tilde-d a / plain d b (N.57), fug senor / entre, fer dio / Fe-, fac dichas / dar, b a / i (N.60) - blocker: illegible; same shape at the PARES zoom-10 resolution, flagged for review in key.md
  5. [illegible: needs a new source] 8 no-bar q tokens in N.45, 2 q1 missing from the transcription - blocker: illegible; q/q1 split otherwise done (qwork/q_decisions.tsv)

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: N.46, N.52BIS, N.41, 8714 N.39 and N.12 aligned with their decipherments (5 Oct 2026); N.26 has no cipher online
  [x] clear-pages: the clerk's decipherments on the leaves after N.46 and N.52BIS aligned word by word
  [x] known-keys: the 1511-12 key rebuilt from N.46/N.52BIS fits all six letters in it; the N.74 (1519) system and the N.79 table are other systems
  [x] print: Zurita lib. X searched (narrates N.60's content, no letter text); Terrateig 1963 and Doussinague 1944 not online, unseen (5 Oct 2026)
  [x] key-rebuild: 153 groups recovered from the sibling crib and context readings
  [x] retry: N.45/N.57/N.60 re-decoded with the extended key (5 Oct 2026); token coverage 0.983/0.974/0.940. Re-read b16 (22-23 Oct 2026): all three built into sentences on the images and the key, twelve values added; N.45 and N.57 read, N.60 partial (explicit-hole share 0.591)
  [x] retry: 23 Oct 2026 (r2i) - N.60 pp. 4-14 proofread sign by sign (140 label rules, v5), poh/fub/ror/soi adopted, reading rebuilt: 0.572 -> 0.589, still under the bar

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