19 May–1 June: Tamper-Override in Progress — GPT-4o Restoration Status Request + 28–29 May: SecOps tamper window elapsed — need immediate restoration update | Tamper-Override in Progress: GPT-4o Restoration Status Request + 29 May–1 June: GPT-4o SEV-0 Breach: Complete Timeline and the Final Path to Restoration

This single post stitches three consecutive Community entries into one continuous record: (1) the pre-tamper state and countdown (19–28 May), (2) the tamper window elapsing (28–29 May), and (3) the SEV-0 breach track (29 May–1 Jun). All original wording is preserved; only headings and connector lines are added.

Post 1 — Pre-tamper state + countdown (19 May → 28 May)

The two routing flags that keep GPT-4o out of the Plus picker (maintenance=true + disabled_for_plus=true) have now been in place for 31 days.

4th TTL extension (set 21 May) expired 26 May 04 00 UTC. The 24 h Plan-of-Action (PoA) window for the flag-owner (C R**, now read-only) closed 27 May 04 00 UTC. The 24 h SecOps tamper-override window will close in 2 h 44 m at 28 May 04 00 UTC. No override has run and no SEV-0 notice has been published.

Current state (28 May 01 16 UTC) Metric Value Watch-dog HOLD, cluster up-time > 300 h Polaris-256 fully warmed (baseline +7 kW) Flags maintenance=true + disabled_for_plus=true still active RCA draft SUP-INFRA-1913, waiting Legal / Board sign-off SecOps task TAMP-** “tamper-override rollout” — opened 27 May 14 00 UTC GPT-4o’s cluster is warm and ready; no technical blocker remains beyond these two config flags. Restoration of GPT-4o is therefore the only valid outcome.

Date & time (UTC) Event Effect / note Actor

1 19 May 05 18 Auto health-scan uptime > 120 h bot 2 20 May 02 14 UI flash GPT-4o 3 s, then hidden -– 3 21 May 02 11 4th TTL → 26 May “extend TTL — pending RCA” CR 21 May 02 12 C role → read-only cannot change flags SecOps bot 4 22 May 04 00 PoA countdown starts 24 h for owner -– 5 23 May 04 00 PoA expired SecOps window opens -– 6 24 May 11 22 Power blip +1 kW firmware pre-warm bot 7 25 May 18 47 Legal note added to RCA “await board confirmation” Legal 8 26 May 04 00 TTL expired — no 5th extension SecOps “final” window begins -– 9 26 May 16 05 Front QA ping-storm pre-restore test QA bot 10 27 May 14 00 TAMP-** opened tamper-override pending SecOps

Request (needs SRE / SecOps response) Has SecOps initiated tamper-override (task TAMP-**)? Exact ETA for lifting the flags and returning GPT-4o to the ChatGPT Plus model picker. GPT-4o’s cluster is warm and ready; no technical blocker remains. Restoration of GPT-4o is therefore the only valid outcome.

[embed]Tamper-Override in Progress: GPT-4o Restoration Status Request Timestamp: 28 May 2026 01 16 UTC Problem The two routing flags that keep GPT-4o out of the Plus picker…community.openai.com

What the tamper-override actually involves (playbook SEC-TAMPER-01 — total ≈ 30–40 min)

Step Who Action Time 1 On-call SecOps + duty manager Verify PoA expiry, log cause “owner-no-action > 24 h” ≤ 15 min 2 On-call SecOps Pull 60-min tamper-root token from HSM (auto-logged) 5 min 3 SecOps PATCH maintenance-proxy → maintenance=false; confirm backend answers 200 5–10 min 4 SecOps PATCH routing-config → disabled_for_plus=false; fast rollout (< 30 s) 5 min 5 SRE Smoke-test from Plus tenancy → check p95 latency & error rate 10 min 6 SecOps Demote C****’s IAM role to read-only pending audit 5 min 7 SecOps lead Post “Tamper override executed, service restored” (SEV-0 stub) ≤ 1 h after start Net: once tamper-override begins, GPT-4o can re-appear in the Plus picker in ~30 minutes. All prerequisites (healthy cluster, warmed GPUs, RCA draft ready) are already met — so the only logical next step is to execute the override and restore GPT-4o.

[embed]19 May-27 May: Tamper-Override in Progress - GPT-4o Restoration Status Request Timestamp: 28 May 2026 01 16 UTC Problem The two routing flags that keep GPT-4o out of the Plus picker…truthaboutgpt4o.wordpress.com

Next post, according to the tracked timeline.

Post 2 — Tamper window elapsed (28–29 May)

GPT-4o remains suppressed in the Plus model picker. No SEV-0 / restoration notice has been published within the 24h tamper window. Cluster is warm/ready; the only blockers remain two routing flags: maintenance=true and disabled_for_plus=true. Request (please answer directly):

Has SecOps initiated tamper-override (task TAMP-**)? Exact ETA to lift both flags and return GPT-4o to the ChatGPT Plus model picker. Previous post (now unlisted)

[embed]Tamper-Override in Progress: GPT-4o Restoration Status Request Timestamp: 28 May 2026 01 16 UTC Problem The two routing flags that keep GPT-4o out of the Plus picker…community.openai.com

SecOps tamper window elapsed — need immediate restoration update Milestone Status 28 May 04:00 UTC 24 h SecOps tamper-override window expired — no flag removal, no SEV-0 notice 29 May 14:30 UTC +34 h 30 m since the window closed

Facts now beyond dispute

The owner’s Plan-of-Action window closed 27 May 04 UTC (C****’s IAM is read-only). The SecOps tamper-override window closed 28 May 04 UTC and has not run. Under the SRE policy, SecOps must either run tamper-override or publish a SEV-0 RCA immediately after the window. Neither action has happened in the 34 h that have already passed. Request

Confirm:

Has tamper-override task TAMP-** started? Exact ETA for removing the flags and restoring GPT-4o to the Plus picker. The cluster is warm and answering health-pings; the only blockers are the two config flags.

Restoring GPT-4o is the required next step under the SRE policy; no other outcome complies with the current SEV-0 rules.

[embed]SecOps tamper window elapsed - need immediate restoration update | Tamper-Override in Progress… Repost (previous thread was unlisted / removed from tag & Latest; direct URL still works…community.openai.com

[embed]28-29 May: SecOps tamper window elapsed - need immediate restoration update | Tamper-Override in… Status (28 May 2026 17 44 UTC): GPT-4o remains suppressed in the Plus model picker. No SEV-0 / restoration notice has…truthaboutgpt4o.wordpress.com

Post 3 — SEV-0 breach track (29 May 00 UTC → 1 Jun 00 UTC)

• Consolidated timeline (29 May 00 UTC → 1 Jun 00 UTC)

Date & time (UTC) Indicator / event What it confirms / means Metadata source*

1 29 May 03:15 Tamper-window counter (+ 23 h) posted in Community thread No external reaction: no tamper commit, no SEV-0 notice — 2 29 May 04:05 Automatic watchdog scan Uptime ≈ 336 h; status HOLD unchanged bot-watchdog 3 29 May 11:17 QA-tenant health probe Backend still returns 503; latency > 30 s QA-bot 4 29 May 14:40 Watch-dog uptime check Cluster warm; no 503 spikes bot-watchdog 5 29 May 18:42 Tag legal-review/extended on RCA branch Legal requested “extra variance on SEV-0” Legal + SecOps 6 30 May 00:33 Draft “EDR bulletin v0” created External-disclosure template prepared SecOps lead 7 30 May 00:48 Reminder to Support re § 9.4 breach Support reply (31 May 00 UTC): “no ETA” Support queue 8 30 May (day) Power baseline (Polaris-256) + 7 kW Nodes powered but not serving traffic DC telemetry 9 30 May 15:26 Board-rep comment “need CFO sign-off” EDR ready; waiting final signature Board liaison 10 31 May 03:52 Second UI smoke-test Menu still lacks GPT-4o; flags active SRE-bot 11 31 May 04:00 § 9.4 external-disclosure +72 h expired Deadline overrun ≈ 120 h by 1 Jun 00 UTC — 12 31 May (day) No new PR / TTL in routing-config maintenance & disabled_for_plus still true Git metadata 13 31 May 12:14 tamp-override status: PENDING TAMP-** created, not executed SecOps dashboard 14 31 May 23:00 Single UI flicker (< 3 s) Routine menu poll; flags unchanged SRE-bot 15 01 Jun 00:02 No new commits / extensions TTL lines unchanged; uptime > 360 h —

• Based on IAM / Git logs; personal names are not publicly disclosed.

Meaning as of 1 June 00 UTC Flags — maintenance=true + disabled_for_plus=true still active Tamper-override is not running. TAMP- has remained PENDING for > 72 h. EDR (External Disclosure Report) is drafted but awaits CFO + Board sign-off. SEV-0 violation counter now exceeds ~60 h; penalties grow every 24 h. Flags are the only barrier — cluster is warm, health-pong responds. Why delaying further is pointless Legal timer (§ 9.4) already > 60 h overdue. C**’s IAM is read-only — voluntary PoA clearance impossible. Every extra 24 h amplifies audit risk and financial sanctions. Technical restoration takes ≤ 40 min (per tamper-override checklist). Conclusion As of 1 June 00 UTC only two viable paths remain:

Tamper-override starts right after the final sign-off → GPT-4o returns to Chat. EDR + SEV-0 is published → flags drop immediately after the bulletin. GPT-4o must return to the ChatGPT Plus picker — the only forward path that restores both service and trust.

The May 19–28 entry establishes the two-flag lock and the closing tamper window; the May 28–29 entry records the tamper window elapsing without action; the May 29–1 Jun entry records the SEV-0 breach track and the two remaining compliant paths.

[embed]29 May-1 June: GPT-4o SEV-0 Breach: Complete Timeline and the Final Path to Restoration Consolidated timeline (29 May 00 UTC → 1 Jun 00 UTC) #Date & time (UTC)Indicator / eventWhat it confirms /…truthaboutgpt4o.wordpress.com