When ICE Put an American Soldier in a Cell: The Case for Abolishing the Agency

George Retes served the United States in uniform. He deployed to Iraq as an American soldier. He came home, went to work, raised a family and lived his life as an American citizen.

Then federal immigration agents treated him as though his citizenship, his constitutional rights and his freedom could simply be ignored.

Retes's case should force Americans to confront a disturbing question: What good is the Constitution if federal agents can seize an American citizen, hold him for approximately three days without charges or a judicial hearing, deny him access to his family and an attorney, and then release him without ever charging him with a crime?

Retes has taken the federal government to court.

His federal lawsuit, filed February 18, 2026, alleges violations arising from his arrest and approximately 72-hour detention following an immigration raid in California. The case remains active, meaning a court has not yet entered a final judgment establishing liability.

But the underlying facts are extraordinary enough.

An American Citizen Caught in an Immigration Raid

On July 10, 2025, Retes encountered a federal immigration operation while trying to reach his job as a security guard at Glass House Farms in Camarillo, California.

Retes is an American citizen and Army veteran who served in Iraq. 

According to Retes and his lawsuit, he identified himself as an American citizen, veteran and employee and attempted to explain that he needed to get to work.

What followed, according to his complaint, was not a routine verification of identity.

Federal officers broke his vehicle window. He was pepper-sprayed, pulled from his vehicle and forced to the ground. Retes alleges that an officer placed a knee on his neck while another placed a knee on his back.

He was taken into federal custody.

Then came the part of this case that should alarm Americans regardless of their position on immigration.

Retes wasn't an undocumented immigrant.

He wasn't someone whose immigration status needed to be adjudicated.

He was an American citizen.

Three Days Without Charges

Retes was arrested at approximately 2:30 p.m. on July 10 and remained detained until the afternoon of July 13—roughly 72 hours, according to his federal complaint.

The complaint alleges that throughout that detention he received no phone call and no hearing before a judge. His attorneys contend officials continued holding him without probable cause or a warrant and failed to provide adequate procedures for determining that there was no legitimate basis to continue imprisoning him.

His attorneys also say he was denied access to an attorney and initially prevented from showering despite still being contaminated by pepper spray and tear gas.

His family did not know what was happening to him.

His young daughter's birthday came while her father was sitting in federal custody.

And when the government finally released him?

No criminal charges were filed against him.

That fact deserves to be repeated.

The United States government took an American citizen into custody during an immigration operation, held him for approximately three days, and ultimately released him without charging him with a crime.

DHS Has a Different Story

Fairness requires acknowledging the government's account.

Department of Homeland Security officials have alleged that Retes became violent, refused officers' commands and blocked law-enforcement vehicles. DHS said he was arrested for assault.

Retes denies those allegations.

But there is an unavoidable fact:

Retes was ultimately released without criminal charges.

If the government believed it possessed evidence establishing that this American citizen criminally assaulted federal officers, prosecutors had the ability to bring charges and attempt to prove that allegation in court.

That did not happen.

An accusation issued by an executive agency is not a conviction.

And it is certainly not a substitute for due process.

This Is Exactly Why the Constitution Exists

The Constitution was not written only for people whom government officials like.

It was written precisely because government possesses extraordinary power.

The Fourth Amendment protects people against unreasonable searches and seizures.

The Fifth Amendment guarantees that the federal government cannot deprive a person of life, liberty or property without due process of law.

Retes's lawsuit squarely invokes those protections.

His complaint alleges that federal officials deprived him of physical liberty without probable cause, prolonged his detention without legitimate justification and failed to provide him with appropriate judicial process.

Those allegations have not yet been finally adjudicated.

But if proven, they describe precisely the kind of arbitrary government detention the Constitution is designed to prevent.

And citizenship should not have been the only thing protecting Retes.

Constitutional protections extend to noncitizens in many circumstances as well.

Immigration enforcement does not create a Constitution-free zone.

The Uniform Makes This Case More Striking—But Not More Constitutional

Retes's military service makes the story especially jarring.

He served his country in Iraq.

Then he returned home and encountered the coercive power of that same federal government.

But Americans should resist drawing the wrong lesson from that fact.

Retes did not deserve constitutional protection because he was a veteran.

He deserved it because the Constitution restrains the government.

A construction worker deserves constitutional protection.

A restaurant employee deserves it.

An immigrant is entitled to the constitutional protections that apply to them.

A protester deserves protection from unconstitutional government action.

And an American veteran certainly does.

The government's obligation to obey the Constitution does not disappear depending upon the popularity, occupation or immigration status of the person standing in front of an officer.

Immigration Enforcement Cannot Mean Unlimited Government

Supporters of aggressive immigration enforcement can legitimately argue that the federal government has a responsibility to enforce immigration law.

That policy debate is separate from what happened to George Retes.

The question here is much simpler:

Must immigration agents obey the Constitution while enforcing immigration law?

The constitutional answer is yes.

The government cannot justify unlawful conduct merely by pointing to the importance of its mission.

Police officers cannot ignore the Fourth Amendment because fighting crime is important.

Federal investigators cannot abandon due process because national security is important.

Immigration enforcement deserves no special exemption from constitutional government.

This Case Strengthens the Argument That ICE Should Be Abolished and Replaced

George Retes's case should force Congress to confront a larger question:

Has ICE become an institution whose structure and methods create an unacceptable threat to constitutional liberty?

There is a powerful argument that the answer is yes.

ICE itself was created in 2003 during the federal reorganization that followed the September 11 attacks.

Abolishing ICE would not require abolishing immigration law.

It would not require abandoning the border.

And it would not require abandoning the enforcement of lawful removal orders.

Congress can dismantle an agency while transferring legitimate governmental responsibilities elsewhere.

That distinction matters.

The choice is not between ICE exactly as it exists today and no immigration enforcement whatsoever.

Congress determines how the executive branch's immigration-enforcement machinery is structured.

If an enforcement structure repeatedly creates unacceptable constitutional risks, Congress has the authority to replace that structure while continuing to enforce the law.

George Retes's experience belongs at the center of that debate.

Government Power Must Have Consequences When It Is Abused

Retes is now asking the judicial system to provide the accountability he says federal officers denied him.

Whatever the eventual outcome of his lawsuit, his case presents a principle much larger than immigration politics.

A badge is not a license to disregard the Constitution.

A federal agency is not above the Bill of Rights.

An immigration operation does not suspend due process.

And an American citizen should never have to sit in federal detention wondering when—or whether—the government will provide a lawful justification for keeping him there.

George Retes once wore the uniform of the United States and served his country overseas.

Years later, he found himself fighting another battle—this time against his own government and through the American court system.

The principle at stake could not be more fundamental:

Nobody should be above the law.

That principle applies to citizens.

It applies to immigrants.

It applies to presidents.

And it applies to ICE.

Congress can enforce America's immigration laws without preserving one particular federal agency.

The case for abolishing ICE is not an argument for lawlessness.

It is an argument that immigration enforcement itself must be subordinate to the Constitution.

ICE should be dismantled and its legitimate immigration-enforcement responsibilities transferred to institutions operating under stronger safeguards, transparency, judicial oversight and accountability.

Because a government powerful enough to disregard one person's constitutional rights is powerful enough to disregard anyone's.

And when the government takes away a person's freedom, the Constitution is not an inconvenience standing in its way.

The Constitution is the law standing in its way.

The Smearing of Alex Pretti: False Story That Slain VA Nurse Was Fired Traced to Vietnam-Based ‘Viet Spam’

MINNEAPOLIS — Alex Pretti was an intensive care nurse who cared for American veterans. He was also a 37-year-old U.S. citizen who was fatally shot by federal Border Patrol agents on a Minneapolis street on Jan. 24, 2026.

And almost immediately after his death, another battle began — this one over the truth about who Alex Pretti was.

A disturbing story began circulating across Facebook claiming Pretti had been fired from his nursing job months before his death because of allegations of inappropriate or predatory behavior toward patients.

There was just one major problem.

The story wasn't true.

Fact-checkers investigating the allegation found no evidence that Pretti had been fired for misconduct. Instead, evidence showed that he remained an ICU nurse at the Minneapolis VA Medical Center at the time of his death.

Even more troubling, investigators traced the false story not to a hospital, police report or legitimate American news organization, but to what fact-checkers described as a Vietnam-based network pumping AI-generated misinformation into American social media.

The ‘Viet Spam’ Connection

Lead Stories traced one version of the fabricated story to BuzzReport247.com and reported that it was promoted through Facebook pages managed from Vietnam.

The fact-checking organization calls this growing phenomenon “Viet Spam” — networks that use artificial intelligence, fake or misleading Facebook pages and sensational headlines to generate viral stories aimed largely at American and European audiences.

The formula is straightforward: manufacture an emotionally explosive story, attach it to a recognizable person or breaking news event, push it through social media and collect advertising revenue from people clicking the link.

In Pretti's case, the misinformation appeared almost immediately after his killing.

The fabricated article claimed that Pretti had worked at “Lakeshore Medical Center” and had been terminated following complaints from patients' families.

But Pretti didn't work there.

He worked at the Minneapolis VA Medical Center, caring for veterans in its intensive care unit.

The bogus story also quoted a supposed hospital executive named “Dr. Elena Vasquez.”

Fact-checkers found no evidence that this supposed executive had anything to do with Pretti's actual employer.

The false article couldn't even get Pretti's age right. It described him as 42. He was 37.

Pretti Was Still Working at the VA

Evidence from multiple independent sources directly contradicts the claim that Pretti had been fired.

The union representing federal employees identified Pretti as one of its members and an ICU nurse at the Minneapolis VA.

His colleagues described working with him there.

Patients described being treated by him.

A nursing student described spending months working alongside Pretti during a capstone preceptorship at the Minneapolis VA.

Pretti also held an active and unrestricted registered-nurse license at the time of his death, according to records reviewed by Lead Stories.

The Associated Press reported after his death that Pretti's father, Michael Pretti, described his son as a compassionate person who cared deeply about the American veterans he treated as an ICU nurse.

That is dramatically different from the portrait painted by the fabricated social-media stories.

A Fake Photograph Added to the Deception

The misinformation campaign went beyond fabricated allegations.

One viral version included a photograph supposedly depicting Pretti wearing a pink dress.

That wasn't Alex Pretti either.

Fact-checkers determined that the image appeared to be a digitally altered photograph of another person associated with the reality program “Fishtank Live.”

So the viral story had virtually every hallmark of manufactured internet misinformation: the wrong hospital, a nonexistent or falsely attributed executive, the wrong age, unsupported allegations and even a photograph of somebody else.

Yet it spread.

Pretti Was Killed by Border Patrol Agents

Pretti's death occurred during the Trump administration's immigration-enforcement operation in Minneapolis.

Although the incident has frequently been described online as an “ICE shooting,” the federal officers who fatally shot Pretti were associated with U.S. Customs and Border Protection, including Border Patrol, not ICE.

Pretti was a U.S. citizen.

According to reporting on the shooting, he was legally permitted to carry a handgun. Federal officials initially portrayed him as having threatened officers, but subsequent video evidence and reporting raised serious questions about those early descriptions of what happened.

A preliminary federal report obtained by the Minnesota Star Tribune said a Border Patrol agent and a Customs and Border Protection officer fired their weapons during the confrontation.

The report did not say that Pretti threatened officers with his firearm.

His family strongly disputed the government's early characterization of their son and said Pretti had been attempting to protect a woman during the confrontation.

A Man Dies — Then the Internet Reinvents Him

There is something particularly disturbing about what happened after Alex Pretti's death.

People were entitled to debate his actions, the actions of federal officers, immigration enforcement and the circumstances that led to the shooting.

But disagreement over a controversial police shooting does not justify inventing someone's history.

Pretti's employment record should be a matter of fact, not ideology.

Either he was fired for misconduct or he wasn't.

The available evidence overwhelmingly supports the latter.

Alex Pretti was not fired from the Minneapolis VA for sexual or inappropriate misconduct.

The viral allegations were fabricated.

Snopes rated the firing claim false. Lead Stories independently investigated similar allegations and concluded that the story originated with a Vietnam-based spam operation using AI-generated content.

The misinformation illustrates a much larger problem facing Americans.

Artificial intelligence has made producing convincing fake news extraordinarily cheap. Operators thousands of miles away can manufacture stories about American political controversies within hours, build Facebook pages that resemble news organizations and distribute those stories to an audience already angry enough to share first and ask questions later.

Alex Pretti became an example of the human consequences.

A 37-year-old ICU nurse was shot and killed by federal agents. His death was already controversial enough.

There was no need to invent another story about him.

Whatever Americans ultimately conclude about the circumstances surrounding Pretti's killing, that debate should begin with facts.

And one of those facts is now firmly established:

Alex Pretti was an ICU nurse caring for veterans at the Minneapolis VA Medical Center when he died. He had not been fired for misconduct. The viral story claiming otherwise was fake — and evidence traced its distribution to the Vietnam-based misinformation ecosystem fact-checkers have dubbed “Viet Spam.”

The Vietnam connection is particularly well documented by Lead Stories: it reported that Meta transparency information showed the Facebook page spreading one version was managed from Vietnam and described it as part of a broader AI-driven “Viet Spam” operation. Snopes separately rated the firing allegation false, while AP reporting identified Pretti as an ICU nurse at the Minneapolis VA at the time he was killed. 

Flock Cameras May Be Leaving Some Cities. That Does Not Mean Surveillance Is.

 

Public outrage has finally forced some cities to reconsider Flock Safety license-plate reader cameras. The reason is simple: people learned how easily a system sold as “public safety” can become a tool for tracking ordinary residents.

In Denver, records showed more than 1,400 searches tied to immigration enforcement concerns. That raised serious questions about whether local camera networks were being used, directly or indirectly, to assist federal immigration investigations. The issue was not merely the cameras themselves. It was who could search the data, why they were searching it, and whether the public had any meaningful say in the matter. 

But communities should not assume that canceling a Flock contract ends the surveillance debate.

A new generation of equipment is arriving under a different corporate name: Axon, the company already known to most Americans for Tasers, police body cameras, vehicle cameras and digital evidence storage. Axon now markets systems designed to combine license-plate recognition, live video feeds and camera networks into a single police-viewing platform.

One product, Axon Lightpost, is designed to use existing streetlight infrastructure. According to Axon’s own materials, it can provide automated license-plate recognition and live video streaming while drawing power from a streetlight. Axon says its plate-reading technology can capture plates at speeds up to roughly 155 mph and at distances up to 328 feet in daylight. 

That should prompt a basic question in every city: How many streetlights could quietly become surveillance points before residents are even told?

The concern is not that every camera is automatically unlawful or that police should be denied tools to solve violent crime. Cameras can help investigate shootings, locate missing people and identify stolen vehicles. The concern is that the same systems can create an always-on record of where innocent people travel, who they visit, what neighborhoods they enter and how often they go there.

Axon’s Fusus platform is central to that concern. It is designed to bring feeds from public cameras and participating private security cameras into a real-time operational view for police. In other words, the surveillance system is no longer just a pole-mounted camera. It can become an integrated network connecting license-plate readers, live video, body-camera footage, dispatch information and privately owned cameras. 

That is why the public discussion cannot stop at the name “Flock.”

A city may remove one vendor and still approve another system that gathers similar information, expands the number of cameras, or links police to a wider network of video sources. Longmont, Colorado, for example, moved away from Flock and approved a path toward Axon license-plate readers, though the Axon contract was not yet finalized at the time of reporting. 

Axon’s growing reach extends beyond cameras. The company announced a $625 million acquisition of Carbyne, a cloud-based 911 technology company. The deal is intended to connect emergency calls, dispatch systems, video and other public-safety information within Axon’s broader ecosystem. 

Carbyne’s past investors and founders have drawn scrutiny, including reporting on former Israeli Prime Minister Ehud Barak’s involvement and Jeffrey Epstein’s undisclosed investment through that relationship. But those historical connections, while worth transparent reporting and public scrutiny, are not proof that any American city’s 911 system is being operated for a foreign government or intelligence service. That claim requires evidence, not insinuation.

The real issue is already serious enough without exaggeration: private companies are building deeply connected public-safety systems that can collect, store, search and combine enormous amounts of data about the public.

Before any city signs an Axon, Fusus, Real-Time Crime Center or similar contract, residents deserve clear answers:

• What data will be collected, and for how long?

• Who can search it?

• Can outside agencies access it?

• Can it be used for immigration enforcement?

• Are private-camera owners voluntarily participating?

• Is a warrant required for certain searches?

• Will audit logs be public?

• Who independently checks for abuse?

A company name change is not a privacy policy. A new camera design is not accountability. And “public safety modernization” should never be a phrase used to avoid public oversight.

The question every resident should ask is not simply, “Does my city have Flock cameras?”

It is: “What surveillance system replaced them, who controls it, and what protections exist for the people being watched?”

ICE Detains Minnesota Teen, Labels Him ‘Unaccompanied,’ Then Loses Track of Him

 

The Trump administration’s immigration crackdown has crossed a new and troubling line: federal authorities detained a Minnesota teenager, officially classified him as an “unaccompanied minor,” and then lost him inside the immigration system—while his family, legally present in the United States, desperately searched for answers.

According to reporting by the Minnesota Star Tribune, Immigration and Customs Enforcement (ICE) apprehended the teen and processed him as if he had no parent or legal guardian in the country. That designation triggered a cascade of bureaucratic consequences—transfer to federal custody, restricted communication, and ultimately a breakdown in accountability so severe that even government agencies struggled to determine where the child was being held.

This was not an accident. It was the foreseeable outcome of a policy choice.

A Label That Separates, Not Protects

Under federal law, an “unaccompanied alien child” is defined as a minor with no lawful immigration status who lacks a parent or legal guardian in the United States able to provide care. In this case, that definition did not reflect reality. The teen’s parents were in the U.S. and actively searching for him.

Yet ICE applied the label anyway.

That designation effectively removed the parents from the process, transferring authority to the Office of Refugee Resettlement (ORR) and plunging the family into a maze of phone calls, conflicting answers, and silence. The parents were left navigating multiple agencies—ICE, Homeland Security, Health and Human Services—each disclaiming responsibility.

The result: a child detained by the federal government, his whereabouts unclear, his family shut out.

Systemic Failure, Not Clerical Error

ICE has insisted that procedures were followed. But the facts tell a different story. The system failed at its most basic function: keeping track of a child in government custody and ensuring parental contact.

This mirrors a broader pattern seen throughout Trump-era immigration enforcement—aggressive apprehensions paired with administrative indifference to due process, family unity, and child welfare. The use of technical classifications to override lived reality has become routine, allowing agencies to claim legal compliance while producing human chaos.

Calling this a “mistake” minimizes the scope of the problem. This was not a lost file. It was a lost child.

Legal and Ethical Questions Mount

The case raises serious legal concerns, including potential violations of due process and federal child welfare standards. Immigration advocates argue that mislabeling children as “unaccompanied” when parents are present may be used to expedite detention and limit family involvement—an end run around protections designed to prevent family separation.

It also exposes a glaring accountability gap. When a child disappears within the federal detention system, who is responsible? ICE? ORR? DHS? The parents received no clear answer—only proof that no single agency appears fully accountable.

A Warning, Not an Anomaly

Federal officials have suggested this case is isolated. The evidence suggests otherwise. As enforcement expands, more children are being swept into detention, more families are being sidelined, and more errors are being normalized as collateral damage.

This Minnesota teen’s case is not just a personal tragedy. It is a warning: when immigration enforcement prioritizes speed and optics over accuracy and humanity, children become paperwork—and paperwork gets lost.

The parents are still searching. The government, meanwhile, insists the system works.

The record says otherwise.

Tom Homan pulling ICE out of Minnesota

Tom Homan, President Donald Trump’s border enforcement czar and former acting director of Immigration and Customs Enforcement, has ordered a significant drawdown of federal immigration agents from Minnesota, marking a turning point in one of the most aggressive and controversial immigration enforcement operations carried out in a single U.S. state in recent years.

The decision follows weeks of intense federal activity across the Twin Cities and surrounding areas, where ICE and Border Patrol agents had been deployed in unusually large numbers as part of what federal officials described as a metro-area immigration surge. While the administration framed the operation as a targeted crackdown on undocumented immigrants with criminal records, the scale and tactics of the deployment quickly sparked backlash from state leaders, civil rights groups, and local communities.

The Federal Surge and Its Fallout

The ICE surge dramatically expanded the federal footprint in Minnesota. Agents conducted high-visibility enforcement actions, workplace visits, traffic stops, and home arrests, creating widespread fear in immigrant communities and straining relationships between federal authorities and local governments. Minnesota officials repeatedly objected to the operation, arguing that it undermined public safety by discouraging cooperation with local law enforcement and eroded trust in government institutions.

Protests erupted in Minneapolis and St. Paul as residents accused federal agents of racial profiling, excessive force, and operating with little transparency. The controversy deepened after multiple high-profile confrontations involving federal officers, intensifying scrutiny of the surge and fueling demands for its immediate end.

Homan Takes Control

Amid the mounting political pressure, the Trump administration sent Tom Homan to Minnesota to take direct command of the operation. Homan, a long-time hardliner on immigration enforcement, was tasked with stabilizing the situation while maintaining the administration’s broader crackdown goals.

In public statements, Homan defended the legality of the operation but acknowledged that the federal presence had become a flashpoint. He emphasized that ICE’s mission was not mass deportation but the identification and removal of individuals deemed public safety threats. Still, critics argued that the reality on the ground told a different story, with families disrupted and communities living under constant fear.

The Decision to Pull Back

This week, Homan confirmed that hundreds of federal immigration agents have been withdrawn from Minnesota, effectively ending the surge phase of the operation. While some ICE personnel remain in the state, their numbers have been reduced substantially, bringing federal activity closer to pre-surge levels.

Homan framed the drawdown as a strategic recalibration rather than a retreat. He claimed that enforcement objectives had been met and that continued large-scale deployment was no longer necessary. He also cited coordination challenges with state and local officials as a factor in scaling back operations.

Political and Legal Implications

The pullback is being interpreted by many observers as a tacit acknowledgment that the operation became politically unsustainable. Minnesota’s governor and several mayors welcomed the reduction but stopped short of calling it a victory, warning that the damage to public trust would linger long after agents left the streets.

Civil rights organizations continue to press for investigations into ICE’s conduct during the surge, including the use of force, detention practices, and the legal basis for certain arrests. Lawmakers at both the state and federal levels have raised questions about executive authority, oversight, and whether similar surges could be launched elsewhere without local consent.

What Comes Next

Although the immediate surge has ended, Minnesota remains a focal point in the national debate over immigration enforcement. Homan has made clear that ICE retains the authority to return if the administration deems it necessary, a statement that has done little to reassure critics.

For many Minnesotans, the episode reinforced long-standing concerns about the expanding power of federal immigration agencies and the lack of accountability when enforcement operations go wrong. For the Trump administration, the drawdown underscores the limits of aggressive immigration tactics when they collide with local resistance, public outrage, and political cost.

The agents may be leaving, but the questions raised by their presence are far from resolved.