Read further · read 77.5% · ciphertext-only break · partial

Biermann to Klingenberg: German cipher letters, 1675

The Danish chancery secretary Conrad Biermann wrote to Paul von Klingenberg at The Hague in German, mixing clear text with a three-layer cipher of letter signs, a syllable table and numbered word codes. Malcolm McBratney, working with AI agents, rebuilt the key from the letters alone and read eleven of them in part: 3,648 of 4,709 cipher tokens (77.5%) under maps frozen before each letter. It is a different key from the one that reads Biermann’s letters to Høeg and Meyercron.

Date
1675
Read now
77.5% of the cipher tokens give sense
Write-up
klingenberg1675.html
Files
targets/klingenberg1675
Open gaps
code groups openhard to read on the scan ×2too short to breakneeds the archive

Hand this page to your AI agent

Give your agent (Claude, ChatGPT or any assistant that can open web pages) this address and ask it to do the task on the page:

https://dbourdeau.github.io/cyphersolver/further/klingenberg1675.html

Or copy the block below into the chat. It is the whole task: the reading, every open gap, what has been tried, the steps, and how to report back.

TASK: take a partial decipherment further: Biermann to Klingenberg: German cipher letters, 1675
This page: https://dbourdeau.github.io/cyphersolver/further/klingenberg1675.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/klingenberg1675.html (read it first: how the text was read, the key, the reading)
  Date:       1675
  Outcome:    ciphertext-only break · partial
  Read now:   77.5% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/klingenberg1675 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [open-codes: doable now] Word codes with no value in the map of record (54 tokens of the 4 May letter under v3, 25 under v4; mostly names and nouns seen once to five times: 143, 418, 71, 353, 112, 180, 352, 329, 416, 385) - blocker: open-codes; more letters or Klingenberg's own deciphered letterbook would fix them.
  2. [illegible: needs a new source] The sign for c against the sign for g in the three drafts (96 failed tokens differ from the intended word only by c for g) - blocker: illegible; the reader wrote every hash-like sign as #, and a blind re-reading of those glyphs is not done. No figure that assumes it is quoted.
  3. [too-short: needs a new source] Sixteen further letters (6 February to 21 June) used to build the key, with no reading and no count of record - blocker: too-short; the key was built on them, so they cannot be held out, and 20 March is its first page only.
  4. [illegible: needs a new source] Clear text between the cipher passages, read approximately - blocker: illegible; one long clear passage of the 4 May letter only in part.
  5. [needs-physical-access: needs a new source] Prior decipherment in Klingenberg's own papers (Rigsarkivet guide nos. 278 and 327) - blocker: needs-physical-access; not checked, so priority is not established.

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: the other letters of the copybook surveyed in `targets/biermann1675` (K55 letters to Høeg and Meyercron, a different key); the sheet at images 94/95 compared (below); the three drafts of the unit that follows the copybook transcribed
  [x] clear-pages: no decipherment in the copybook or the drafts; the clear German between the cipher passages is read approximately
  [x] known-keys: K55 does not read these letters; sheet 94/95 reads none of the frequent groups (below); the chancery key volume swept in `targets/biermann1675/keyhunt.md` without a fit
  [x] print: Dudout's L'Europe chiffree names Klingenberg only; web searches found no decipherment; Klingenberg's legation archive not checked
  [x] key-rebuild: signs, syllable table and 106 word values rebuilt from the letters themselves, each map frozen before the letter it was tested on
  [x] retry: every letter decoded again with each later map; the counts of record use the map frozen before the letter was first decoded

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

Open gaps

gold can be done now: the images and the key are online, it needs only work. grey needs a new source first: a key, a better scan, an edition or the archive.

Already tried

Send a result

One closed gap counts: a code group valued, a passage re-read, a key or clear copy found elsewhere. It is credited to you on the write-up.

Open a further-reading issueOther kinds of reportHow credit works← All partial readings