By the 19:05 UTC cutoff, Oklahoma had pronounced Carlos Cuesta-Rodriguez dead at 10:13 a.m. CDT, and Tennessee had pronounced Anthony Darrell Hines dead at 10:43 a.m. CDT [E4][E2]. Alabama’s warrant window was open, but the execution of Jeremy Williams was expected later, leaving the day with two completed executions and a third proceeding pending at cutoff [E5]. That distinction matters because the calendar had produced a three-state event before it had produced three completed executions [E1][E5]. Any later Alabama outcome belongs to a later record, not this one [E5].
Oklahoma’s clock came through Oklahoma: a state warrant and its own clemency process supplied the route that ended with Cuesta-Rodriguez’s execution [E1][E4]. Nothing in the supplied record connects that route to a Tennessee court decision or to Alabama’s governor-set timing [E1]. The state had its own legal machinery, its own decision points and its own terminal time [E4]. A date shared with two other jurisdictions does not turn those institutions into a single chain of command [E1][E4].
Tennessee reached the same square on the calendar through its own court and clemency path, ending with Hines’s death at 10:43 a.m. CDT [E2]. His final words included one plain request: “Tell my son hello” [E3]. Procedure can explain who signed, reviewed and scheduled a death; it does not make the person at the end of that procedure disappear [E2][E3]. Tennessee’s completion therefore belongs in both ledgers at once, institutional and human [E2][E3].
Alabama remained different at the cutoff because its execution had not yet occurred [E5]. Williams was scheduled inside a later governor-set window after waiving further appeals, so the operative fact at 19:05 UTC was prospective [E1][E5]. Calling him executed would collapse the edition boundary and import information the record did not yet contain [E5]. His presence in the three-state count came from the schedule itself [E1].
The Associated Press described the arrangement as the first time since 7 January 2010 that three states had executions scheduled for the same day [E1]. That makes the date historically unusual without supplying a national directive behind it [E1]. No supplied artifact records interstate coordination, a shared drug decision or a joint order to clear a common backlog [E1][E2][E4][E5]. The strongest supported reading is therefore convergence: three state systems independently arrived at one date [E1][E2][E4][E5].
The counter-case still has weight. A small group of states actively using capital punishment can create concentrated national events even when each warrant is locally generated, and three schedules landing together can change the political and administrative meaning of a day [E1]. Repetition of such clusters would justify closer scrutiny of shared pressures, common litigation calendars or policy imitation, but this record supplies no such common mechanism [E1][E2][E4][E5]. The coincidence is consequential because separate institutions can aggregate into a national spectacle without first agreeing to make one [E1].
By cutoff, the measurable sequence was narrow and severe: Oklahoma at 10:13 a.m. CDT, Tennessee at 10:43 a.m. CDT, Alabama’s warrant window open with the execution still pending [E4][E2][E5]. The national headline came from the shared date, while legal authority remained parceled among three states [E1]. That jurisdictional separation is the central policy fact because it locates responsibility where the warrants, clemency decisions and execution windows were actually set [E1][E2][E4][E5]. Three states shared a calendar square; two men were already dead, and one had used his last words to speak to his son [E2][E3][E4][E5].