Poinsett to Monroe from Santiago, 20 February 1813

TASK: take a partial decipherment further: Poinsett to Monroe from Santiago, 20 February 1813
This page: https://dbourdeau.github.io/cyphersolver/further/poinsett1813.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/poinsett1813.html (read it first: how the text was read, the key, the reading)
  Date:       1813
  Outcome:    external key matched · partial
  Read now:   88.1% of the deciphered cipher tokens give sense (pieces below may be untouched)
  Files:      https://github.com/dbourdeau/cyphersolver/tree/main/targets/poinsett1813 (NOTES.md, key, transcription, reading, scripts)

OPEN GAPS (from NOTES.md, "## Remaining gaps")
  1. [illegible: needs a new source] P0, f. 37r (frame 0092), about three lines of groups - blocker: illegible; the microfilm frame is nearly black; needs a new scan of the original (NARA RG 59) or the 1813 duplicate if one survives
  2. [open-codes: doable now] 20 Feb 1813, 7 groups whose WE025 value gives no sense where they stand - blocker: open-codes; the groups are 55, 12, 502, 774, 487, 122, 1261 (five of the numbers, 55, 502, 487, 122, 1261, occur nowhere else in the letter); a misread digit, a slip of the encoder or a wrong row of our copy of the table cannot be told apart from these frames
  3. [illegible: needs a new source] 20 Feb 1813, 20 groups read only by assuming a digit misread - blocker: illegible; listed in `beling/groups_1813-02-20.tsv` (status I); the film is high-contrast, the doubtful digits are filled blots or lie at the gutter and the page edge; eleven were looked at again on frame 0093 on 12 Nov 2026 (integration check) and none can be settled digit for digit there; needs a new scan of the original
  4. [illegible: needs a new source] 20 Feb 1813, 25 groups whose number was fixed after the decode was seen - blocker: illegible; 21 choices between two readings frozen beforehand and 4 rereads; same film; one transcriber, no second reader of the numerals
  5. [open-codes: doable now] 1315, three times in the 14 June 1814 letter where "a" is wanted - blocker: open-codes; WE025 has "hu" and 1215 = a; 1315 is clear on frame 0100 all three times, so it is not a misreading of 1215; not explained
  6. [needs-physical-access: needs a new source] 210 in Brice Dudout's 1811 line ("in-form-ed") - blocker: needs-physical-access; WE025 has "cur" at 210 and "form" at 216; his photograph of the HSP leaf is not published, so the digit cannot be checked here
  7. [needs-physical-access: needs a new source] that the table used is the one Weber prints as WE025, row for row - blocker: needs-physical-access; neither the book nor the contributor's full transcription is in the repository (341 of 1,592 rows are, 10 marked as checked on the page image); the page numbers given for the table conflict (see the integration check)
  8. [no-key-material: needs a new source] the marks over and under groups (circle, diamond, cross, caret) - blocker: no-key-material; their meaning is read from use only, no instruction sheet for this code is in hand

ALREADY TRIED (from NOTES.md, "## Escalation")
  [x] siblings: M37 roll 2 frames 0091-0102 opened; 14 June 1814 (0098, duplicate 0100) is in the same code with a clerk's decode, used for the key; 0462 (Jacob Lewis) is another code; Sumter's Rio code (M121) is not this one. 28 Oct: M37 roll 1 (all 753 frames), M37 roll 2 frames 0025-1057, M70 roll 1 (Buenos Aires consular despatches 1811-17, 292 frames) and M77 vol. 7 (instructions 1808-15, sampled) surveyed by contact sheet: no further frame in this code and no key table. Lowry, La Guaira 1810-12 (M84 roll 1 frames 0014-0090): all clear. Not surveyed: M78 consular instructions 1801-17 (naId 220862827)
  [x] clear-pages: Manning prints the clear text only; no clear copy of the cipher passages found
  [x] known-keys: JQA/Department 1803-40, Armstrong THE=972, Pinckney, 1788 legation, Jefferson 1787, Mountflorence 1801, Sumter 1813 tried directly and under shifts; none fits. 11 Nov 2026: the printed table WE025 (Weber 1979) is this code (Beling; beling/README.md)
  [x] print: Manning vol. 1 doc. 201 (1925) prints the 14 June 1814 letter decoded (the clerk's text); vol. 2 prints the 1813 letter undecoded; Weber 1979 consulted by the contributor on 11 Nov 2026 (table only, no decode of 1813). The HSP calendar of the Poinsett papers (1941, HathiTrust mdp.39015034759822) is behind a bot check and was not searched; it is a calendar of his own papers, where no decode of the Department's copy is expected
  [x] key-rebuild: context pass of 27 Oct gave only 'Lima'; superseded by WE025, which gives every group a value. The seven holes cannot be bracketed: the code is not in alphabetical order
  [x] retry: 11 Nov 2026, every group decoded again with WE025 from the frozen numerals, four rereads on the image (Beling); 12 Nov 2026, eleven of the twenty assumed misreads looked at again on frame 0093 (integration check)

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