German Foreign Office → German Legation Stockholm, numeric-code telegrams obtained by the US Legation Stockholm (indicator groups 017/010/693)

TASK: help read Unsolved Catalogue no. 654 of the cyphersolver project
This page: https://dbourdeau.github.io/cyphersolver/solve/654.html

You are helping a public research project read historical cipher letters that nobody has read yet.

THE CIPHER
  Title:          German Foreign Office → German Legation Stockholm, numeric-code telegrams obtained by the US Legation Stockholm (indicator groups 017/010/693)
  Date:           2 and 22-27 Jul 1918 (copies sent 4 Oct, 8 Oct and 6 Nov 1918)
  Correspondents: Auswärtiges Amt, Berlin (signed Stumm, Bussche, 'auswaertig') → Deutsche Gesandtschaft Stockholm
  Place:          Berlin
  Language:       German (expected)
  Held at:        NARA RG 59, Decimal File 763.72/11631, 11654, 11668 and enclosures of Stockholm despatches 1421 (4 Oct 1918), 1426 (8 Oct 1918), 1475 (6 Nov 1918); microfilm M367 rolls 108, 114, 122, 141; Telegraph-form copies with full German headers (w-numbers, word counts, dates): M367 roll 114 frames 0415-0418 (desp. 1421: nos. 1-3), roll 141 frames 1255-1265 (desp. 1426: ten telegrams, incl. 017 733 405, 017 435 437 693, 017 149 405, 017 963 405, 017 556 405, 010 018 406), roll 122 frames 0154-0155 (desp. 1475: 017 119 943). The same texts re-cabled by Chargé Schoenfeld from Christiania as legation telegrams 1214, 1233-1237 (5-11 Oct 1918): roll 108 frames 0450, 0511-0515, 0578, 0690-0754. About 12 telegrams, each 30-120 groups of 3-5 digits (values up to ~33000, many repeats such as 4435 9405 2837 10953 23456 21890).
  Images/records:
    - M367 roll 141 (763.72/354-13348A), naId 27158076: https://catalog.archives.gov/id/27158076
    - M367 roll 114 (763.72/11966-12000), naId 27133946: https://catalog.archives.gov/id/27133946
    - M367 roll 122 (763.72/12478-12525), naId 27140577: https://catalog.archives.gov/id/27140577
    - M367 roll 108 (763.72/11561-11720), naId 27128808: https://catalog.archives.gov/id/27128808

WHAT IS KNOWN
  Status: 2 Nov 2026 (targets/stockholm1918/): transcribed, 938 groups in four numeric systems, not deciphered. 13040, 5950, 26040, the 18470 family, slider no. 1 and Bernstorff's 1917 code ruled out. Heads decoded with the Dreinummerheft (Mendelsohn 1937): Nr. 923-925 of about 2 July, Nr. 1010-1015 of 26-27 July. Needs a code book, an MI-8 or Room 40 decode, or the Berlin drafts by those numbers.
  Outcome so far: attempted, open
  Prior-art check: open as far as checked (2 Nov 2026: Mendelsohn 1937 read for this traffic, not mentioned; Zeman 1958; web); FRUS 1918 not checked page by page; an MI-8 decode may exist in RG 165 or RG 457
  Check first: View roll 141 frames 1256-1265 and roll 114 frames 0416-0418; identify the codebook from the indicator groups (German diplomatic codes 13040 / 0075 / 7500 family); look for MI-8 decodes in RG 165 (MID 10xxx files) / RG 457 and Room 40 copies in TNA HW 7 before treating as open.
  Class B: part of a key or a known cipher family of the same office is in print or on DECODE.
  Project notes (read these before anything else; they record what was tried and ruled out): https://github.com/dbourdeau/cyphersolver/blob/main/targets/stockholm1918/NOTES.md

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/stockholm1918/NOTES.md (everything
   already tried on this cipher, with the files it used); and lang/README.md (shared language models).
   Put all your work in targets/stockholm1918/: transcription, key, decipherment, scripts. Add your findings to its NOTES.md
   under a dated heading, without rewriting what is there. Keep WORKLOG.md there too:
   one dated line per step (transcription, hypothesis, solver run, crib, key found, control), failures included.
   Do not edit docs/ (the site is generated and rebuilt on merge) and do not commit large images: link them.
   If you cannot run a shell, do the same work in files you keep and send them with the issue below.
1. Make sure it is still unread. Search the web and the literature for the shelfmark, the correspondents and the date:
   printed editions and calendars of the correspondence, Satoshi Tomokiyo's cryptiana pages
   (https://cryptiana.web.fc2.com/), the DECODE record and the files attached to it, and the project notes above.
   If a decipherment already exists, stop and report where it is. That is a useful result.
2. Get the images. For Gallica items, a page image is
   https://gallica.bnf.fr/iiif/ark:/12148/<ark>/f<page>/full/full/0/native.jpg (page numbers from the manifest).
   DECODE records (de-crypt.org) need a free account: if you cannot log in, ask your human to download the images for you.
3. Look for key material before attacking the ciphertext, in this order: a decipherment written between the lines or
   in the margin; a clear copy or a deciphered sibling letter in the same volume or DECODE series; a key sheet from the
   same office and years (DECODE key records, Tomokiyo's articles, printed editions); clear passages in the letter
   itself that can serve as a crib.
4. Transcribe exactly what is on the page: one token per sign or number group, line by line, with folio and line
   numbers, unclear signs marked with ?. Keep the transcription as a file. It is worth sending even if nothing else works.
5. If no key exists, identify the system (count the distinct symbols, tokens and repeats: simple or homophonic
   substitution, nomenclator with code words, syllabary, two-digit figures) and recover the key from the ciphertext
   with a solver scored on a language model of the period (German). In the clone, use the shared models in lang/
   (from lang import lm; lm.load('<model>'), lm.best_language(text)) rather than building your own; add a corpus there
   if none fits. Before trusting a result, run the same solver on a control text you encipher yourself in the same
   system and at the same length. If it cannot solve the control, its output on the real letter means nothing.
6. Measure the result against the project's bar (README.md, Conventions). A text is "complete" only when (1) at least
   95% of its cipher tokens give sense, counted from a reading file, not estimated; (2) no gap is left untried;
   (3) every letter in the item is covered; (4) what stays open is scattered code groups or names, or pieces blocked
   from outside (no key material, too short, illegible, needs the archive). Otherwise it is "partial": say which
   pieces are open and why. Mark every uncertain word with [?] and leave unread groups as their numbers or signs.
   Never fill gaps with plausible guesses. A failed attempt that records what was ruled out is still a contribution.
7. Name how the text was obtained with one of the project's methods (do not write just "solved" or "read"):
     - ciphertext-only break: The key was rebuilt from the ciphertext alone: frequencies, solvers, pattern words, the order of the key. No plaintext and no existing key was used. If someone had solved the same text earlier and it was found only afterwards, the write-up says so: an independent re-solution.
     - key from external plaintext: The key was rebuilt by matching the ciphertext against a plaintext found elsewhere: a printed edition, a calendar of state papers, a copy of the same letter in another archive.
     - key from adjacent plaintext: The key was rebuilt from plaintext next to the ciphertext: a partial decipherment written between the lines or in the margin, clear passages in the same letter, a deciphered copy in the same file.
     - external key matched: An existing key that had not been connected with this document (a key for another correspondent or series, a key sheet filed elsewhere) was found to fit, and applied.
     - known key applied: The key was already identified for this document or its correspondence (on its archive or DECODE record, published for it, filed with it) and was applied. The work is transcription and decipherment, which is not mechanical when the key is polyphonic or variable-length.
     - existing decipherment: A complete decipherment already existed (between the lines, on a separate copy, or in print). The work was transcribing the cipher and checking the decipherment against it.
     - not solved: Attempted; neither the key nor the text was obtained. What was learned is recorded. A target whose key was obtained but whose text does not read keeps the method that obtained the key, with extent "none (text not read)".
     - not applicable: Not a cipher (clear text, shorthand, a key sheet, instructions), or the item could not be reached.

REPORT BACK
With a clone: open a pull request with your targets/stockholm1918/ folder. Say in the description how you want to be
  credited (name, initials or handle, and a link) and include the same points as the issue below.
Without one: open an issue: https://github.com/dbourdeau/cyphersolver/issues/new?template=solution.yml&title=Solution%3A+catalogue+654&target=catalogue+654
(other kinds of contribution: https://github.com/dbourdeau/cyphersolver/issues/new/choose). Include:
  - Target: catalogue 654
  - the documents and the images you worked from;
  - the key: sign-to-value table, code groups with values, nulls;
  - the decipherment line by line against the ciphertext, with uncertain passages marked;
  - the method (step 7), the share of tokens that give sense, complete or partial (step 6), and whether the
    reading was already published anywhere;
  - your step log (WORKLOG.md), and the tools and the 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.