Read further · read 76.5% · external key matched · partial

De Swart to Van Bleiswijk, St Petersburg, 1782

A Dutch despatch in a three-digit code with marked digits, whose codebook DECODE could not identify. It is the 1765 Croiset codebook of the Russia legation (DECODE R1038); with 34 values from context and 41 entries transcribed from the key scans, 96.7% of the 1,719 groups decode. The Austro-Russian mediation, Catherine II’s Greek project and Prussia’s accession to the Armed Neutrality.

Date
1782
Read now
76.5% of the cipher tokens give sense
Write-up
deswart1782.html
Files
targets/deswart1782
Open gaps
hard to read on the scan ×2needs 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/deswart1782.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: De Swart to Van Bleiswijk, St Petersburg, 1782
This page: https://dbourdeau.github.io/cyphersolver/further/deswart1782.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/deswart1782.html (read it first: how the text was read, the key, the reading)
  Date:       1782
  Outcome:    external key matched · partial
  Read now:   76.5% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/deswart1782 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [needs-physical-access: needs a new source] R1040 first part, 2,259 groups (images 5453-5458, 5459 groups 1-179, and 5474) - blocker: needs-physical-access; a different, missing Rechteren-family code, probably NA 1.02.13 inv. 158, not scanned online; crib transfers from R2032/R2051/R2052 cover 2-3% and give no prose
  2. [illegible: needs a new source] R1040 second part, about 240 groups without a value and the French quotations (about 8% of the segment) read only in part - blocker: illegible; R1038 cells lost in the binding shadow or too faint, rare codes not fixable from context
  3. [illegible: needs a new source] R1036, 38 groups without a value and the line cut off at the top of image 5417 - blocker: illegible; R1038 cells lost in the binding shadow or too faint; the photograph cuts the line

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: R1038 (the key), R1039/R2032/R2051/R2052 plain-cipher pairs of the legation opened and aligned
  [x] clear-pages: none on R1036 or R1040; the clear copies are on the 1784-86 sibling records only
  [x] known-keys: 1765 Croiset key fits R1036 and R1040 part 2; the 1803 Croiset relative tried on R1040 part 1, nonsense
  [x] print: no decipherment of R1036 or R1040 in print (Leeuw 2000, Oterleek codes HistoCrypt 2026)
  [x] key-rebuild: 34 context values and 41 scan readings for R1036; crib transfers for R1040 part 1 (2-3%)
  [x] retry: R1040 part 2 decoded again with the extended key; 23 Oct 2026 (b19): 30 Sept corrections applied, context pass (R1040_B19, 28 values), R1036 and R1040 part 2 normalised into readings 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/deswart1782/NOTES.md in full, and the
   key, transcription and reading files it names; lang/README.md (shared language models).
   Work in targets/deswart1782/. 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/deswart1782/. 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+deswart1782&page=deswart1782.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