u/R3ZondoOfficial

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

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

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.