# MISSING RECORDS ## The pattern Two consecutive dev calls of the recurring "VTC: Boundless app development" meeting — August 20, 2026 and August 27, 2026 — were denied recording permission by the host. Both AI note-takers that had auto-recorded every prior dev call in the series stopped producing artifacts on those two dates. This pattern is corroborated by two independent sources: Eyal's Gmail (Otter.ai and Read AI notification history) and Eyal's Read AI dashboard (which explicitly labels both calls "Cancelled — Read AI was not given recording permission by the host"). ## The recurring meeting - Meeting title (Zoom/calendar): **VTC: Boundless app development** - Recurrence: Weekly (Thursday, 8:00 AM PT / 6:00 PM EEST / 5:00-6:00 PM local as applicable) - Host: Boundless (George Goldsmith / Allan Malievsky / Suuvi Bacelar depending on session) - Participants across the series: George, Allan, Jacob, Bob, Eyal, Suuvi, Laura, Sian, Rosie ## The recorded calls (baseline) For three consecutive dev calls, **both** Otter.ai and Read AI recorded and produced transcripts. Notifications hit Eyal's Gmail inbox. The transcripts became foundational evidence in the negotiation record. | Date | Otter.ai "shared conversation" | Otter.ai "Meeting Summary" | Read AI pre-read | Read AI report | Transcript in archive | |---|---|---|---|---|---| | Mon Aug 3, 2026 | Yes — 15:01:39 UTC | Yes — 16:11:59 UTC | Yes — Aug 2, 14:14:39 UTC | — | Yes | | Thu Aug 6, 2026 | Yes — 15:01:59 UTC | Yes — 15:40:05 UTC | Yes — Aug 5, 14:13:26 UTC | — | Yes — `VTC_-Boundless-app-development-Transcript-1-13.txt` | | Thu Aug 13, 2026 | Yes — 15:01:34 UTC | Yes — 16:03:07 UTC | Yes — Aug 13, 14:15:40 UTC | Yes — meeting report emailed | Yes — `VTC_-Boundless-app-development-Transcript-2.txt` | Sender addresses: - Otter.ai notifications: `"Suuvi Bacelar via Otter.ai" ` - Read AI pre-reads: `Read Assistant ` and `Suuvi Bacelar via Read AI ` ## The blocked calls For the two dev calls immediately following George's "hit the pause button" WhatsApp message on August 20, 2026 (21:16:35 LA time), both AI recording tools were denied by the host. No transcripts were produced. | Date | Otter.ai "shared conversation" | Otter.ai "Meeting Summary" | Read AI pre-read | Read AI status | |---|---|---|---|---| | **Thu Aug 20, 2026** (5:55 PM – 6:13 PM per Read AI) | **No — did not fire** | **No — did not fire** | Yes (pre-read still sent) | **Cancelled — "Read AI was not given recording permission by the host."** | | **Thu Aug 27, 2026** (5:51 PM – 6:10 PM per Read AI) | **No — did not fire** | **No — did not fire** | **No — did not fire** | **Cancelled — "Read AI was not given recording permission by the host."** | ## The Read AI evidence Read AI's own dashboard on Eyal's account (`app.read.ai`, screenshots taken Aug 28, 2026, 22:46-22:47 IDT): - **Screenshot 1** (`read-ai-incomplete-aug20-aug27-cancelled.jpeg`): Read AI "Incomplete" tab. Shows both the Aug 27 and Aug 20 VTC: Boundless app development meetings marked "Cancelled" with Read AI's own status message: *"Read AI was not given recording permission by the host."* - **Screenshot 2** (`read-ai-reports-aug6-aug13-jul16-recorded.jpeg`): Read AI "Reports" tab. Shows the prior recurring meetings that were successfully recorded — the Aug 13 dev call (7 participants, host SB = Suuvi Bacelar), the Aug 6 dev call (8 participants, host EG = Eyal Gever), and the July 16 VTC George & Eyal 1:1 (2 participants, host EG). All three are complete reports with participant counts, sentiment scores, and meeting-type tags ("Planning Meeting", "Partnership Alignment"). Together the two screenshots show that Read AI was recording the same recurring meeting series successfully every week for weeks — and that the recording stopped on the two specific dates where the host actively denied permission. ## Timing - **Aug 6 dev call (recorded).** Transcript later quoted by Eyal in his Aug 20 "Where are we" email — George's "we've been working a bit with Phil and Simon… leverage this concept of entropy… dig into what EILS created" (auto-transcript mishearing of "Eyal"). Also George on tape: "That's amazing." - **Aug 13 dev call (recorded).** Transcript later quoted by Eyal — George's "based on Eyal's color palette, based on his research summaries" and "this is why we need to have Eyal on a call, but I think I need to prepare him because he's really attached to what he's done"; Allan's "we've included screens from ALS, live build, as well as from the app as it currently stands" (mishearing of "Eyal") and Allan's remark on the art-styles UI. - **Aug 20, 07:38 UTC.** Eyal sends "Where are we" email to George + Allan (cc Rosie). Quotes from the Aug 6 and Aug 13 transcripts are used to support the record of what was said in team calls. - **Aug 20, 5:55 PM local start (18:55 UTC-ish depending on tz).** Dev call happens. **Read AI is denied recording permission.** No transcript produced. - **Aug 20, 21:16:35 LA time.** George's "hit the pause button" WhatsApp message. - **Aug 27, 02:11 UTC.** Allan's dev-call invite email for the Aug 27 meeting. Notion agenda goal: "close the art-generation decisions with Eyal." - **Aug 27, 5:51 PM local start.** Dev call happens without Eyal in the room. **Read AI is denied recording permission again.** No transcript produced. ## What can be stated as fact 1. Otter.ai and Read AI both recorded every prior dev call in the recurring series (Aug 3, 6, 13). Evidence: Eyal's Gmail notification history, sender addresses documented above. 2. The Aug 20 and Aug 27 dev calls were denied recording permission by the host. Evidence: Read AI dashboard screenshots showing both dates marked "Cancelled — Read AI was not given recording permission by the host." 3. Otter.ai stopped producing "shared conversation" and "Meeting Summary" notifications for those same two dates. Evidence: absence of matching emails in Gmail from `no-reply@otter.ai` for those dates. 4. The pattern shift began the same week Eyal's Aug 20 "Where are we" email used quotes drawn from the Aug 6 and Aug 13 transcripts. ## What cannot be stated as fact (and should not be alleged in writing) 1. Who at Boundless specifically decided to deny recording permission. 2. Whether the denial was verbally communicated in the meeting or configured via Zoom host settings. 3. Whether Suuvi Bacelar's Otter.ai account was manually removed from the meeting invite or whether the recording setting was toggled on the host's end. 4. The specific intent behind the denial. The record shows what happened and when. It does not need to allege why. The reader can see it.