The dependency chain problem
EO 14365 created a 4-step sequential lock: DOJ list (§3) → Commerce eval (§4) → NTIA notice (§5a) → FCC proceeding (§6). The §3 list is the legal predicate for everything downstream. It was due ~Jan 10 and never published. Every gate below it stays frozen at step one.
The slipping guidance deadline
Four sequentially slipped commitments: Mar 11 (NTIA staff) → Mar 26 (per Rep. Dingell) → "two months" / ~Jun 22 (Lutnick, Apr 22) → "this summer" (Roth, Jun 30). Each vaguer than the last.
The $21B framing trap
"We've executed universal broadband for $21B" conflates grant-agreement execution with deployment. Homes are connected in only two states. GAO's open recommendation that NTIA better communicate program financial sustainability to Congress (Jun 22) sits directly against the savings narrative.
Two speeds, one order
The EO's litigation arm moved fast and off-script: DOJ intervened behind xAI against Colorado's SB 24-205 on Apr 24, the first federal bid to void a state AI law, before Commerce ever published the §4 "onerous" list. Colorado then repealed the law itself (May 14). But the BEAD-conditioning chain at left, the part that actually gates the $21B, never fired. Going around the sequence in court did not unlock the money.
▓ The October 1 wall
Three regime shifts land on one date: OMB's 2 CFR 200 rewrite takes effect; FY2027 begins; NTIA's grants system cuts over to eRA/GEMS, a transition delayed since FY2023 (OIG-25-025-A) onto a platform never used for BEAD, via an interface not yet built. Any nondeployment award not executed before Oct 1 meets all three at once. "This summer," at its outer edge, leaves only days of margin.