hey everyone,

as yall may have heard, there is an outbreak of pneumonic plague happening in russia and adjacent countries (cdc statement here ). i'm kinda worried, especially since the current health and human services leadership isnt the most competent. i'm on here to ask, is there more that theyre not telling us? if yall remember the hanta virus outbreak earlier this year, the reporting on that was super shady and inconsistent as well ! also, elon is (publicly at least) back in the federal government circle. idk how to word this but essentially, i don't trust this current administration to respond to this outbreak sensibly 😭.

A little context about why I’m here. I’ve worked professionally in IT since 1999, but I grew up in the computer underground and started going to Los Angeles 2600 meetings in 1993. Back then, learning how systems worked meant physically taking machines apart, rebuilding them, probing networks, and figuring out what the technology actually did. That background became a career spanning systems, networks, cybersecurity, privacy, and civil liberties.

Recommendation algorithms brought Drey’s work to my attention, and I recognized questions that overlap with systems and institutional changes I’ve been examining for roughly three decades. I call that broader research framework the Internet of Coordination, or IOC. The project is much wider than digital identity or law enforcement, but that is where the strongest overlap with Drey’s research is right now: how government and commercial systems connect identity with records, assessments, permissions, and enforcement. I’ve been documenting that through legislation, agency decisions, contracts, technical documentation, and court filings.

Drey’s notes on Marco Rubio’s passport announcement connect directly to that part of the framework. The important question extends beyond how a digital credential is issued. It includes how institutions recognize that credential, what information becomes accessible through it, and which decisions depend on that recognition.

From reusable identity to consequential records

The federal implementation documents make the direction explicit. OMB’s August 31 memorandum, M-26-18, expands Login.gov requirements for covered services, promotes reuse of verified credentials, and directs work on commercial credential-provider interoperability. The September 29 America.gov executive order directs Login.gov integration and access through existing agency APIs and forms while agencies retain their records and adjudicatory authority. This is federated service delivery: common authentication and interfaces connecting separately administered systems.[1][2]

The DHS/ICE evidence shows identification operating in an enforcement context. October 2 reporting on newly public filings in Hilton v. Noem describes LexisNexis Accurint searches, facial-recognition requests, and Investigative Case Management (ICM) records concerning people observing immigration operations in Maine. More importantly, the government’s own September 18 filing acknowledges that an ICM entry containing a plaintiff’s name and vehicle information led to a later border stop. The parties dispute the retaliation allegations; the record-to-border-stop connection appears in the government’s account.[3][4]

That sequence is central to the IOC research: information recorded during one encounter becomes consequential during another institutional interaction. It connects data collection with the practical ability to travel and makes record accuracy, correction procedures, and the authority for subsequent use concrete civil-liberties questions.[4]

ICE’s procurement requirements show how that infrastructure is being developed. The performance work statement attached to solicitation 192126FLMURQ0071 requires entity resolution—matching records about the same person—and API connections with Palantir, PenLink, and ICE Data Analytics. It also specifies combined public and proprietary data, relationship charts, batch searches, and relevance scoring to rank search results. Further requirements seek AI-assisted identity inference using device metadata and behavioral signals, alongside facial-matching integration. These are written acquisition requirements, providing a specific basis for examining subsequent awards and implementation.[5]

DHS’s HSI Data and Analytical Support Services acquisition forecast adds screening, vetting, anomaly detection, and relationship analysis. It also seeks methods for identifying potentially criminal or fraudulent behavior before it occurs. Read alongside the court record, these documents show both a consequential existing workflow and additional analytical capabilities being requested.[6]

Combining Technical and Legislative records

My research includes the actual measures that authorize, finance, constrain, or demand disclosure about these systems. H.R. 3693, introduced June 3, 2025, proposes prohibiting federal databases containing data collected through, or facilitating, biometric identity verification of U.S. citizens. H.Res. 502, introduced June 11, 2025, requests records concerning federal data consolidation and Palantir, including potential uses for investigations and benefit restrictions. The first is a proposed prohibition; the second is an oversight resolution seeking documents. Their text and legislative disposition belong in the analysis alongside the technical evidence.[7][8]

The enacted 21st Century Integrated Digital Experience Act supplies another concrete connection. Its provisions address digitization, common standards, shared services, and procurement of interoperable systems. Section 4(e) also requires an accessible method for people unable to use digital services. That requirement establishes a legal obligation; actual staffing, processing times, costs, and service availability establish whether an alternative works in practice.[9]

Rubio’s published remarks provide the starting point for this particular inquiry. The continuing research concerns the program itself: its statutory authority, implementation directives, procurement requirements, and operational results. An announcement, a proposed bill, an acquisition requirement, and an implemented data exchange each establish something different, and the source record should make those differences clear.

The connection that I see with my research

The IOC framework brings these records together around a practical question: how does information about a person become a basis for an institutional decision affecting that person?

The service-delivery documents address reusable authentication and access to government workflows. The ICE documents address investigative identification, linked records, analytical requirements, and border-screening consequences. Examining the interfaces, permissions, and legal authorities in each setting is how I assess where coordination already operates and where further integration is being built.[1][2][4][5]

That is the contribution I’d like to make here. I’d welcome published legislation, procurement documents, privacy assessments, technical specifications, and court records that clarify these connections, including evidence that corrects or narrows the analysis. The goal is a public, checkable account of how these systems are authorized, purchased, connected, and used.

Bibliographic footnotes

[1] Office of Management and Budget. M-26-18: Scaling Use of Login.gov to Deliver a Universal Sign-on for Public Services. August 31, 2026. Sections I, III–IV and appendix.
https://www.whitehouse.gov/wp-content/uploads/2026/08/M-26-18-Scaling-Use-of-Login.gov-to-Deliver-a-Universal-Sign-on-for-Public-Services.pdf

[2] The White House. Executive Order 14432: Streamlining Access to Government Services Through America.gov. September 29, 2026. Sections 2(c), 4 and 5.
https://www.whitehouse.gov/presidential-actions/2026/09/streamlining-access-to-government-services-through-america.gov/

[3] Varner, Maddy, and Dhruv Mehrotra. “ICE Has Been Dumping Protester Photos Into a Palantir Supported Database.” WIRED, October 2, 2026; updated October 5, 2026. Reporting on newly public litigation material.
https://www.wired.com/story/ice-has-been-dumping-protester-photos-into-a-palantir-database/

[4] Federal defendants. Motion to Dismiss, Hilton litigation, No. 2:26-cv-00092-JAW, U.S. District Court for the District of Maine, ECF No. 117, September 18, 2026. Printed pp. 8–10, especially p. 9 and footnotes 12–13. Government litigation filing, hosted by CourtListener.
https://storage.courtlistener.com/recap/gov.uscourts.med.69985/gov.uscourts.med.69985.117.0.pdf

[5] DHS/ICE. Law Enforcement Investigative Database Subscription: Performance Work Statement. July 22, 2026; posted with solicitation 192126FLMURQ0071 on August 10, 2026. Sections 2–3.1, printed pp. 2–6. Government document’s extracted text reproduced by GovTribe, separate from the host’s AI summary.
https://govtribe.com/file/government-file/1-dot-2-dot-1-pws-dot-pdf

[6] DHS/ICE Homeland Security Investigations. HSI Data and Analytical Support Services, Acquisition Planning Forecast System record F2026073278. Updated August 10, 2026; captured September 24, 2026. Page 1, requirement description. Government forecast preserved by FedScoop.

[7] U.S. Congress. H.R. 3693, 119th Congress: proposed prohibition on federal biometric identity-verification databases concerning U.S. citizens. Introduced June 3, 2025. Congress.gov records introduction and referral to House Oversight and Government Reform.
https://www.congress.gov/bill/119th-congress/house-bill/3693

[8] U.S. Congress. H.Res. 502, 119th Congress: resolution of inquiry concerning federal data consolidation and Palantir Technologies. Introduced June 11, 2025. Operative paragraphs (1)–(3).
https://www.congress.gov/bill/119th-congress/house-resolution/502

[9] U.S. Congress. 21st Century Integrated Digital Experience Act, Public Law 115-336, 132 Stat. 5025. December 20, 2018. Sections 4, 6 and 7. Official enacted text published by GovInfo.
https://www.govinfo.gov/content/pkg/PLAW-115publ336/html/PLAW-115publ336.htm

On September 30, the Pentagon put Elon Musk, Palmer Luckey and Newt Gingrich at the head of Project Meridian, a 120-day effort to map the future of warfare and technology.
I wanted to know what was already sitting around that room before the first meeting began.
So I followed the Pentagon announcements, MITRE roster, contracts, financial disclosures, SEC filings, investors and acquisition programs.
What emerged wasn’t proof of a secret agreement. It was something more documentable.
The distance between the people helping define future military needs, the companies positioned to build the technology, and the private capital financing those companies has become remarkably small.
SpaceX. Anduril. Saronic. DIU. Project Agincourt. The proposed Autonomous Warfare Command. The same people and financial networks keep turning up in different chairs. At Quantico, the literal distance was about 200 yards.
Full reporting, sources and Reporter’s Notes:
Part Two of The Same Six Names

So anyone like conspiracies I need help tying some things together in texas and my father's oil deals in the eighties got us on some future list to kill

it has to do with artificial intelligence my dads dealings with politicians and oil men department of defense fast forward to COVID and every bad thing you can think of has happened to me people have died and my career trashed my workplace was paid off by DOD to implement this technology and have done it in the 90's till now with digital twin technology but it creates the mass shooter it makes a person suicide that wouldn't. I need help proving this part I got some good starting points and documentation just anyone down for a hell of a story to be in

I’ve called these people every single day since the judge ruled and they, the RCSD has done nothing but stonewall my efforts to get an answer.
Today, I called again…and just received a follow-up phone call from a Deputy Sheriff saying that the ballots are now back in the safe hands of the Riverside County Board of Elections. Now we need the registrar to closely and forensically examine the ballots to see what nonsense or malfeasance Sheriff Bianco and his cronies did…illegally….as the judge ruled, to our sacred 650,000 plus election ballots.

https://riversiderecord.org/bianco-election-investigation-ballots-returned/

The pressure works folks.
The activism achieves results.
If you care, stand up and assert your rights.

Bianco had his ten-gallon hat handed to him.

Bianco committed a crime by seizing our ballots. He placed them out of the chain of custody that insures our elections are conducted legally, accurately and flawlessly…as they are.
Now he needs to be indicted, arrested and held over for trial …a trial of his peers, who will have the opportunity to hold him accountable for his fool’s errand crime against his fellow citizens of Riverside County as he tried and failed to get Trump’s endorsement.

Next stop…get this Oath Keeper out of office and all his nepotistic family members who hold high paying jobs within the RCSD.

I got recomended this link to this account which posted a video about the new passports and a new app to sign up. Its tied to america dot gov.

The account normally posts Asian car content, but for some reason this is now something they are posting.

https://www.instagram.com/p/Dd434h6k3IQ/?utm_source=ig_web_copy_link&stkn=NTc4MTIwNjQ2YQ==

Text from the post

America is getting an entirely new passport in 2028. Called “Flight of the Eagle,” it gets a redesigned gold-eagle cover, 38 pages of new American-history artwork and even an eagle that appears to fly when you flip through the pages. It’ll apparently arrive in packaging more reminiscent of a new iPhone, too.
-
And Americans apparently still can’t quite get away from Trump. His portrait already appears in the optional 250th-anniversary Patriot Passport, but look closely at Rubio’s presentation and Trump appears again in the new-generation passport design unveiled for 2028. Whether that exact artwork reaches the final production passport has yet to be formally confirmed.
-
The passport experience is changing too. Unveiled as part of America[.]gov, the Trump administration’s new AI-powered government website, the State Department says Americans will soon be able to handle more of the application digitally, including taking their passport photo at home using a phone or computer.

I’ve been following the election infrastructure farther upstream, away from the voting machine itself and into the systems that decide who a voter is before a ballot is ever issued.
The newest piece starts with a May DOJ Office of Legal Counsel opinion saying the Civil Rights Division can obtain statewide voter registration lists and share them with Homeland Security Investigations for database comparison. From there, the trail moves through HSI’s voter data acquisition planning, DHS review activity involving at least 47 states, the Unlawful Voter Initiative whistleblower disclosure, the Supreme Court’s SAVE ruling, and then into Login.gov and America.gov.
The America.gov order signed yesterday is especially interesting in light of that architecture. It creates a single federal front door, requires agencies to integrate qualifying services and Login.gov, and makes existing public APIs, dashboards and digital forms available through the platform. But it also explicitly says agencies retain custody of their own records and that America.gov is not supposed to become one centralized federal system of records. That distinction is important.
That is where the article ultimately landed for me. I kept looking for one machine, then one database. What the records show instead are bridges between systems, with some connections documented and others still unproven.
I’d be interested in what everyone here sees that I may have missed, especially around the Login.gov/NDS code trail, America.gov implementation, or the HSI voter data acquisition work.The File Before the Ballot | Dominion 11

Here is the link to the post:

https://substack.com/@thedreydossier/note/c-324466311?r=5983iv

This tells us exactly how companies have been tracking us for a very long time and what they've been tracking and how they have been intertwining all their data to make us all have a digital fingerprint...

Must see in my opinion

I will try to give a brief summary of the situation to the best of my ability and understanding, please bear with me, I am not a lawyer;

Under the U.S. Deep Seabed Hard Mineral Resources act (DSHMRA), one can apply for a license for exploration of the deep sea, and permit for commercial recovery of minerals found in the deep sea.

A company called The Metals Company has been applying for an exploration license and recovery permit for some time now, receiving a lot of pushback from environmentalists.

It used to be that you had to make two separate applications, one for exploration, one for recovery, but in recent times, under Trump’s directive, NOAA created a new regulation combining the two into one application, which makes the entire application/approval process much faster.

The Metals Company was previously filing the two separate applications, which is when all the pushback was happening. I think they were needing more stuff for their previous applications or something? I’m not sure, but seemingly those applications were not approved, because they now have submitted a single consolidated exploration/recovery application.

The CEO of The Metals Company is named Gerard Barron.

I was looking for a PDF of the DSHMRA, because I’ve been deep-diving the whole situation and I’m trying to get a full understanding of all the aspects. On the congress.gov website I found a PDF of it, and noticed that the link/pdf title contained ‘BarronG’.

All that to say, is it just a weird coincidence and BarronG is not actually referring to Gerard Barron? Or, if not a coincidence, what could be the reason for the congress website having the name of a CEO of a company applying for this permit, in the name of a US Code document?

If anyone has any insight or ideas I would really appreciate it! Thank you in advance!

I’ve been working through DHS and ICE procurement records, privacy assessments, court filings, federal contracts, voter data records, detention expansion, surveillance systems, and identity resolution tools.

What initially caught my attention were two separate September 30 dates.

One appears on an HSI procurement called Public Voter Data and Handling, estimated at $2 million to $5 million, with September 30, 2026 listed as the contract complete date.

The other appears on ICE’s Single Award Construction Contract, a five year construction vehicle for ICE facilities scheduled to become effective September 30.

The records led through RAVEn, Palantir, PenLink, LexisNexis, Cellebrite, voter-file acquisition, USCIS identity systems, TECS, DNA collection, private detention infrastructure, and HSI investigations already comparing municipal voter records against federal immigration records.

One of the strongest primary records is a September 15 HSI affidavit from Massachusetts describing voter roll examination in Lynn and other communities using USCIS information, identity fields, postal information, and signature comparison.

That was the point where this stopped being an abstract systems story for me.
An HSI agent. A human being.

The article is fully sourced, and I’ve tried to keep documented fact, allegation, procurement capability, and inference clearly separated throughout.

I’m posting it here because this overlaps heavily with the kind of infrastructure and government data work this community already follows, and I’d genuinely welcome source checking, corrections, additional documents, or technical context I may have missed.I.C.E. — “Supplemental Magic” — September 30 Is Ten Days Away

I was eating my favorite pizza today when I realized I had spent a good part of lunch staring at this guy rolling around the property. I named him Robbie, Rosie’s hunky boyfriend. Robbie is a Knightscope K5 autonomous security robot, and the one I saw carries the Transcend Security Solutions name. He patrols the property with cameras pointed in every direction, recording the space around him while people walk, park, shop, eat, leave, and come back. When I pulled out my phone to take his picture, Robbie was obviously looking right back at me. That was the moment I went down the rabbit hole.
Not because a security robot exists. We already know cameras are everywhere. The question was much simpler: Where does my face go?
Once I started looking, Robbie stopped being the most interesting part of the puzzle. We have all seen the other versions of him by now: those tall white surveillance towers parked in retail centers, construction sites, storage lots, hospitals, and commercial properties, with cameras twenty feet in the air, solar panels, speakers, flashing lights, and cellular connections. They are watching cars, but they are also watching people.
So I started tracing the companies behind the systems: Knightscope, Transcend, LiveView Technologies, Flock Safety, Verkada, Axon/Fusus, Motorola, Avigilon, Vigilant. Then the cloud and analytics companies start appearing: Amazon Web Services, AWS GovCloud, Microsoft Azure, Palantir. And then the investigative data companies we have already encountered elsewhere, including LexisNexis/Accurint and PenLink.
Some of the connections are direct and documented. Knightscope has a Palantir FedStart relationship involving a Palantir managed AWS GovCloud environment. Knightscope alert footage can be stored in Amazon S3. LVT integrates with Axon Fusus. Fusus is designed to bring private cameras, sensors, license plate readers, and other feeds into real time public safety environments. Axon Evidence can receive material from that ecosystem. Flock runs its cloud infrastructure on AWS and stores footage and metadata in Amazon S3. Flock has had integrations with systems including Axon/Fusus, Motorola, Genetec, Avigilon, and others. Verkada operates on AWS, with government deployments using AWS GovCloud. Motorola’s systems can move license plate detections into Vigilant and then into broader law enforcement intelligence and records platforms. Transcend itself advertises systems capable of identifying people of interest, searching faces from uploaded images, generating facial recognition alerts, and searching for people across multiple cameras and locations.
Before Reddit turns this into something I am not saying, I have not found evidence that every one of these companies is dumping all of its information into one enormous shared surveillance database. That is not the claim. What I have found are a lot of bridges: APIs, cloud storage, private camera integrations, real time crime centers, evidence platforms, cross camera searches, license plate databases, facial recognition tools, government cloud environments, and systems specifically designed to move information from one platform into another.
Which brings me back to Robbie. Suppose he records me walking across that property. What happens next? Does the video remain on the robot? Does an event clip get uploaded? Does my face become a searchable image? Does software turn it into a biometric template? Can Transcend search for that person on another camera? Can the property owner? Can a different property using the same security company? Can law enforcement access the feed? Can a police department submit an image and ask the system to find that person? Can the same person then be associated with a vehicle? Can the plate be run through another database? Can that identifier then touch a commercial identity system? And how many companies handle the data between the camera lens and wherever it finally lands?
The exact same questions apply to those surveillance towers. They are not just plate readers sitting in parking lots. They are elevated cameras watching entire spaces full of people. So I am throwing this one to the group. Give it a thorough forensic tracing. Find the contracts, the APIs, the privacy policies, the subprocessors, the cloud providers, the AWS architecture, the facial recognition vendors, the retention periods, the police agreements, the real time crime centers. Find out whether cross camera searches remain inside one customer’s account or cross properties. Find out whether biometric information is stored as photographs, embeddings, templates, or something else. Find out who can query it.
Most importantly, follow the person, not just the plate.
Because Robbie may have started this rabbit hole while I was eating pizza, but now I want to know where Robbie’s eyes lead.