# Lucy 4/23 · source proof · cx5

1. **Mode applied: Lucy PREP · 4/23 gate · no execute.** The controller read the complete installed reference. It is byte-identical to the current control copy: 5,291 bytes, SHA-256 `7a39067aa836cde4a0d1aeacb5f3e556aeb3bac59f53656ddee2ae6e0aeb02ac`. The older Desktop file remains separate. This verifies the source used; it does not establish a separately running Lucy service.

2. **LSD = Lucy in the Sky of Diamonds.** This is the definition in `TONY_LEXICON.md`, line 142. The full sourced relay template is:

   `LSD-{LANE}-{VERSION}-{YYYYMMDD}-{HHMM}-{SUFFIX}-VT-369`

   This is a recorded label format. Typing it does not prove identity, what a model read, or runtime health. This pass has the audit receipt ID `LUCY-PREP-CX5-20260907-001`; that is not a newly adopted LSD format.

3. **Your 60-to-20 statement was found; the exact new format remains unresolved.** Telegram message 3998, on 9/5/2026 at 3:09:43 PM PDT, explicitly describes reducing the signature and timestamp from 60 to 20 characters. The inspected Phone Hub code still renders 60. The older shortened LSD example measures 21 characters; a separate corner code measures 16. The evidence report includes exact strings, recomputed lengths, 13 message excerpts and 20 source hashes. A further 44-file Dispatch search found no exact 20-character value.

4. **Dates carried forward from current canon.** Kali27 was named on 4/18/2026 at 6:21 PM PT. April 23 is a guard date, not Lucy’s birthday. Lucy first appears on 5/1/2026 at 10:20 PM PT. May 4 was a context-limit stop. The named Drive correction was fetched and read in full this pass. It remains a historical report; its old deployment and Hermes status claims are not current system evidence.

5. **The communication record now has a second delivery surface.** Jenny’s bot and Tony’s existing private chat were verified through Telegram. App links, the Lucy picture and animation were accepted with outgoing message IDs 76, 77 and 78. That proves outbound API acceptance, not that Tony opened them or that Telegram replies automatically reach this Codex task. A later user screenshot shows an existing “Kali27 4D Lucy” chat. The earlier local configuration check missed that chat; its current bot health remains unverified.

6. **Recovery is bounded and documented.** Substantive old cx2 is `01a06acf-5c2f-72e2-8bc9-8d80a53ac17c`, with 210 visible messages from its original M2 transcript. Old cx5 has 521 visible messages; its complete 058 handoff includes 39 copied files with matching hashes. All 731 messages are searchable in K27’s archive. A full export is different from closely rereading or verifying every historical sentence.

7. **Phone delivery is still awaiting Tony’s confirmation.** Server and browser checks pass. Tony’s screenshot showed a private communications page and Safari rejecting the desktop Codex address. Tony subsequently said he does not know whether the new link opened. The updated Build 12 phone route therefore remains unconfirmed on his physical phone.

8. **Restart.** In the ChatGPT app, choose Remote → M5 Kali-27 → `CX5 · Main Controller · M5 · 09/07 🟣`. Read `outputs/00_LIVE_CHECKPOINT.md` in this task. Resume the exact unresolved signature source and communication work from the saved receipts. No exact remaining context percentage is exposed, and compaction has not been claimed.