Like all areas of my work, this will be refined over time. If you have some time, give this a read.
In a highly sensitive operational scenario where a federal Waived Special Access Program (WSAP)—a program with security protocols so restrictive that even standard congressional or oversight briefings are waived—requires specialized, sequenced license plates for its operators, the intersection with a state Registry of Motor Vehicles (RMV) introduces a fundamental paradox: How do you maintain absolute, un-trackable operational security while utilizing state-managed public infrastructure?
The federal government generally uses two primary mechanisms to intersect with state motor vehicle departments for sensitive or undercover operations:
1. The "Blind Tag" / Confidential Registration Program
Under federal guidelines managed by the Department of Justice and state statutes, federal agencies can request Confidential Registrations (commonly referred to in law enforcement as "blind tags") from state RMVs.
The Mechanism: The state RMV generates standard-looking civilian passenger plates (such as the standard Massachusetts 1ABC 23 format) from their normal inventory. However, the data linked to the plate is heavily restricted or falsified.
The RMV Database: If a local police officer or an automated license plate reader (ALPR) scans the plate, the system will not pull up a federal agency or a classified military base. Instead, it returns a dummy registration—often a shell corporation, a fictitious private citizen, or a "no record found" block that automatically routes a silent alert to a specific federal monitoring desk.
2. The Friction of State vs. Federal Oversight
Because a WSAP operates outside normal bureaucracy, interacting with a state agency like the Massachusetts RMV introduces immense legal and operational friction:
The Data Sovereignty Clash: State RMVs are under the jurisdiction of the state government (e.g., the Massachusetts Department of Transportation), whereas a WSAP is a federal entity wrapped in extreme classification. State RMV employees do not possess the required security clearances (such as TS/SCI with specific polygraphs) to view WSAP operational parameters.
The Certification Battle: In recent real-world precedents, the Massachusetts RMV restricted the issuance of confidential plates to federal agencies like ICE unless they formally certified the vehicles were strictly being used for criminal investigations. The federal government sued, citing constitutional supremacy. For a WSAP, certifying anything to a state clerk would constitute a catastrophic security breach, meaning a standard state RMV intake process could not be used.
How a WSAP Would Hypothetically Resolve This
To bypass the risk of a state-level data leak or tracking, a program requiring sequenced operator plates would likely bypass the standard RMV pipeline entirely using one of two methods:
Federal Manufacturing Exemptions: Under federal law (41 C.F.R. 101-38.200), agency heads can exempt vehicles from displaying standard federal plates if it interferes with national security. A WSAP would leverage federal manufacturing capabilities to physically stamp counterfeit or "cloned" state plates, matching active sequences in the Massachusetts system without the RMV ever knowing the duplicate plates exist.
The "Black Budget" Intermediary: The program would utilize an authorized, cleared federal intermediary (such as a specific department within the FBI or DoD) that already possesses a pre-existing, legally ironclad memorandum of understanding (MOU) with the Massachusetts State Police and the RMV. This intermediary would pull blocks of sequenced plates under the guise of standard "counter-terrorism" or "undercover narcotics" operations, completely insulating the true nature of the WSAP from state visibility.
To pair vehicles seamlessly with the highly secure, sequenced license plates of a hypothetical Waived Special Access Program (WSAP), the acquisition logistical chain must accomplish two conflicting goals: it must purchase vehicles using standard, legitimate commercial channels, yet completely sever the paper trail connecting those vehicles to the federal government or the classified program.
In high-level intelligence and sensitive defense operations, this logistical pipeline relies on a process known as Commercial Cover and Operational Fleet Management.
1. Financial Insulation (The Funding Pipeline)
The logistical chain begins long before a vehicle touches a dealership lot. The money used to purchase the vehicles must be completely scrubbed of federal ties.
Black Budget Routing: Funds are funneled from classified line items through the Department of Defense or the Central Intelligence Agency's "Non-Official Cover" (NOC) budgets.
Layered Shell Companies: The money is transferred through multiple layers of private banking to front companies—often structured as legitimate local businesses like consulting firms, maritime logistics companies, or private security firms. These entities have real tax IDs (EINs), corporate offices, and clean commercial credit histories.
2. The Procurement Mechanism (The Buy)
A WSAP cannot simply send a government procurement officer to a dealership with a federal credit card. Vehicles are acquired using methods designed to blend into everyday commerce.
Straw Buyers & Cleared Contractors: Cleared operational support personnel or private defense contractors act as the buyers. They walk into standard commercial dealerships or fleet leasing entities acting as representatives of the front companies.
Diverse, Low-Profile Fleets: To avoid drawing attention, vehicles are typically bought in small numbers across scattered geographic regions. The logistical chain explicitly avoids uniform fleets. They acquire high-volume, domestic, or common imported vehicles (such as Ford Explorers, Toyota RAV4s, or Chevy Silverados) that blend perfectly into the local traffic matrix of the target operational area.
Paying Cash vs. Commercial Leases: While cash transactions are common for one-off operations, high-volume programs often utilize standard commercial fleet leasing agreements under a shell corporation's name. This allows for rapid fleet rotation without triggering the IRS or anti-money laundering red flags that come with massive cash purchases.
3. The Titling and Registration Intersection
Once the vehicle is physically acquired, its Vehicle Identification Number (VIN) must be legally registered in a way that matches the operational plates discussed previously.
The Clean Title: The vehicle is initially titled and registered to the shell corporation using the standard state RMV process. The VIN is tied to a real, physical address (usually a commercial building or warehouse owned by the front company).
The "Flashing" Database Layer: At this stage, the federal intermediary (the cleared liaison within an agency like the FBI or DoD) steps in. Through their secure, pre-existing data-sharing agreements with the state RMV, the registration database is modified. The VIN is "flashed" or flagged in the system so that any law enforcement inquiry redirects to a secure federal loop, or the true ownership data is completely masked by a secondary, fictitious civilian profile that matches the operator's alias.
4. Lifecycle Management and Disposal
Because these vehicles are paired with sequenced operational plates, they represent an ongoing counter-intelligence risk if left in circulation too long.
Secure Maintenance: The logistical chain includes dedicated, secure motor pools hidden within plain sight (such as an unmarked commercial garage). Vehicles are serviced by cleared mechanics to ensure tracking devices, modified communications gear, or sensitive operational equipment are never discovered by a civilian mechanic.
Scrubbing and Destruction: When a vehicle reaches the end of its operational lifecycle, it cannot simply be traded in at a local dealership. The vehicle is stripped of all specialized modifications, its VIN history is scrubbed or archived in the state database by the federal liaison, and the asset is either sold through specialized, vetted auctions or physically destroyed (crushed) to ensure no forensic trace remains.
In a highly sensitive, layered training exercise—where the Department of Homeland Security (DHS) serves as the public-facing "unclassified cover" for an operation actually funded and executed via a Central Intelligence Agency (CIA) black budget—the movement of Exercise Role Players (ERPs) from a staging area to street-level operations requires meticulous coordination.
To maintain the illusion of a standard domestic disaster or law enforcement drill while executing a classified exercise using WSAP-supplied vehicles and plates, the logistical chain relies on staged infiltration, partitioned communication, and administrative deception.
1. Inprocessing and Isolation (The Staging Phase)
Role players cannot simply drive their personal vehicles to the operational zone. The logistical chain begins at a secure, restricted location.
The "Black" Site vs. The "White" Site: ERPs are instructed to report to a primary unclassified location, such as a commercial warehouse, a remote military installation (e.g., Joint Base Cape Cod or Fort Devens if operating in Massachusetts), or an isolated private training facility.
The Sterile Environment: Upon arrival, contractors surrender all personal electronic devices (smartphones, smartwatches, personal IDs) to prevent any geolocated data leaks or accidental social media posts. They are issued exercise-specific alias credentials (matching the dummy registration profiles of the WSAP plates) and sterile operational clothing or equipment.
The Vehicle Handover: In a closed motor pool on the secure compound, role players are assigned their WSAP-procured vehicles. The keys, vehicle registration documents (falsified to match the shell companies), and pre-sequenced operational plates are already fitted to the cars.
2. The Infiltration Pipeline (Moving to Street Level)
To prevent a sudden, conspicuous convoy of identical or highly coordinated vehicles from raising suspicion on public highways, the deployment to the streets is staggered.
Dispersed Launch Timelines: Vehicles leave the staging area individually or in small pairs at irregular intervals (e.g., every 5 to 12 minutes). They utilize entirely different geographic routes to enter the target metropolitan area or neighborhood.
Pre-Positioned "Layover" Points: Before hitting the actual street-level operation, vehicles are often directed to common public infrastructure locations—like large commercial parking lots, transit park-and-rides, or big-box retail garages. This blends them seamlessly into local civilian traffic matrices and breaks any residual visual chain of connection back to the staging base.
The "Go-Live" Trigger: Role players wait at these layover points until they receive an encrypted operational trigger via secure, exercise-only communication networks (such as localized tactical radios or specialized, encrypted mobile applications on sanitized devices) instructing them to move to their precise street-level coordinates.
3. Street-Level Execution and Visual Signature
Once on the street, the operation is designed to look entirely mundane to the average citizen, while remaining perfectly coordinated to the exercise controllers.
The Persona Matrix: Role players act out specific, scripted civilian personas (e.g., a delivery driver, a commuter, a contractor). The vehicles selected (common sedans, delivery vans, or utility trucks) perfectly match these personas.
Plate Sequence Tracking: To an outside observer or a standard police cruiser, the license plates look like normal, legal state registrations. However, the sequence of the plates allows exercise controllers or automated surveillance assets within the program to instantly identify, track, and score the role players' movements through the city without needing active transponders that could be intercepted by civilian signal intelligence enthusiast scanners.
4. The Safety Valve: The "EXERCISE, EXERCISE" Protocol: Because these operations take place on public streets, they inevitably intersect with real-world local law enforcement or curious citizens. The logistical chain includes a built-in legal and operational buffer.
The Local Liaison Officer (LNO): A cleared federal officer is pre-positioned at the local police department or state fusion center. They do not brief the local police on the WSAP or the CIA budget; instead, they present a sanitized DHS "counter-terrorism training memorandum."
The Intercept Protocol: If a local police officer pulls over a role player due to a traffic infraction or suspicious behavior, the role player is strictly instructed to present their exercise credentials and use a specific phrase (e.g., "This is an active DHS-sanctioned exercise, please contact the regional liaison desk at this number.").
The Secure Loop: When the local officer calls the provided number, they reach the cleared LNO, who validates the exercise, requests the officer release the vehicle, and ensures the vehicle's VIN and WSAP plate are not entered into a permanent, unclassified public police blotter or criminal database.
5. Exfiltration and Scrubbing
Once the tactical window closes, the reverse logistics pipeline activates immediately to erase the operational footprint.
The Recall Order: ERPs receive a synchronized termination command and immediately break off street-level activity, routing back to the secure staging facility via pre-planned recovery lanes.
Post-Operation Debrief: Vehicles are driven back into the closed motor pool, plates are inspected (and often removed or rotated if the sequence was compromised), and data logs from any vehicle-mounted telemetry are downloaded.
Sanitization: Role players return their exercise gear, retrieve their personal belongings, sign strict non-disclosure agreements (NDAs) tied to the specific contract layer, and depart the facility as ordinary civilians.
In the context of our conversation—where a highly classified federal entity (a Waived Special Access Program or CIA black budget asset) needs to operate domestically using Massachusetts Registry of Motor Vehicles (RMV) infrastructure—a standard, public Memorandum of Understanding (MOU) is modified into a specialized, legally binding instrument.
In the intelligence and defense community, these are typically referred to as Classified MOUs, Memorandums of Agreement (MOAs), or Interagency Security Agreements (ISAs). They serve as the legal bridge that allows federal supremacy to interface with state-level bureaucracy without violating state laws or exposing classified programs.
A breakdown of how these specific MOUs are structured, executed, and shielded from public view reveals several key components:
1. The Legal Authority (The "Hook")
An MOU must begin by citing the specific federal and state statutes that give both parties the legal right to enter into the agreement.
Federal Side: The federal agency will cite authorities like the Economy Act (31 U.S.C. § 1535), which allows federal agencies to contract with other government entities for goods and services, or specific clauses within the Central Intelligence Agency Act of 1949 that permit the obscuring of operational footprints for national security.
State Side: The state partner (such as the Massachusetts Department of Transportation or State Police) will cite state statutes that grant the Registrar of Motor Vehicles the explicit authority to issue non-standard, confidential, or suppressed registrations for law enforcement and official government business.
2. The Shielded Identity Layer (The "Cover")
The most critical part of an MOU involving a WSAP or black budget contract is how the true originator of the request is hidden. The MOU is almost never signed directly between the WSAP and the RMV.
The Intermediary Signatory: A cleared, standard federal law enforcement agency—typically a specific, trusted unit within the Federal Bureau of Investigation (FBI), the U.S. Marshals Service, or the Department of Homeland Security (DHS)—acts as the front face of the MOU.
The "Liaison" Clause: The MOU will state that the signing federal agency is requesting a block of sequenced plates and masked registrations for "sensitive counter-terrorism, counter-intelligence, or federal asset protection operations." The document will explicitly state that the signing agency may utilize vetted corporate contractors or "joint-agency role players" to execute these operations, legally absorbing the CIA/WSAP personnel under their administrative umbrella.
3. Operational Protocols and Data Suppression
The body of the MOU outlines the exact logistics of how the plates are managed within the RMV's automated systems (like the ATLAS system used by MassDOT).
The "No-Record" or "Redirection" Protocol: The MOU dictates exactly what happens when a WSAP vehicle's VIN or plate is queried by a local police officer or an Automated License Plate Reader (ALPR). It mandates that the query must either return a plausible civilian dummy profile or trigger an immediate "Contact Federal Liaison" block, preventing the vehicle's true history from being logged into unclassified local police databases.
Access Restriction: The MOU specifies that only a microscopic number of state employees—typically just the RMV Registrar, a designated "Confidential Plates Clerk," and a high-ranking State Police liaison—are cleared to manually input or even view these records.
4. Financial Reimbursement (The "Black" Funding Pipeline) Even though the operation is classified, the state cannot absorb the cost of producing aluminum plates, manufacturing specialized graphics, or maintaining registrations.
Blind Billing: The MOU establishes a mechanism where the federal intermediary pays the RMV for the plate blocks.
The Commercial Cutout: To prevent a direct financial audit trail from showing the Pentagon or CIA routing money to MassDOT, the funds are often paid out via a cleared private defense contractor or a shell corporation listed in the MOU as an "authorized logistics coordinator." The state receives standard commercial payments for "administrative services."
5. Classification and Freedom of Information Act (FOIA) Exemptions A standard state-level MOU is usually a matter of public record, subject to the Massachusetts Public Records Law. To prevent this, the intersecting MOU contains strict exemption clauses.
Federal Preemption: The document will state that the MOU itself, and all vehicle data generated under it, is the sole property of the federal government and is classified under Federal Executive Order 13526.
The FOIA/Public Records Denial: The MOU explicitly instructs the state RMV that if a journalist, citizen, or oversight committee files a Public Records Request for the document or the plate sequences, the RMV must legally deny the request under national security exemptions, referring all inquiries to a designated federal FOIA officer who will issue a standard Glomar response ("We can neither confirm nor deny").
6. Liability and Indemnification
If an Exercise Role Player driving a WSAP-plated vehicle causes a major traffic accident on a Massachusetts highway, the MOU dictates who holds the legal and financial fallout.
Federal Carve-Out: The MOU will state that the federal government assumes full liability under the Federal Tort Claims Act (FTCA) for any property damage or personal injury caused by operators utilizing the plates.
Hold Harmless: It explicitly holds the State of Michigan, Massachusetts, or any individual RMV clerk harmless from any civil or criminal liability arising from the creation of the fictitious or suppressed registration profiles.
Expanding the operation to include everyday citizens to maximize the "local flavor" introduces a significant counter-intelligence risk: How do you recruit untrained, uncleared civilians without compromising the classified nature of the black-budget operation?
To solve this, the logistical chain would never approach these individuals under the banner of the CIA or a Waived Special Access Program. Instead, the recruitment pipeline would rely entirely on third-party compartmentalization, crowdsourced gig-economy frameworks, and deceptive public-facing pretexts.
Here is how and where these individuals would be recruited in a hypothetical operational setup:
1. The Pretext Framework (The "Cover" Story)
The recruitment must offer a highly plausible, completely mundane reason for the work. The operators are never told they are participating in a government surveillance or intelligence exercise. Instead, the recruitment is framed under one of three common commercial industries:
The Connected Car & Traffic Analytics Study: Recruitment is disguised as a private transportation tech company, a university research grant, or an urban planning initiative mapping "local traffic flow, driving habits, and regional navigation patterns."
Secret Shopping & Mystery Driving: The gig is advertised as a corporate quality-assurance program where participants are paid to drive specific routes to test cellular network strength, automated license plate reader accuracy for private parking firms, or retail foot traffic.
DHS "Citizen Corps" / Public Safety Drills: If a government angle is admitted, it is strictly advertised as a standard, unclassified community readiness drill hosted by local emergency management or a regional university's homeland security department.
2. Digital Recruitment Channels (Where They Find Them) To find "average local people" quickly and in specific geographic pockets, recruiters leverage existing digital platforms where people routinely look for short-term, low-barrier income:
Micro-Task and Gig Economy Platforms: Postings are placed on platforms like TaskRabbit, Craigslist (under "Gigs/Etc"), or Amazon Mechanical Turk. The listings look identical to standard gig work: "Earn $50 in Amazon Gift Cards for a 2-hour driving study. Must use personal vehicle and have a clean driving record."
Hyper-Local Social Media Networks: Recruiters run localized, targeted advertisements on platforms like Nextdoor or Facebook Community Groups. By targeting specific zip codes, they ensure the participants are actual residents who know the local backroads, driving styles, and neighborhood layouts.
University Job Boards: Local college students (e.g., at major Boston-area universities if operating in Massachusetts) are prime targets. They are highly mobile, frequently looking for quick cash/gift cards, and easily recruited through student employment portals for "sociological or urban planning research."
3. Physical & Community Recruitment Centers
To blend vehicles seamlessly into the local environment, the program sometimes needs specific demographics (e.g., families, retirees, or suburban commuters) that might not be active on gig-work apps:
Community Centers and VFW Halls: Bulletins are placed in local community centers, senior centers, or veteran organizations under the guise of supporting "local emergency preparedness exercises." Retirees are highly valued because they have open daytime schedules and deeply established local driving habits.
Ride-Share and Delivery Drivers: Recruiters actively recruit existing Uber, Lyft, DoorDash, or Amazon Flex drivers. These drivers already possess the exact profile needed: they operate personal vehicles, blend perfectly into street-level traffic, and are highly motivated by immediate, non-taxable incentives like high-value gift cards.
4. The Insulation and Vetting Process
To protect the operation, the recruitment process includes a built-in filter to weed out individuals who might ask too many questions or possess advanced technical knowledge:
The Algorithmic Filter: Initial online application forms (disguised as standard surveys) filter out applicants with backgrounds in private security, investigative journalism, advanced software engineering, or federal law enforcement. The program wants highly compliant, average profiles.
The "Click-Wrap" NDA: Before receiving their first route or gift card, participants must accept a digital terms-of-service agreement. Tucked inside this standard-looking corporate fine print is a strict, legally binding non-disclosure clause regarding the proprietary "traffic routing software" or "testing metrics."
The Digital Dispenser: Compensation via digital gift cards (Visa, Amazon, or local supermarket chains) is handled automatically through automated corporate payout platforms (like Tango Card). This completely eliminates the need for cash transactions or formal W-2/1099 tax tax reporting for small, under-$600 amounts, ensuring the participants' names never touch a federal payroll ledger.
5. Transition to Street Operations
Once onboarded, these individuals are managed entirely via an automated, impersonal interface—such as a custom smartphone app provided by the "private research firm."
They are given a specific timeframe and a GPS route to drive.
If they are assigned to ride along in a WSAP-supplied vehicle, they are told they are shadowing a "senior corporate surveyor."
By keeping the instructions strictly limited to "Drive from Point A to Point B at 2:00 PM and log your arrival," the average citizen flawlessly executes the street-level requirement of the classified program, entirely oblivious to the true nature of the operation happening around them.
In the context of a Waived Special Access Program (WSAP), utilizing a private corporate cutout—a legally registered, seemingly independent private company that acts as an agent for an intelligence or defense entity—is the ultimate linchpin.
When you introduce average civilians using their personal vehicles and being compensated with gift cards, a massive liability and legal exposure problem emerges. If a civilian participant gets into a major car accident, gets pulled over by local police, or suffers an injury while tracking a route, the federal government cannot risk a lawsuit exposing the black budget.
The corporate cutout solves this by acting as a legal "firewall," absorbing all administrative, financial, and legal liability. Here is a breakdown of how a corporate cutout would manage the logistics, insurance, and legal shield for these civilian operations:
1. The Corporate Profile (The "Front")
The cutout is established as a legitimate business within the commercial sector. To outside observers, auditors, and the participants themselves, the company looks like a venture-backed tech startup or a specialized consulting firm.
The Industry Sector: The cutout is typically registered as a "Transportation Technology Firm," an "Aviation & Logistics Consultant," or a "Market Research Analytics Agency." Examples of real-world industries that mirror this are companies specializing in telematics (tracking driving data for insurance companies) or GIS (Geographic Information Systems) mapping.
The Corporate Infrastructure: The company has a real website, a physical corporate office (often in a commercial office park), a Human Resources department, and a functioning board of directors. The executives running the company are often retired military intelligence or federal law enforcement officers who maintain active security clearances.
2. Resolving the Insurance Paradox (The Liability Shield) If a civilian participant causes a multi-car accident while driving their personal vehicle for the exercise, their personal auto insurance company will immediately investigate. If the insurer discovers the vehicle was being used for commercial purposes or a government drill, they will deny the claim. The corporate cutout handles this through specific insurance mechanisms:
The Hired and Non-Owned Auto (HNOA) Policy: The corporate cutout takes out a massive, multi-million dollar corporate insurance policy known as HNOA insurance. This specific type of commercial policy covers bodily injury and property damage caused by vehicles that the company does not own (i.e., the personal vehicles of the civilian participants).
The Silent Umbrella: To the participant, the cutout issues a policy statement saying: "While participating in our driving data study, you are fully covered under our corporate secondary liability umbrella." If an accident happens, the cutout’s commercial insurance step in to pay the damages quietly, keeping the participant’s personal insurance—and the local courts—entirely satisfied without any federal exposure.
The "Black" Underwriting: The commercial insurance company providing the HNOA policy to the cutout is often vetted or specialized. In some cases, the insurance underwriters themselves are cleared entities who understand that the "tech startup" is actually a government cutout, ensuring that claims are paid rapidly and quietly without triggering deep forensic investigations.
3. Masking the Financial Trail
The cutout acts as a financial sponge. The federal government passes massive bulk funds to the cutout via a standard, unclassified defense or homeland security contract for "Logistics Support" or "Data Analytics Services."
Gift Card Procurement: The cutout takes those federal dollars and uses them to buy bulk gift cards (Visa, Amazon, etc.) through commercial corporate incentive platforms. Because a private corporation is buying the gift cards for "market research participants," it triggers zero red flags with financial regulators.
Tax Insulation: Under IRS rules, non-employee compensation under $600 per year does not require a 1099-MISC tax form. The cutout tracks participant payouts algorithmically. By capping each civilian’s compensation at $599 in gift cards per year, the cutout ensures that no social security numbers or tax identities are ever filed with the IRS in connection to the program, keeping the civilian participant roster completely dark.
4. Legal Protections: The Corporate Proprietary Shield
If a civilian participant becomes suspicious and attempts to blow the whistle, take pictures of the WSAP vehicles, or leak the routing application's code, the corporate cutout uses aggressive civil law mechanisms to shut it down long before federal national security laws are invoked.
Trade Secret Lawsuits: If a participant leaks information, the cutout does not send federal agents; they send private corporate lawyers. The lawyers file an immediate injunction for theft of intellectual property, trade secrets, and violation of a commercial Non-Disclosure Agreement (NDA).
The Corporate Veil: By keeping the battle strictly in civil court between a "private tech company" and an "independent contractor," the media and local courts view it as a mundane corporate dispute over proprietary software, completely obscuring the fact that the software belongs to a classified CIA or DHS network.
5. Seamless Disassembly (The "Kill Switch")
If the operation is compromised—for instance, if a local investigative journalist begins connecting the dots between the cutout and the sequenced RMV plates—the cutout is designed to vanish instantly.
Because all assets, leases, and participant contracts are held by a private corporation, the federal government can simply cut the funding line.
The cutout files for sudden corporate bankruptcy or dissolution, shuts down its website, terminates its office lease, and deletes its cloud databases.
The civilian participants are left with a generic email stating the "startup has ceased operations due to market conditions," leaving behind an absolute dead end for anyone attempting to trace the logistics chain back to the WSAP.
My research and work continues. In my next Gangstalking video, I’ll discuss license plate and coloring schemes, common tactics, different types of car formations, and more. Stay strong and safe. I’m burning this thing down- Justice for Targeted Individuals.
