Huang Xing’s numeric telegrams, June 1916

TASK: take a partial decipherment further: Huang Xing’s numeric telegrams, June 1916
This page: https://dbourdeau.github.io/cyphersolver/further/numeric1916.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/numeric1916.html (read it first: how the text was read, the key, the reading)
  Date:       June–July 1916
  Outcome:    ciphertext-only break · partial
  Read now:   99.9% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/numeric1916 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [illegible: needs a new source] 共密: 45 doubtful characters in 9 telegrams - blocker: illegible; uncertain digit readings or rare codes, marked on his pages
  2. [illegible: needs a new source] 容密: 102 doubtful and 6 illegible characters in 14 telegrams - blocker: illegible; uncertain digits on the police copies, and recurring anomalous codes (繒 for 生, 盻 for 盼) kept as marked
  3. [illegible: needs a new source] 辰密: 7 doubtful characters (four single-digit probable readings, 一不 for 不一, 盻 for 盼) - blocker: illegible; single-digit uncertainties on the forms
  4. [needs-physical-access: needs a new source] V4B (容密, 265 groups): only 4 of its 22 sheets re-read blind; framing repairs in V4B, V4D, V4E still to be checked on the scans - blocker: needs-physical-access; contributor's re-reading of the JACAR scans, not done here
  5. [no-key-material: needs a new source] N07 (prefix 共密, does not decode under the 共密 key; only the first sheet transcribed), N06 (和密), N09 (乾密), N01 and N03 (no prefix) - blocker: no-key-material; other keys or the other direction's book, no plaintext, only first sheets transcribed by the contributor
  6. [illegible: needs a new source] ~~共密 and 容密 telegrams: decoded, not read~~ closed 23 Oct 2026 (b21): both read from Dudout's proposed readings checked group by group; 共密 21 [?x], 容密 47 [?x] + 6 illegible groups left - blocker: illegible; digits to re-read on the police copies, or names and date codes (telegram endings)

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: his 32-telegram set covers every form in B03050089200-89500 and the vol. 4 items; the unread five are listed above
  [x] known-keys: 共密 and 容密 keys tried by him on 辰密 and on N07 before the 辰密 search; they do not read them
  [x] print: Hsueh Chun-tu ed., 黃興等電稿 checked by him: nothing between 8 and 20 June; 黃興集 and Li Yuanhong's correspondence not yet checked
  [x] retry: (23 Oct 2026, b21): one-digit variants listed for every unresolved group; N24 灰 adopted, V4E [?垣] kept as conjecture, the rest left; N35 sheet 1 re-read on the JACAR scan

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