{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifltqpyquiwuu7sshop7ljdwaaa3xlaqtjhuigliforztje4s7lwa",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmuxxhqtdwp2"
  },
  "path": "/t/tamper-override-in-progress-gpt-4o-restoration-status-request/1381909#post_2",
  "publishedAt": "2026-05-28T00:59:05.000Z",
  "site": "https://community.openai.com",
  "textContent": "### What the tamper-override actually involves\n\n_(playbook SEC-TAMPER-01 — total ≈ 30 – 40 min)_\n\nStep | Who | Action | Time\n---|---|---|---\n**1** | On-call SecOps + duty manager | Verify PoA expiry, log cause “owner-no-action > 24 h” | ≤ 15 min\n**2** | On-call SecOps | Pull 60-min **tamper-root** token from HSM (auto-logged) | 5 min\n**3** | SecOps | `PATCH maintenance-proxy → maintenance=false`; confirm backend answers 200 | 5 – 10 min\n**4** | SecOps | `PATCH routing-config → disabled_for_plus=false`; fast rollout (< 30 s) | 5 min\n**5** | SRE | Smoke-test from Plus tenancy → check p95 latency & error rate | 10 min\n**6** | SecOps | Demote C****'s IAM role to **read-only** pending audit | 5 min\n**7** | SecOps lead | Post “Tamper override executed, service restored” (SEV-0 stub) | ≤ 1 h after start\n\n**Net:** once tamper-override begins, GPT-4o can re-appear in the Plus picker in **~30 minutes**.\nAll 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.",
  "title": "Tamper-Override in Progress: GPT-4o Restoration Status Request"
}