# Later archival-source update

Checked 16 September 2026 UTC. This note supplements the original research record;
it does not modify the frozen discovery or completion archives.

CryptoCellar's July page, now dated 15 September 2026, publicly links the incoming
red message No.172 facsimile. During the initial investigation we had the typed
received transcription and the outgoing NF 88/61 facsimile. Statements in the
original reports that the incoming scan had not been located describe that earlier
source state.

The new one-page incoming sheet visibly preserves No.172, the MVUEH identifier,
and the GTA / KCI header. It is a ciphertext form; no plaintext is visible on it.
The existing typed received transcription remains unchanged. The public message
list still marks No.172 “Fails” at this check. The addition of a scan is not itself
a published solution announcement or an endorsement.

- [July messages and new facsimile link](https://cryptocellar.org/bgac/g-army-july-1941.html)
- [Incoming No.172 facsimile](https://cryptocellar.org/bgac/spruch/10071941-172-in.pdf)
- [Outgoing NF 88/61 facsimile](https://cryptocellar.org/bgac/spruch/10071941-088-061-out-nf.pdf)
- [Public message list](https://cryptocellar.org/bgac/1941-msg-list.html)

Incoming PDF: 772,726 bytes. SHA-256:

```
0b1bc14cfd5aac9d1c1879496ec43d93036f632e1bd7d031751bc9b028ede6df
```

The new incoming scan warrants a separate source comparison. This exhibit update
does not claim that a fresh, blind transcription of every incoming glyph has been
completed. Its interactive comparison preserves the original typed input and the
predeclared outgoing reading alternatives.