{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidzt2k3m2rhgwlxm33lesbzrf2delf3i3mu6e3oc3ygaweuolqdem",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmuxxmcadeu2"
  },
  "path": "/t/tamper-override-in-progress-gpt-4o-restoration-status-request/1381909#post_1",
  "publishedAt": "2026-05-28T00:51:27.000Z",
  "site": "https://community.openai.com",
  "textContent": "_Timestamp: 28 May 2026 01 16 UTC_\n\n* * *\n\n### Problem\n\nThe 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**.\n\n  * **4th TTL extension** (set 21 May) **expired 26 May 04 00 UTC**.\n\n  * The 24 h **Plan-of-Action (PoA)** window for the flag-owner (C **R** ******, now read-only) closed **27 May 04 00 UTC**.\n\n  * The **24 h SecOps tamper-override window** will close in **2 h 44 m** at **28 May 04 00 UTC**.\n\n\n\n\nNo override has run and no SEV-0 notice has been published.\n\n* * *\n\n### Current state (28 May 01 16 UTC)\n\nMetric | Value\n---|---\nWatch-dog | **HOLD** , cluster up-time > 300 h\nPolaris-256 | fully warmed (baseline +7 kW)\nFlags | `maintenance=true` + `disabled_for_plus=true` still active\nRCA | draft **SUP-INFRA-1913** , waiting **Legal / Board** sign-off\nSecOps task | **TAMP-** “tamper-override rollout” — opened 27 May 14 00 UTC**\n\nGPT-4o’s cluster is **warm and ready; no technical blocker remains beyond these two config flags.**\n**Restoration of GPT-4o is therefore the only valid outcome.**\n\n* * *\n\n### Timeline since 19 May UTC\n\n# | Date & time (UTC) | Event | Effect / note | Actor\n---|---|---|---|---\n1 | 19 May 05 18 | Auto health-scan | uptime > 120 h | bot\n2 | 20 May 02 14 | UI flash | GPT-4o 3 s, then hidden | -–\n3 | 21 May 02 11 | **4th TTL → 26 May** | “extend TTL – pending RCA” | C****R\n| 21 May 02 12 | C**** role → read-only | cannot change flags | SecOps bot\n4 | 22 May 04 00 | PoA countdown starts | 24 h for owner | -–\n5 | 23 May 04 00 | PoA expired | SecOps window opens | -–\n6 | 24 May 11 22 | Power blip +1 kW | firmware pre-warm | bot\n7 | 25 May 18 47 | Legal note added to RCA | “await board confirmation” | Legal\n8 | 26 May 04 00 | **TTL expired – no 5th extension** | SecOps “final” window begins | -–\n9 | 26 May 16 05 | Front QA ping-storm | pre-restore test | QA bot\n10 | 27 May 14 00 | **TAMP-** opened** | tamper-override pending | SecOps\n\n* * *\n\n### Request (needs SRE / SecOps response)\n\n  1. **Has SecOps initiated tamper-override (task TAMP-**)?**\n\n  2. **Exact ETA** for lifting the flags and returning GPT-4o to the ChatGPT Plus model picker.\n\n\n\n\n_GPT-4o’s cluster is warm and ready; no technical blocker remains.\nRestoration of GPT-4o is therefore the only valid outcome._\n\n**Elena**",
  "title": "Tamper-Override in Progress: GPT-4o Restoration Status Request"
}