Alonso Sánchez at Venice to Charles V, 1522

TASK: take a partial decipherment further: Alonso Sánchez at Venice to Charles V, 1522
This page: https://dbourdeau.github.io/cyphersolver/further/sanchez1522.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/sanchez1522.html (read it first: how the text was read, the key, the reading)
  Date:       1522
  Outcome:    existing decipherment · partial
  Read now:   75.0% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/sanchez1522 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [no-key-material: needs a new source] R9653 cipher, second paragraph (f. 299v ll. 7-12) and single groups of the first, decoded, not read - blocker: no-key-material; xug, zi, tac, lud, qef, sob, ca, nu absent from Tomokiyo's table, single contexts, no decipherment bound or imaged
  2. [needs-physical-access: needs a new source] R9653 second copy (f. 300v) and R9654 (ff. 301-302, same date) - blocker: needs-physical-access; f. 300v only as faint bleed-through, R9654 not imaged on DECODE (rechecked 23 Oct 2026)
  3. [illegible: needs a new source] R9635 four uncertain words of the decipherment ([?bastar], [?tenido], [?Menorami], [?Lucerna]) - blocker: illegible; cramped court hand at DECODE's resolution
  4. [illegible: needs a new source] R9613 and R9641: three and two uncertain words of their decipherments ([?nescia], [?nemora], [?sus pagos]; [?conversacion], [?vera]) - blocker: illegible; fast cursive at DECODE's resolution
  5. [no-key-material: needs a new source] R9593 (5 March 1522) f. 27r ll. 26-33, f. 27v ll. 11-13 and about twenty open code groups (xe, vub, lud, fug, la, lif, ni, fu, sag, nif, ram, tag, zom, fag, pil, dug, nad, mug, tem, nog, ca, ce) - blocker: no-key-material; read sign by sign 23 Oct 2026 (r2o), groups absent from the published key and mostly met once, no decipherment bound or imaged, not in CSP Spain 2
  6. [not-attempted: doable now] the other Sánchez records of 9/23-9/26, 48 records (some duplicates: R9626/R9627, R9628/R9629; R9625 and R9638 mostly clear): R9594, R9595, R9596, R9597, R9598, R9599, R9600, R9601, R9602, R9603, R9604, R9606, R9607, R9608, R9609, R9610, R9611, R9612, R9614, R9615, R9616, R9617, R9618, R9619, R9620, R9621, R9622, R9623, R9624, R9625, R9626, R9627, R9628, R9629, R9630, R9631, R9632, R9633, R9636, R9637, R9638, R9639, R9640, R9643, R9647, R9651, R9655, R9657 - blocker: not-attempted; no decipherment imaged (r2i); R9594 is next in date order (5 pp., = CSP 396, whose decipherment is in the Gayangos papers); each readable sign by sign with the key as R9593 was
  7. [no-key-material: needs a new source] Lope Hurtado records R9634, R9644-R9646, R9648-R9650, R9652, R9656 - blocker: no-key-material; a third cipher, finals p/z absent from Sánchez's key; groups not in Tomokiyo's Juan Manuel table (see the lopehurtado1522 target)

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: R9603-R9657 metadata tabulated; R9605 facing decipherment aligned; R9648 examined
  [x] clear-pages: R9605 clerk's decipherment aligned as ground truth; R9635 interlinear glosses used
  [x] known-keys: Tomokiyo 2025 Sánchez key; Juan Manuel key compared for the Lope Hurtado leaves
  [x] print: done 2026-09-21 — Bergenroth CSP Spain vol. 2 (1866) grepped by Salazar folio; 14 of the DECODE records here are calendared as "Autograph in cipher. Contemporary deciphering" (English abstracts made from the bound decipherments). R9635 = no. 476 confirms the reading; the May 9/24 run and R9653 are not calendared. See "Calendared in CSP Spain 2" below
  [x] key-rebuild: c-block numerals by alphabetical bracket (cab, cef, cif confirmed), lel = puede, va = despacho; sign table from R9605
  [x] retry: 23 Oct 2026 (b23) — every DECODE image reopened (R9635's f. 22r decipherment found, R9653's f. 299v cipher found); R9653 re-read sign by sign and regraded (still decoded, not read); R9635 read
  [x] print: redone 23 Oct 2026 (r2o) - CSP Spain 2 entry by entry (nos. 380-515): R9593 not calendared, R9594 = no. 396 (decipherment in the Gayangos papers, cipher called not extant)
  [x] key-rebuild: 23 Oct 2026 (r2o) - gim = suyos and fef = toda adopted on every occurrence; ril = lansquenetes? flagged
  [x] retry: 23 Oct 2026 (r2o) - R9593 read sign by sign on line crops at 2-3.5x (decoded, not read, 0.614)
  [x] retry: 23 Oct 2026 (r2i) - R9635 tear read in the cipher of f. 20r; all 52 Sánchez records of R9593-R9657 fetched and every image opened; decipherments of R9613 (ff. 206-207) and R9641 (ff. 187-188, under R9642) found and read

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