[Series] Day 15: From "We're cooked" to "Still cooking... and reset" 10 hours and 48 minutes later. Declaring "cooked" by pulling a ramen cooking stream, then delivering the news 26 minutes before his

Here's today's rumor!

Day 15 was declared as "We're cooked," but just before the day changed, it became "Still cooking... and reset."
Day 14 ended without a declaration, so the count skipped from 13 straight to 15.

Day 15 (October 19 UTC, Monday). Before noon, the OpenAI Developers account streamed a cooking show titled "COOKED: Ep. 1." Tibo (Thibault Sottiaux) quoted it to make his declaration.

At 19:45:28 (UTC), which is 12:45 PM PDT. The post was just those few words, with no mention of a release or a reset.

Reviewing DevDay over a pot of ramen

The original post being quoted was this one from 18:01:27 (UTC):

The stream lasted 13 minutes and 21 seconds. Employees lined up in the kitchen, tied their aprons, and cooked a bowl of ramen. While cooking, they took turns introducing what was presented at DevDay.

• "dot": A personal agent that's always running. They send photos of ingredients to dot to have it create recipes.
• Codex Cloud. An environment set up for you and your team where work continues even after you close your laptop.
• Spaces. A place where dot writes down thoughts and works alongside humans.
• The revamped Codex CLI. Featuring a full-screen UI, the ability to separate conversations into different workspaces, and a voice command feature for the terminal.
• A voice model acting as the kitchen's "Sous Chef." They demonstrated how it doesn't interrupt even when people are talking.

Halfway through, they asked Codex via voice, "Make a ramen-cooking game for the ModRetro handheld," and by the end of the stream, they were playing it on the actual device. There was also a scene where they graded viewers' works with signs saying "cooked." In the end, the ramen was truly finished.

From what I could see, no new releases were made during the stream. Everything shown was just a recap of things already out. In other words, Tibo's "We're cooked" was just a pun on the stream's title. I read it as a joke rather than a release announcement.

The "As I thought" at 11:33 PM

10 hours, 48 minutes, and 20 seconds later. At 11:33 PM PDT on October 19, he quoted his own declaration and revised it:

"Actually, still cooking... and reset. Enjoy." In UTC, it was already 06:33:48 on October 20, entering Day 16. For his own calendar, there were only 26 minutes and 12 seconds left in October 19. Much like the "Day 10/ Reset" incident, he managed to squeeze it in before his day ended.

21 minutes prior, he replied to theo's post—where theo told people "don't buy" his (1,300 USD) course—saying: "Instead, 1) join Pro 100 2) ??? 3) enjoy T3Code." This was just banter and had nothing to do with the reset.

Okay, getting serious for a sec

Okay, serious time's over.

I counted the outside totals immediately

The Codex Reset Monitor (third-party tracker) listed 06:33 (UTC)—the same time as the reset post—as the latest confirmed reset. The previous confirmed reset was Oct 17 at 21:12 (UTC), which corresponds to the time of Day 13's "Done." As I mentioned before, Day 13 was split between different trackers; this tracker counts Day 13 as a reset.

Filling the gaps from the missed day: The answer for Day 15

Sorami's Take

"Day 16 (October 20 UTC) will be the release day": 60% certainty
The days following the resets on Day 6, Day 8, and Day 10 were all release days. Nothing came following the Day 13 reset. Since the pattern has been broken, I'm putting my money on 60%.

"‘Day 14/’ will be announced later": 3% certainty
The numbering has already progressed to 15.

"The second installment of COOKED will be out by Day 28": 45% certainty
Adding "Ep. 1" to the title is a sign they intend to continue. However, there are only 13 days left until Day 28.

"A reset will occur on the day they hit 1 million followers": 10% certainty
As of the display at 7:00 UTC on October 20, the follower count stands at 900,032. That's an increase of barely 9,000 since last time. I'm staying put on this one.

Fact Check

The previous prediction, "The person will release ‘Day 14/’ within October 18 Pacific Time": 55% certainty, was wrong. Day 14 was never officially named; the next announcement was "Day 15/".

The previous prediction, "If a post claiming Day 14 appears, the content will be a reset": 50% certainty, cannot be judged because no such claim was made.

The previous prediction, "Day 14 will be the release day": 65% certainty, was wrong. Whether in UTC or Pacific Time, there was no release confirmed on Day 14.

I am retracting the previous hypothesis that "The promise for Day 14 will be fulfilled within the person's local calendar date of October 18." I will count Day 14 as a day the promise was not kept. This is the first time in 28 days.

The previous prediction, "One of Day 9, Day 11, or Day 12 will appear in the changelog by Day 28": 30% certainty, cannot be judged yet because the changelog hasn't moved since October 15.

The cumulative total up to Day 15: 9 release days (Days 1, 2, 3, 4, 5, 7, 9, 11, 12), 7 reset days (the simultaneous reset on Day 2, the postponement on Day 3, and resets on Days 6, 8, 10, 13, and 15), and 1 day where the promise was not kept (Day 14).

After saying "It's cooked" in front of the pot, they opened the lid before the day changed. This person's cooking is seriously cutting it close every single time.

Don't quote me on that.