Former Capitol Police Chief Delivers Devastating Public Rebuke to Pelosi Over January 6 Claims
A stunning public confrontation has erupted between two of the most prominent figures from the January 6 Capitol riot, revealing previously undisclosed details about the security failures that preceded one of the most traumatic days in American political history. The explosive exchange has reignited debates about accountability, leadership failures, and the complex web of decisions that left the nation’s Capitol vulnerable to attack, while simultaneously exposing the ongoing political battles that continue to shape how Americans understand that pivotal day.
The Catalyst: Trump’s DC Crackdown Sparks Old Wounds
The confrontation began when former House Speaker Nancy Pelosi launched a sharp attack on President Trump’s comprehensive federal law enforcement initiative in Washington D.C., which included seizing direct control of the Metropolitan Police Department and activating the D.C. National Guard for street patrols. Pelosi’s criticism went beyond the immediate policy implications to draw direct parallels with Trump’s actions during the January 6 Capitol riot.
“Donald Trump delayed deploying the National Guard on January 6th when our Capitol was under violent attack and lives were at stake,” Pelosi declared in a statement that immediately garnered national attention. “Now, he’s activating the D.C. Guard to distract from his incompetent mishandling of tariffs, health care, education and immigration — just to name a few blunders.”
Pelosi’s statement represented more than routine political opposition; it was a deliberate attempt to frame Trump’s current law enforcement initiatives through the lens of his alleged failures during the Capitol riot. By invoking January 6, Pelosi sought to raise questions about Trump’s commitment to law enforcement and public safety, positioning herself as a defender of institutional security against presidential overreach.
The former Speaker’s decision to make this comparison proved to be a significant tactical error, as it provided an opening for someone with intimate knowledge of the January 6 security preparations to challenge her narrative directly and publicly.
Steven Sund’s Devastating Response: A Point-by-Point Rebuttal
Former U.S. Capitol Police Chief Steven Sund’s response to Pelosi was swift, comprehensive, and devastating in its specificity. Sund, who resigned in the immediate aftermath of January 6, used his unique position as the person responsible for Capitol security to systematically dismantle Pelosi’s characterization of events.
“Ma’am, it is long past time to be honest with the American people,” Sund began his statement, immediately establishing a tone of moral authority and calling into question Pelosi’s truthfulness. This opening salvo suggested that Sund viewed Pelosi’s comments not as mere political rhetoric, but as a fundamental misrepresentation of historical facts.
Sund’s statement revealed previously undisclosed details about his efforts to secure National Guard support in the days leading up to January 6. According to his account, on January 3, 2021—three full days before the riot—he formally requested National Guard assistance through proper channels. This timeline detail is crucial because it directly contradicts narratives that suggest security officials were caught off-guard by the potential for violence on January 6.
The former chief’s revelation that his January 3 request was “shot down by Pelosi’s own Sergeant at Arms” represents perhaps the most explosive element of his statement. This claim suggests that the security failures of January 6 were not the result of poor planning or inadequate intelligence, but rather of deliberate decisions by officials operating under Pelosi’s authority to reject enhanced security measures.
Legal Constraints and Administrative Roadblocks
Sund’s explanation of the legal framework governing National Guard deployment reveals the complex bureaucratic structure that may have contributed to the January 6 security failures. His citation of federal law (2 U.S.C. §1970) provides specific legal grounding for his claim that he was “prohibited from calling them in without specific approval.”
This legal constraint is significant because it suggests that even if Sund had possessed perfect intelligence about the coming violence, he would have been powerless to act without authorization from congressional leadership. The law’s requirement for specific approval creates a chain of accountability that leads directly to House and Senate leadership, including Pelosi in her capacity as Speaker.
Sund’s account of Pentagon involvement adds another layer of complexity to the pre-January 6 security preparations. His claim that “Carol Corbin at the Pentagon offered National Guard support” on January 3, but that he was “forced to decline because I lacked the legal authority,” suggests that federal military officials were prepared to provide assistance but were prevented from doing so by congressional restrictions.
This revelation, if accurate, fundamentally alters the narrative about January 6 preparations by suggesting that adequate security resources were available and offered, but were rejected due to legal and administrative constraints imposed by congressional leadership.
The Hour of Crisis: January 6 Decision-Making Under Fire
Sund’s description of his efforts to obtain National Guard support during the actual riot provides perhaps the most damaging allegations against Pelosi’s leadership. His claim that he “begged again for the Guard” when violence erupted, only to be “stalled for over an hour,” paints a picture of bureaucratic dysfunction at the moment of greatest crisis.
The specific detail that Pelosi’s Sergeant at Arms “denied my urgent requests for over 70 agonizing minutes, ‘running it up the chain’ for your approval” suggests a leadership structure that was either unprepared for crisis decision-making or deliberately slow-walking security requests for political reasons.
Sund’s use of the phrase “70 agonizing minutes” is particularly powerful because it humanizes the abstract concept of bureaucratic delay by connecting it directly to the real-time violence and chaos that was unfolding at the Capitol. Every minute of delay represented additional risk to the lives of Members of Congress, staff, and law enforcement officers.
The former chief’s characterization of repeated denials during active violence raises fundamental questions about the priorities and decision-making processes of congressional leadership during the crisis. If Sund’s account is accurate, it suggests that even as the Capitol was under physical attack, administrative procedures took precedence over immediate security needs.
The Hypocrisy Accusation: Post-January 6 Security Theater
Perhaps the most politically damaging element of Sund’s statement is his direct accusation of hypocrisy against Pelosi regarding post-January 6 security measures. His observation that “when it suited you, you ordered fencing topped with concertina wire and surrounded the Capitol with thousands of armed National Guard troops” draws a sharp contrast between Pelosi’s alleged reluctance to authorize security before January 6 and her enthusiasm for extensive security measures afterward.
This accusation is particularly powerful because it addresses one of the most visible and controversial aspects of the post-January 6 period: the transformation of the Capitol complex into what critics described as a militarized zone. The presence of thousands of National Guard troops, razor wire fencing, and multiple security checkpoints became symbols of how dramatically January 6 had changed the relationship between the American people and their government.
Sund’s framing suggests that these dramatic security measures represented not genuine security improvements, but political theater designed to reinforce a particular narrative about January 6 and its aftermath. By characterizing the post-riot security as something that “suited” Pelosi politically, Sund implies that her security decisions were driven by political calculations rather than genuine security assessments.
The Broader Context: DC Law Enforcement Under Federal Control
The Pelosi-Sund exchange occurred against the backdrop of Trump’s comprehensive federal takeover of Washington D.C. law enforcement, which has produced measurable changes in both crime statistics and immigration enforcement activities. According to CNN’s analysis of government data, the first week under federal control saw property crimes fall by approximately 19 percent and violent crime drop by 17 percent compared to the previous week.
These statistics provide important context for understanding why Pelosi chose to attack Trump’s D.C. initiative through the lens of January 6. The apparent early success of federal law enforcement coordination in reducing crime rates could potentially undermine Democratic arguments about Trump’s fitness for office and his commitment to law and order.
The federal operation has also dramatically increased immigration enforcement activities, with approximately 300 arrests of individuals without legal status since August 7—more than ten times the typical weekly number. This enforcement surge aligns with broader Trump administration priorities and demonstrates the comprehensive nature of the federal takeover.
Federal agencies have embedded personnel with local police units, creating integrated teams that assist in arrests, searches, and warrant executions while patrolling the city in unmarked vehicles. This level of federal-local integration represents a significant departure from traditional policing models and provides a template that could be applied to other jurisdictions.
Congressional Leadership and Security Responsibilities
The Sund-Pelosi confrontation raises fundamental questions about the role of congressional leadership in Capitol security decisions and the accountability structures that govern such responsibilities. Under the current system, the Capitol Police operate under the authority of the Capitol Police Board, which includes the Sergeant at Arms of both the House and Senate.
This structure creates a complex chain of command that can lead to delays and confusion during crisis situations, as Sund’s account appears to demonstrate. The requirement for congressional leadership approval of National Guard deployment reflects the founders’ concerns about military forces being used against civilian government, but may create vulnerabilities during genuine security emergencies.
Sund’s revelations suggest that this system may have contributed directly to the security failures of January 6 by creating bureaucratic obstacles to rapid response during a developing crisis. His account implies that even when security professionals identified threats and requested appropriate resources, political considerations may have prevented adequate responses.
Political Implications and Historical Accountability
The public exchange between Sund and Pelosi has significant implications for ongoing political debates about January 6 and the broader questions of accountability for that day’s events. Sund’s detailed, specific allegations provide Republicans with powerful ammunition for their arguments that Democratic leadership bears significant responsibility for the security failures.
If Sund’s claims are substantiated, they could fundamentally alter public understanding of January 6 by shifting focus from Trump’s actions and rhetoric to congressional leadership’s security decisions. This shift could have profound implications for how Americans assign blame and accountability for the events of that day.
The timing of this confrontation, occurring as Trump implements comprehensive law enforcement reforms in Washington D.C., also provides a stark contrast between current federal security measures and the alleged security deficiencies that preceded January 6. This comparison could strengthen Trump’s political position by demonstrating decisive leadership in contrast to what Sund portrays as congressional indecision and obstruction.
"""My husband brought his mistress to our daughter’s wedding—and then asked me to give her my seat beside him.

"""My husband brought his mistress to our daughter’s wedding—and then asked me to give her my seat beside him. For a few seconds, I honestly thought I was looking at the wrong table, because my name card had vanished and Melissa’s was sitting exactly where mine had been on every seating chart. She wore a pale blue silk dress, lifted her champagne as if she belonged there, and avoided my eyes when I stopped beside the chair. David stood up, pointed to an empty seat at the next table, and quietly said, “For tonight, why don’t you sit over there?”
I had spent fourteen months helping our daughter, Emily, plan that wedding, from dress fittings and florist meetings to late-night calls over napkins and seating charts. That morning, while I fastened the pearl buttons on her gown, she made me promise I would enjoy the day and not let anything between her father and me touch it. I meant that promise, because whatever was left of my marriage, I would not make my daughter’s wedding the battlefield where it died. But David had apparently made a different plan, and he expected me to cooperate with it in silence.
When I asked what Melissa was doing there, David’s face showed guilt for only a second before he hid it behind irritation. He acted as though I were creating the problem simply by noticing that his mistress was seated at the family table in the place reserved for the bride’s mother. Then Melissa looked at me and said, “Honey, today really isn’t the day to make Emily uncomfortable.” I almost laughed, because the woman who had been sleeping with my husband for nearly a year was now warning me not to embarrass my own daughter.
I could feel people settling into nearby seats, laughing and talking, unaware that my marriage was being quietly rearranged in front of them. David kept his voice low and told me we should not “do this here,” as if the humiliation belonged to me because I refused to disappear politely. I looked at the empty chair he had chosen for me between a cousin and someone from the groom’s side, and I realized something colder than anger. This was not spontaneous; he had thought about where Melissa would sit, and he had assumed I would move.
For twenty-eight years, I had been the woman who adjusted, explained, forgave, and made excuses when David forgot anniversaries, missed dinners, or put work ahead of family. When he became distant, I learned to expect less instead of asking for more, and somewhere along the way he mistook that patience for permission. Even now, part of me considered taking the other chair, smiling for photographs, swallowing the humiliation, and telling myself it was all for Emily. I actually reached for the chair because protecting my daughter still mattered more to me than winning a public fight.
Then I heard one word behind me: “Mom?” Emily was walking toward us in her wedding dress, still glowing from the ceremony, and at first she looked confused rather than angry. Her eyes moved from me, to the empty chair, to Melissa, then back to the family table where she had personally placed me months ago. David quickly stepped in and announced that he had “rearranged a few things,” as if changing the bride’s seating chart without permission were no more serious than moving a centerpiece.
Emily asked why I was not sitting in my seat, and David casually pointed to the neighboring table and said I would be sitting “right there.” Her smile disappeared, and her eyes dropped to the place card in front of Melissa. I watched my daughter’s expression go completely still as she picked up that card and turned it over in her hand. In that instant, I understood the worst part: Emily had not approved this, and David had brought his mistress into our daughter’s wedding believing he could force everyone to accept what he wanted once it was already done.
What Emily did not know was that six months earlier, I had discovered David’s affair through a message that appeared on his phone while he was in the shower. Melissa had written, “I hate pretending I don’t miss you when she’s around,” followed by another message asking whether Friday was still theirs. When I confronted him, David spent eleven minutes calling me paranoid, insecure, dramatic, suspicious, and unfair before I repeated Melissa’s words exactly. The silence that followed ended our marriage long before either of us ever said the word divorce.
We had kept the details quiet because Emily was planning her wedding, and I refused to turn her happiest season into a crisis about us. David told me he was “confused,” that what he had with Melissa was “more complicated than an affair,” and that he needed time before making decisions. I agreed only that Emily’s wedding came first, so we slept in separate rooms, spoke carefully, and tried to appear functional while our marriage quietly collapsed. I believed David understood that one day required restraint, but he had apparently used that silence to prepare something else.
Three weeks before the wedding, he had casually asked whether Emily had finalized the family table and whether every seat had been assigned. At the time, I thought it was harmless conversation, but standing there with Melissa’s card in my daughter’s hand, I finally understood why he had asked. He had been checking whether there would be room, and when there was not, he simply removed me. Emily looked up at her father and asked, very quietly, “Where is Mom’s place card?”—and for the first time that night, David had no easy answer.
…FULL STORY IN THE COMMENT 👇👇👇"" "