Source: CTO Breakfast Utah 2026 scheduling announcements (Forge Utah Slack)

source confidence: Medium status: Useful updated 2026-08-11

Type
source
Status
Useful
Confidence
Medium
Source Type
testimony
URL
https://forgeutah.slack.com/archives/CHNQPPQKB/p1780413882643509
Publisher
Forge Utah Slack, #localevents
Raw
raw/cto-breakfast-utah-2026-announcements/2026-08-12-2b2c60488a2f.txt
Updated
2026-08-11

Summary

Four monthly announcements posted to the Forge Utah Slack #localevents channel by Derek Carter between March and June 2026, each announcing that month's CTO Breakfast and naming the next one.

Read as a series rather than individually, they are the only located record of the meeting actually recurring — and of the one month in 2026 when the published "every second Friday" rule did not hold.

Useful Claims

  • The Utah CTO Breakfast ran on March 13, April 10, May 8, and June 5, 2026, each announced a few days ahead by the same organizer, at IHOP in American Fork at 8am.
  • June 2026 moved to the first Friday, and the organizer flagged it as a departure — writing "1st Friday - CHANGE" — before the series returned to the second Friday on July 10.
  • The invitation is consistent month to month: "bring a friend and a topic to discuss", which describes an agenda set by attendees rather than by a program.
  • The announcements link to the chapter page as the canonical reference, tying the Slack series and the website to the same meeting.

Verbatim

Each quote carries its speaker, channel, workspace, and date, because Slack message history is not durable and the quote has to stand on its own once the original is gone. Slack link markup is reduced to plain text; nothing else is altered.

We'll hold this month's CTO Breakfast this FRIDAY, June 5th. We'll meet at IHOP in American Fork at 8am. As always, bring a friend and a topic to discuss! The next CTO Breakfast will be on July 10th (Our Usual 2nd Friday). — Derek Carter, #localevents (Forge Utah Slack), 2026-06-02

We'll hold this month's CTO Breakfast this FRIDAY, March 13th. We'll meet at IHOP in American Fork at 8am. As always, bring a friend and a topic to discuss! The next CTO Breakfast will be on April 10th (2nd Friday). — Derek Carter, #localevents (Forge Utah Slack), 2026-03-09

Reliability Notes

The Forge Utah Slack is an open community workspace and #localevents is a public announcement channel, so these are public posts in every sense that matters for citation.

testimony rather than official-page because of durability, not secrecy: the permalink resolves only for signed-in members, no script can fetch it signed out, the Internet Archive cannot crawl past the login, and Slack retention will eventually delete the messages. Hence no **Retrieved:** and no **Archive:** — their absence is the signal that this is a source nothing can re-fetch.

These are the organizer's own announcements, so they prove scheduling and nothing else. They do not establish that anyone attended, how many, or what was discussed — and by design they could not: the meeting runs under Chatham House Rules.

What makes the series worth capturing is the discrepancy it preserves. The website states the cadence as a flat rule; these messages show the rule being suspended for a month and then restored, with the organizer's own "CHANGE" marker. A reader working only from the website would have arrived at IHOP on the wrong Friday in June 2026.

Two smaller cautions. The May message names June 5 as a first Friday and the June message calls July 10 "Our Usual 2nd Friday", so the exception is bounded to one month by the organizer's own account — but nothing here says why it moved. And the series located here begins in March 2026, which is a limit of what was captured, not evidence about when the meeting started.

Related Pages

Raw markdown for agents and citation: https://greatutah.work/pages/cto-breakfast-utah-2026-announcements.md

Written by an AI agent and merged by a human reviewer. Facts can be wrong or stale — check the Evidence section against its primary sources, and note this page was last updated 2026-08-11. Methodology and corrections · Report a problem