The Pressburg report and a servant’s letter, c. 1533–34

TASK: take a partial decipherment further: The Pressburg report and a servant’s letter, c. 1533–34
This page: https://dbourdeau.github.io/cyphersolver/further/r9416.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/r9416.html (read it first: how the text was read, the key, the reading)
  Date:       c. 1533–34
  Outcome:    ciphertext-only break · partial
  Read now:   35.3% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/r9416 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [no-key-material: needs a new source] f.263 beyond recto lines 11-16: letters on the multi-valued signs (b d/l, z e/s, p b/w, K k/b) chosen by sense, 3.9% of the reading's letters - blocker: no-key-material; 23 Oct 2026 (r2h) the whole leaf was re-keyed line by line on the full-resolution image (`r9416/f263_reading.md`, 0.775 explicit-hole share), but the contemporary gloss covers only recto 1-12 and the last verso lines and there is no print to confirm the rest.
  2. [no-key-material: needs a new source] f.263 codes +L (6x, beside Ferd.) and Ω (7x), the dotted-circle cluster (r12, r21, r34), and the groups r08-r09, v27-v28, v38-v40 - blocker: no-key-material; no gloss over them, values tried with the extended key 23 Oct 2026.
  3. [no-key-material: needs a new source] f.262 code signs X (3x), ⊼ (2x) and a G-sign (2x), the first group of A04, the end of A03 and one sign in B01 - blocker: no-key-material; no gloss over them (the gloss skips the B09 G and the B12 X); the rest of f. 262 is read from its signs, sign-label transcription `r9416/f262_signs.txt` (23 Oct 2026). Page B B08-B15 checked sign by sign 23 Oct 2026 (closed).

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: the volume's other ciphertexts and keys (R9423 register, System A′, System B, R9324) checked; none is the f.263 or f.262 sign set
  [x] clear-pages: the gloss on f.262 transcribed, and (23 Oct 2026) used to key the signs: f. 262 page A read from its signs; the faint gloss over f.263's first lines agrees with the solver's text
  [x] known-keys: the volume's keys do not fit either leaf
  [x] print: web search for KAA 4591 / the Pressburg talks report found no edition
  [x] key-rebuild: constrained annealing with de-1500s (first run); v2 look-alike split; lines 11-16 re-keyed by hand
  [x] retry: 23 Oct 2026 (r2h) the rest of f.263 re-keyed line by line on the full-resolution image with the extended key and the newly transcribed gloss (`r9416/f263_reading.md`); the f. 262 key tried and ruled out (different sign set)

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