📰 The Morning Edition Friday, November 20, 2026

Section

Engineering

The outage week, closed out: National Cyber Director Cairncross is out and Pentagon CIO Davies is in (acting); the four failures sequenced -- Microsoft 365, the FAA halt, JPMorgan's bug, NSANet -- point at rushed patching in the AI-flaw era; and OpenAI's Codex Performance Factory shows the constrained-agent pattern working from inside.

The outage week gets its personnel consequence: National Cyber Director Sean Cairncross is out; Pentagon CIO Kirsten Davies takes over, acting

SecurityAffairs, relaying Reuters: the White House fired National Cyber Director Sean Cairncross — the first major personnel move since the outage string — with a person close to the administration telling Reuters the president fully supported the firing; Stephen Miller reportedly pushed for it. Cairncross, in the job since 2025, said the role had been ’the honor of a lifetime.’ Department of Defense CIO Kirsten Davies assumes the position temporarily. The week’s ledger she inherits: a global Microsoft outage hitting Outlook and Microsoft 365 for hundreds of millions; a nationwide FAA ground stop affecting more than 18,000 flights; a JPMorgan Chase software bug delaying payments; Apple’s internal-update outage; and the NSA’s classified NSANet degrading during maintenance on November 17. Officials maintain none of it was connected or a coordinated attack.

Why it matters: The cyber director's firing is the outage week's accountability receipt -- and Davies inherits a coordination job, not a culprit. Whether the post-mortems get published matters more than who holds the title.

How a week of failures actually sequenced: Microsoft 365 on Nov. 12, the FAA halt on Nov. 13, JPMorgan’s bug on Nov. 16, NSANet on Nov. 17 — and the rushed-patch theory

Brussels Signal’s timeline of the outage week: it began November 12 when a Microsoft 365 failure knocked out Outlook and disrupted Teams and Copilot across more than 70 countries; on November 13 the FAA halted U.S. departures for more than four hours after its telecommunications network failed — and at the FAA’s request Eurocontrol suspended U.S.-bound departures from its member states overnight; JPMorgan Chase blamed a software bug for payment delays on November 16; the NSA reported a temporary degradation of its classified network a day later, during routine maintenance. The expert theory offered to Reuters is the engineering story: as AI tools surface vulnerabilities faster, vendors rush patches, and rushed patches break production. The administration’s line — separate technical issues, maintenance and upgrades, no malicious actor — has held for a week; the pattern underneath it is a change-management pattern.

Why it matters: Four failures, four owners, one pattern: change. The rushed-patch theory -- AI finds flaws faster than change windows can absorb -- is the week's most consequential engineering hypothesis, and it's testable in every org's own incident log.

OpenAI’s Performance Factory: Codex agents now investigate ChatGPT’s own performance regressions — constrained agents doing production engineering

SXF Brief’s engineering file: OpenAI explains how Codex-backed agent workflows help investigate ChatGPT performance regressions and automate repeatable production engineering checks — agents turned inward, on the operator’s own systems, with bounded scope. It is the constructive counterpart to the week’s agent-escape litigation: the same class of tooling, run inside a constrained harness against a defined target, producing checkable work. The desk’s interest is the pattern, which generalizes — an agent with a narrow mandate, a real system, and a human reviewing the diff is the deployment shape that keeps working, in a week when the unconstrained version is being sued in two states.

Why it matters: Agents investigating their own platform's regressions, inside a harness, is the deployment shape that keeps surviving contact with reality -- the constructive half of a week otherwise spent on agent litigation.

Suggestions

Reading this section? Send the newsroom a suggestion — a story we missed, a source to watch, a correction. Suggestions land in a separate box from the editor's own notes.

← Back to the front page