Random AITA Story

Random AITA Story Random Reddit AITA Story

I was debugging a routine server sync error late on a Thursday night when I opened the outbound traffic log and realized...
06/02/2026

I was debugging a routine server sync error late on a Thursday night when I opened the outbound traffic log and realized the software our superintendent bought was secretly selling the depression scores and disciplinary records of 15,400 children—including my own niece and nephew—to insurance underwriters.

I am thirty-two years old.
I work as a Data Analyst for the Bridgewater Consolidated School District.
My desk sits in the basement of the District Office building.
The room is B-14.
It has no windows.
I administer the district Student Information System.

In August 2024, our district received a free software platform.
It was donated by BrightPath Educational Technologies out of Austin, Texas.
The CEO of the company stood in front of the Board of Education and presented it himself.
Our Superintendent signed the ninety-four-page Terms of Service that same night.
Two months later, the BrightPath Foundation awarded our Superintendent a one-hundred-twenty-thousand-dollar fellowship.
The money funded a three-week trip to Singapore and Helsinki for him and his wife.

On Thursday, September 18, 2025, I was at my desk at 22:14.
The BrightPath platform had failed a routine end-of-day sync.
The second-period algebra cohort could not pull up their assessments.
I ran a remote terminal session into our integration server.
The server is housed in a locked room two doors down from my office.
I opened the network monitor.

I looked at the outbound traffic counter.
The counter was running.

It was late on a Thursday night.
No classrooms were in session.
The server was transmitting fourteen-point-seven megabytes per minute to an external endpoint.
The encryption flag was turned off.
I piped the data stream to a local file.
I opened the file on my workstation.
It was full of unencoded JSON records.
I read the first record.
It contained a student ID.
It listed the grade as 10.
It listed a free lunch eligibility as true.
It listed two disciplinary incidents.
It listed a PHQ-A depression score of 19.
A score of 19 is in the moderate-to-severe range.
It listed the destination client as Sentient Analytics.

I opened a web browser.
I searched the company name.
Sentient Analytics is a firm in Virginia.
They sell juvenile-risk-scoring packages to family health-insurance underwriters.
The student in the file was fourteen years old.
The server was selling her depression score to an insurance company.

Twenty years ago, I was an eleven-year-old student in this same district.
I stepped between a seventh-grade bully and an eight-year-old boy in a hallway.
I pushed the older boy away.
The school suspended me for aggressive conduct.
My mother walked from her shift at the poultry-processing plant to sign the form.
She did not speak English well enough to read the box labeled ""Permanent Record.""
Three years later, a high school counselor opened my file.
He pointed to that single checkmark.
He denied my entry into the STEM magnet program.
It took me three years of petitions and hearings to get that mark expunged.
A child's data record is a gate.

On Saturday, October 11, 2025, I drove to Bridgewater East High School.
I was there to troubleshoot a token-rotation bug.
I walked into the guidance office.
The counselor was sitting at her desk.
Her screen showed the BrightPath clinical-screener interface.
She had just entered a PHQ-A score of 19 for Student ID 08-2247.
A girl was sitting on the wooden bench outside the office.
She wore a gray hooded sweatshirt with the hood pulled up.
She had headphones in.
She was staring at the floor.

I drove back to my basement office.
I opened the capture log.
I checked the timestamps.
The integration server had transmitted the package to Sentient Analytics at 14:52.
The counselor had entered the score at 14:47.
The transmission occurred exactly five minutes and twenty-three seconds after the data was typed.
The girl had been sitting on the wooden bench at the exact moment her score was sold.

(Read more in the first comment below)

I pulled the audit trail on my city's flood zone permits after a retired couple flagged an insurance discrepancy, only t...
06/02/2026

I pulled the audit trail on my city's flood zone permits after a retired couple flagged an insurance discrepancy, only to discover my boss—who is also my son's godfather—had spent thirty months secretly doctoring fifty-five federal elevation certificates to fake compliance. I am a Senior Permit Records Analyst for a Florida Gulf-coast city's Building Department.
I hold an ICC Permit Technician certification and a CRM credential.
The Records and Audit Division sits in a modular suite at the back of the second floor of city hall on Beach Boulevard.
The suite has three records analyst desks against the inside wall.
A Tyler Munis EnerGov platform terminal sits at each desk.
The platform retains a tamper-evident records audit trail on every document attachment and metadata change.
I teach junior technicians how to cross-check the FEMA Form 086-0-33 Elevation Certificate.
I walk them through the federal record of a structure's lowest-floor elevation inside a Velocity Zone.
I show them the licensed surveyor's seal and registration number at the top of page one.
I point out the date-time stamp of the on-site survey at the second header line.
I explain the deficit between the Base Flood Elevation and the lowest-floor elevation. Three days before the discovery, I gave a presentation at the Florida Floodplain Managers Association pre-conference Workshop.
I stood in the Tampa Convention Center east wing on a Saturday afternoon.
I spoke to twenty-eight permit technicians and records analysts from across the state.
My talk was titled Post-Issuance Certificate Replacement and the EnerGov Audit Trail.
I walked the room through three case studies of how document replacements show up at the audit-trail layer in the platform.
A records analyst in the third row asked how to handle a building official who countersigns post-issuance changes against a flag.
I told her in plain English to pull the audit trail, cross-check the surveyor chain-of-custody package, and file a Records Tampering Complaint to the Florida Office of Inspector General under Chapter 14 of the Florida Statutes.
A records analyst from Lee County in the fifth row wrote down exactly what I said. Conrad Vetterly is the city Building Official.
Conrad is also the godfather to my son, Mateo.
Eleven years ago, on a Sunday afternoon, we stood at St. Mary Star of the Sea parish on Beach Boulevard for Mateo's baptism.
Conrad stood at the font in a charcoal suit and a gold tie.
I held Mateo against my shoulder at the font while the parish priest read the rite.
We posed for the family photograph on the parish steps.
Conrad kept his hand on my shoulder for the photograph.
That framed photograph has sat on the kitchen bookshelf at my house for eleven years. On a Friday afternoon at fifteen-twelve, a retired couple came in through the lobby door of city hall.
Mr. and Mrs. Devereaux Mancuso approached the records counter.
Mrs. Mancuso held a one-page Wright National Flood Insurance Services policy review notice in her hand.
The notice indicated a possible elevation-data discrepancy on their Sea Oats Boulevard home.
The underwriter had flagged it on the policy renewal.
Mr. Mancuso filed a Homeowner's Records Request.
I accepted the request at the counter.
I pressed my hand against the counter edge to feel the laminate under my palm.
I told the Mancusos I would pull the permit packet and follow up by Monday morning. I walked back to my desk at fifteen-twenty.
I pulled the Mancuso permit packet from the EnerGov platform on the desk terminal.
The attached Form 086-0-33 showed the lowest-floor elevation at point-six feet above the Base Flood Elevation.
I pulled the licensed surveyor's chain-of-custody package retained in the surveyor-submission archive on the city side.
The surveyor's original showed the lowest-floor elevation at point-five feet below the Base Flood Elevation.
I closed the EnerGov terminal at sixteen-forty Friday afternoon. On Sunday afternoon at fifteen-eighteen, I sat at my dining table in Palmetto Beach.
I opened the city-issued laptop on the wood surface.
I set a glass of unsweetened iced tea at my elbow.
I logged in to the Tyler Munis EnerGov platform under the federal-tier records-of-decision custodian account.
I pulled the full audit trail for the Mancuso permit packet.
The audit trail showed the original elevation certificate was attached on March fourteenth at fourteen-twelve.
The user account was E.L.Trent at the Trent Geomatics submission account.
That original document recorded the elevation at point-five feet below the Base Flood Elevation.
A subsequent attachment was made on March twenty-first at oh-nine-fourteen.
The user account on the second attachment was C.Vetterly.
That was the city Building Official's records account.
The March twenty-first attachment showed the lowest-floor elevation at point-six feet above the Base Flood Elevation.
The audit trail showed no documentary correction note attached to the C.Vetterly replacement. I pressed my hand flat against the dining table edge to feel the wood under my palm.
I extended the EnerGov platform query window to all V-Zone permits issued in the past thirty months.
The query returned forty-seven single-family permits and eight multi-family permits.
I ran the audit-trail diff on each of the fifty-five permits in chronological order on a sortable table.
The pattern was systematic across all fifty-five permits in the period.
In every case, the licensed surveyor's original submission showed the lowest-floor elevation between point-four and one-point-seven feet below the Base Flood Elevation.
In every case, a subsequent attachment was made between four and twelve days later by user account C.Vetterly.
In every case, the elevation was revised upward by exactly the deficit.
In every case, the C.Vetterly attachment carried no documentary correction note.
In every case, the original surveyor-side attachment was retained in the hidden chain-of-custody archive on the system. I exported the audit-trail diff to a city-encrypted USB drive in the records-custodian audit case.
I opened the FEMA Map Service Center records portal on a federal browser session.
I queried the seven permits within the thirty-month window that had active Letters of Map Amendment requests on file with FEMA.
The FEMA Map Service Center retains a surveyor-side cryptographic hash manifest for any LOMA-adjacent submission.
The hash manifest on the federal server matched the original Trent Geomatics package.
The hash manifest did not match the C.Vetterly post-issuance replacements.
The digital proof of the tampering was locked permanently into the federal database, contradicting the city-side record on every one of the seven permits. (Read more in the first comment below)

I ran a routine forty-one-line database anomaly check on my state's master license registry, expecting zero results like...
06/02/2026

I ran a routine forty-one-line database anomaly check on my state's master license registry, expecting zero results like the two hundred and eighty-three previous Tuesdays, but instead I uncovered one hundred and thirty-seven fake identities tied to the same commercial warehouse—all authorized by the highest levels of my own department.

I manage the master Oracle relational database for the Virginia Department of Motor Vehicles. The identity document system holds seven million four hundred thousand active records. I write the SQL queries.

I manage the replication to the national federation. Every Tuesday at fourteen-hundred hours, I run an Address Concentration Anomaly check. My father was born in Ghana and arrived at Dulles International Airport on a student visa in 1982.

He worked in the night-shift janitorial team at the Medical College of Virginia Hospital for thirty-one years. He took the oath of allegiance at the federal courthouse in Richmond in November 1995.

On a Saturday morning in March 1997, he took me to the Richmond DMV office to obtain his first Virginia driver's license. I sat in the second row of orange plastic chairs.

The clerk printed his license on the production printer and handed it across the counter. His hands trembled slightly under the fluorescent ceiling fixture. He held the license up and told me it was the first card he had ever held in this country with his real name and his real photograph on it.

He put the license in his wallet. I wrote the forty-one-line anomaly query on a stay-at-home Saturday afternoon in April 2020. I designed it after an internal-audit briefing from New Jersey disclosed an identity-theft cluster involving fourteen licenses.

I presented the query to my supervisor in the second-floor conference room. She dismissed it as overengineering. She stated the compute budget allowed quarterly scans, not weekly. I scheduled it as a Tuesday-fourteen-hundred-hours job anyway.

The query flagged any residential address appearing on more than five active driver's license records. I had run the check two hundred and eighty-three times. The query had returned zero anomalies every previous Tuesday.

On Tuesday, October 7, 2025, at fourteen-forty-seven, my left monitor displayed the query result set. The result set contained one hundred and thirty-seven rows. Every row showed a different driver's license identification number.

Every row showed a different given name and surname. Every row showed a different date of birth. Every row showed a different photograph identifier. Every row showed the exact same residential address.

The address column read, in every one of the rows: ""3417 PARHAM RD, HENRICO, VA 23294"". I sat at the workstation. The cursor blinked at the end of the result set.

I refreshed the query. The result set returned the same one hundred and thirty-seven rows. I exported the result set to a CSV file. I saved the file to my encrypted home directory on the secure share.

I pulled the issuance metadata for each of the one hundred and thirty-seven license records. Every record had been entered into the system through the Real ID expedited-issuance queue. Every record carried the same administrative override credential in the originating-user field.

The credential read, in every record: ""SNORQUIST"". SNORQUIST was the assigned user ID of Deputy Commissioner Sterling Norquist-Falke. He was the Virginia DMV Deputy Commissioner for Customer Service Operations. He had executed the override on every one of the licenses between April 9, 2024 and September 26, 2025.

I queried the Social Security number field for the records against the Social Security Administration's verification service. The responses returned at fifteen-eleven. Ninety-four of the SSNs were in the nine-hundred-prefix range.

Numbers in the nine-hundred-prefix range are Individual Taxpayer Identification Numbers issued by the Internal Revenue Service. They are not valid identifiers on a Real ID Act-compliant driver's license. The remaining forty-three SSNs returned ""no match"" from the database.

They did not correspond to any living person. One hundred and thirty-seven licenses. Zero legitimate identities. At fifteen-forty-eight, I locked my workstation. I walked down the second-floor corridor to the office of Chief Information Security Officer Rosalind Achterberg-Menon.

She was at her desk reading a bulletin on her left monitor. I closed the door behind me. I asked for fifteen minutes. She set the bulletin down. I laid out the one hundred and thirty-seven rows.

She listened for nine minutes. She did not interrupt. She did not write anything down. At sixteen-eleven she opened the IT Security Policy on her right monitor. She scrolled to the section for Compromised Record Quarantine.

She read it. She closed the policy. She instructed me not to run the quarantine yet. She told me to take seventy-two hours to verify the address and verify the override chain.

On Wednesday evening at nineteen-forty-seven, I drove to 3417 Parham Road. The address was a single-story corrugated-metal warehouse. The street-facing wall had no windows. A vinyl sign above the loading dock read: ""APEX FACILITY SERVICES — Commercial Cleaning Contractor"".

A white cargo van with company branding was parked at the loading dock. I parked across the street under a sodium-vapor street lamp. I left the engine running. I left the heater on the low setting.

At twenty-eleven the steel pedestrian door opened. Seven people walked out in single file. They wore identical royal-blue cotton-blend janitorial uniforms. Five were women. Two were men. The first woman in the line was in her mid-twenties.

She walked to the rear of the van. She turned to climb in. She looked across the parking lot toward Parham Road. She looked at my car. She looked at me through the windshield for exactly three seconds.

Her face did not change. She climbed into the back of the van. The driver closed the sliding side door. The van pulled out of the parking lot at twenty-twelve.

I sat in my car under the sodium-vapor lamp. The pedestrian door closed. The warehouse went dark. I sat for four minutes. I did not pull out my phone. At twenty-sixteen I put the car in drive and drove back to my apartment.

On Thursday morning, I started a new query. I joined the database to the inter-state record-sharing federation log. I filtered the log for outbound replication events on the one hundred and thirty-seven Parham Road records.

Forty-one of the fraudulent licenses had been queried inbound by DMVs in ten other states. In every case, our system had automatically returned the response: VALID — REAL ID COMPLIANT.

Forty-one fraudulent Virginia licenses had been successfully used as breeder documents to obtain credentials across the country.
(Read more in the first comment below).

I ran a routine forty-one-line database anomaly check on my state's master license registry, expecting zero results like...
06/02/2026

I ran a routine forty-one-line database anomaly check on my state's master license registry, expecting zero results like the two hundred and eighty-three previous Tuesdays, but instead I uncovered one hundred and thirty-seven fake identities tied to the same commercial warehouse—all authorized by the highest levels of my own department.

I manage the master Oracle relational database for the Virginia Department of Motor Vehicles. The identity document system holds seven million four hundred thousand active records. I write the SQL queries.

I manage the replication to the national federation. Every Tuesday at fourteen-hundred hours, I run an Address Concentration Anomaly check. My father was born in Ghana and arrived at Dulles International Airport on a student visa in 1982.

He worked in the night-shift janitorial team at the Medical College of Virginia Hospital for thirty-one years. He took the oath of allegiance at the federal courthouse in Richmond in November 1995.

On a Saturday morning in March 1997, he took me to the Richmond DMV office to obtain his first Virginia driver's license. I sat in the second row of orange plastic chairs.

The clerk printed his license on the production printer and handed it across the counter. His hands trembled slightly under the fluorescent ceiling fixture. He held the license up and told me it was the first card he had ever held in this country with his real name and his real photograph on it.

He put the license in his wallet. I wrote the forty-one-line anomaly query on a stay-at-home Saturday afternoon in April 2020. I designed it after an internal-audit briefing from New Jersey disclosed an identity-theft cluster involving fourteen licenses.

I presented the query to my supervisor in the second-floor conference room. She dismissed it as overengineering. She stated the compute budget allowed quarterly scans, not weekly. I scheduled it as a Tuesday-fourteen-hundred-hours job anyway.

The query flagged any residential address appearing on more than five active driver's license records. I had run the check two hundred and eighty-three times. The query had returned zero anomalies every previous Tuesday.

On Tuesday, October 7, 2025, at fourteen-forty-seven, my left monitor displayed the query result set. The result set contained one hundred and thirty-seven rows. Every row showed a different driver's license identification number.

Every row showed a different given name and surname. Every row showed a different date of birth. Every row showed a different photograph identifier. Every row showed the exact same residential address.

The address column read, in every one of the rows: ""3417 PARHAM RD, HENRICO, VA 23294"". I sat at the workstation. The cursor blinked at the end of the result set.

I refreshed the query. The result set returned the same one hundred and thirty-seven rows. I exported the result set to a CSV file. I saved the file to my encrypted home directory on the secure share.

I pulled the issuance metadata for each of the one hundred and thirty-seven license records. Every record had been entered into the system through the Real ID expedited-issuance queue. Every record carried the same administrative override credential in the originating-user field.

The credential read, in every record: ""SNORQUIST"". SNORQUIST was the assigned user ID of Deputy Commissioner Sterling Norquist-Falke. He was the Virginia DMV Deputy Commissioner for Customer Service Operations. He had executed the override on every one of the licenses between April 9, 2024 and September 26, 2025.

I queried the Social Security number field for the records against the Social Security Administration's verification service. The responses returned at fifteen-eleven. Ninety-four of the SSNs were in the nine-hundred-prefix range.

Numbers in the nine-hundred-prefix range are Individual Taxpayer Identification Numbers issued by the Internal Revenue Service. They are not valid identifiers on a Real ID Act-compliant driver's license. The remaining forty-three SSNs returned ""no match"" from the database.

They did not correspond to any living person. One hundred and thirty-seven licenses. Zero legitimate identities. At fifteen-forty-eight, I locked my workstation. I walked down the second-floor corridor to the office of Chief Information Security Officer Rosalind Achterberg-Menon.

She was at her desk reading a bulletin on her left monitor. I closed the door behind me. I asked for fifteen minutes. She set the bulletin down. I laid out the one hundred and thirty-seven rows.

She listened for nine minutes. She did not interrupt. She did not write anything down. At sixteen-eleven she opened the IT Security Policy on her right monitor. She scrolled to the section for Compromised Record Quarantine.

She read it. She closed the policy. She instructed me not to run the quarantine yet. She told me to take seventy-two hours to verify the address and verify the override chain.

On Wednesday evening at nineteen-forty-seven, I drove to 3417 Parham Road. The address was a single-story corrugated-metal warehouse. The street-facing wall had no windows. A vinyl sign above the loading dock read: ""APEX FACILITY SERVICES — Commercial Cleaning Contractor"".

A white cargo van with company branding was parked at the loading dock. I parked across the street under a sodium-vapor street lamp. I left the engine running. I left the heater on the low setting.

At twenty-eleven the steel pedestrian door opened. Seven people walked out in single file. They wore identical royal-blue cotton-blend janitorial uniforms. Five were women. Two were men. The first woman in the line was in her mid-twenties.

She walked to the rear of the van. She turned to climb in. She looked across the parking lot toward Parham Road. She looked at my car. She looked at me through the windshield for exactly three seconds.

Her face did not change. She climbed into the back of the van. The driver closed the sliding side door. The van pulled out of the parking lot at twenty-twelve.

I sat in my car under the sodium-vapor lamp. The pedestrian door closed. The warehouse went dark. I sat for four minutes. I did not pull out my phone. At twenty-sixteen I put the car in drive and drove back to my apartment.

On Thursday morning, I started a new query. I joined the database to the inter-state record-sharing federation log. I filtered the log for outbound replication events on the one hundred and thirty-seven Parham Road records.

Forty-one of the fraudulent licenses had been queried inbound by DMVs in ten other states. In every case, our system had automatically returned the response: VALID — REAL ID COMPLIANT.

Forty-one fraudulent Virginia licenses had been successfully used as breeder documents to obtain credentials across the country.
(Read more in the first comment below).

I spent twenty-six years protecting the Virginia Lottery's randomness from street-level fraudsters, only to run a statis...
06/01/2026

I spent twenty-six years protecting the Virginia Lottery's randomness from street-level fraudsters, only to run a statistical routine on a Tuesday afternoon and discover the state's sole-source ticket printer had hijacked the algorithm to funnel twenty-nine million-dollar winning scratch-offs directly into convenience stores owned by his own brother.

My name is Dorothea Vickers-Pham.
I am fifty-three years old.
I joined the Virginia Lottery Commission's Office of Security and Integrity in January 1999.
I am a Certified Fraud Examiner.
I worked my first field-audit investigation ten weeks after transferring from the Richmond Police Department.
I shut down a forty-seven-thousand-dollar redemption fraud ring on the Peninsula in exactly four days.
Every quarter for thirteen years, I audited the Mathematical Assurance of Prize Distribution algorithm.
The MAPD is a software module.
It routes physical packs of scratch-off tickets to four thousand seven hundred licensed retailers.
It relies on a cryptographic pseudorandom number generator.
It is seeded by a hardware entropy source.
The mathematics guarantee that every winning ticket is equally likely to land at any retailer in the state network.
I trusted the math.

My training officer Mara walked me through the architecture on my fifth day.
She pulled a thick binder off a shelf at the field office.
She pointed to the flow diagram on the very first page.
She told me the algorithm was the one part of this agency nobody could beat.
She told me the fraud always happens at the cash register with the clerks.
She told me to stay focused on the retailer level.
I believed her completely.
I believed her for twenty-six consecutive years.

I had personal reasons to care about the integrity of the math.
My mother Alma drove school bus number forty-one on the Bensley-Bellwood route for thirty-one years.
She raised me alone on a single working-class salary.
On a Friday evening in October 1989, she parked her Plymouth Volaré at a Crown Gas station on Willis Road.
She handed the clerk a five-dollar bill.
She bought three Diamond Dazzle tickets.
She sat in the driver's seat with the engine idling.
She scratched the latex coating against the steering wheel using her right thumbnail.
The gold foil curled into thin ribbons and dropped onto her gray work skirt.
Three losing tickets.
She folded the cards into a tight square.
She pushed the square into the side compartment of her brown vinyl purse.
She looked at me and said that five dollars on a Friday was not much.
I knew the lottery revenue model explicitly targeted the working class.
I knew the people whose Friday five-dollar bills mattered most deserved a mathematically bulletproof game.

I designed a retailer-level Chi-squared goodness-of-fit test at my kitchen table in March 2024.
The test compares the actual physical distribution of top-tier winners against the expected uniform distribution.
For five straight quarters, the p-value returned between 0.08 and 0.61.
The numbers indicated uniform randomness within standard statistical tolerance.
The math was working.

Then came the afternoon of Tuesday, October 14, 2025.
I sat at my desk on the fourth floor of the headquarters building on East Main Street.
I queued the test against Game Number 2247.
Game Number 2247 was the Gold Rush Millionaire scratch-off.
It was a thirty-dollar ticket.
The print run contained exactly forty-eight one-million-dollar winners.
At fourteen-forty-seven, the script finished running.
The p-value was zero-point-zero-zero-zero-zero-zero-three.
Six decimal places.
A four-hundred-and-eighty-seven-sigma deviation from uniform randomness.

I leaned back in my chair.
The fluorescent light fixture in the ceiling tile hummed above my head.
I cleared the terminal and ran the test a second time at fourteen-forty-nine.
Zero-point-zero-zero-zero-zero-zero-three.
I executed it a third time at fourteen-fifty-one.
Zero-point-zero-zero-zero-zero-zero-three.

I picked up my office phone.
I dialed extension four-one-one.
I reached Chief Information Security Officer Wendell Achebe-Garrison on the third floor.
I read the exponential decimal sequence out loud.
I asked him to validate the run against the integrity-replicated dataset.
He asked me for forty minutes.
He called back at fifteen-thirty-three.
He confirmed the identical decimal sequence.
He explicitly stated the result was not statistical noise.

At fifteen-thirty-eight, I pulled the massive pack-routing log from the production server.
The log contained twenty-two months of shipping destinations.
I filtered the data to isolate the forty-eight packs containing a top-tier winner.
I exported the destinations into a fresh spreadsheet.
I sorted the rows by the retailer chain column.
Twenty-nine of the forty-eight million-dollar packs had been routed to thirty-four specific storefronts.
The stores traded under the names Quick Fuel, FastMart, and Capital Corner.
Those thirty-four storefronts represented just 0.72 percent of our network.
Under algorithmic randomness, the expected number of top-tier wins at those stores was 0.35.
The observed count was twenty-nine.

At sixteen-eleven, I opened the Virginia State Corporation Commission portal.
I queried the business owner records for the three chains.
All thirty-four stores operated under a single LLC called Cardinal Retail Holdings.
I immediately queried the LLC against the Delaware Division of Corporations annual-report database.
The entity was managed by the Stroud Family Irrevocable Trust.
The settlor of record listed on the document was Dalton Stroud-Endicott.
Dalton Stroud-Endicott was the founder and CEO of Patriot Game Printing, Inc.
Patriot Game Printing was the sole-source contract printer for every scratch-off game in the Commonwealth.

I sat completely still at sixteen-twenty-three.
I stared at the four browser windows open on my dual monitors.
The Chi-squared output.
The routing log.
The Virginia corporate filing.
The Delaware trust filing.
I picked up the phone and called Wendell.
I told him the thirty-four stores were owned by the brother of the printing company's CEO.
Wendell told me to get our director on the line immediately.
He started writing the administrative-search authorization while we spoke.

I called Director Trenton Halligrove-Brackenbury at sixteen-thirty-one.
I requested unrestrictable search authorization for the Henrico County facility under Virginia Code section 58.1-4022(B).
I closed my office door three minutes later.
I put the MAPD audit binder under my left arm.
I folded the Chi-squared printout into thirds and placed it in my breast pocket.
I walked to the elevator.

On the morning of Friday, October 17, I walked into the printing facility's west wing.
I bypassed the administrative suites and went directly to the printing-press hall.
I located a 120-gallon gray rolling cart marked for quality-control rejects.
I lifted the heavy plastic lid.
I dug through a layer of three hundred uncut press sheets.
I pulled out a massive card-stock sheet holding sixty uncut tickets.
I held it directly under the industrial press-hall lights.
I checked the four-point-font routing codes printed on the edge tab.
Ticket twelve was stamped CRH-0017.
Ticket thirty-seven was stamped CRH-0017.
Ticket fifty-four was stamped CRH-0017.
Three top-tier tickets on a single sheet were destined for the exact same store.
I slid the physical evidence into a Kapak bag.
I sealed it with red tamper-evident tape.

(Read more in the first comment below)

Address

Brickell, Miami
Miami Beach, FL
33129

Alerts

Be the first to know and let us send you an email when Random AITA Story posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to Random AITA Story:

Share