Readit Saga, 8 Taylor Avenue, Monteagle, TN (2026)

06/03/2026

"I ran a routine blood test on a commercial cattle herd destined for a public school lunch program, and the results proved the operations manager was pumping them full of a banned, fatal antibiotic and forging the shipping manifests. I sat at the small portable veterinary laboratory bench inside secondary holding pen number three.
The workspace held a fluorescence microscope, a high-pressure liquid chromatograph, and a portable centrifuge.
I prepared a thin smear from a f***l sample with a malachite-green-acid-stain.
I identified the parasite as the larval form of dictyocaulus viviparous in under four minutes.
I administered the proper anthelmintic dewormer at the standard therapeutic dose.
My name is Joanne Kowalski.
I serve as a United States Department of Agriculture Food Safety and Inspection Service veterinary pharmacologist. Barry Landry sat at his desk on the second floor of the site office.
He was reviewing the previous week's truck departure manifests on his desktop terminal.
He told me the herd had received the standard feed formula and zero non-standard supplementation.
He claimed he runs a clean operation. The herd's average finishing weight was thirteen hundred and forty-two pounds.
That number was exactly one hundred and forty pounds higher than the standard finishing weight for the standard feed formula cycle. I drew a small blood sample from six representative head in commercial feed pen number five.
I spun the samples in the portable benchtop centrifuge at four thousand revolutions per minute for ten minutes.
I separated the serum from the cellular fraction.
I prepared all six serum samples for the benchtop high-pressure liquid chromatograph.
I loaded the tray into the autosampler.
I ran the routine pre-slaughter chemistry panel.
The chromatogram displayed a small but distinct peak at a retention time of exactly fourteen point two minutes. I locked the inspection station's laboratory bench from the inside.
I stared at the chromatograph's monitor on the benchtop terminal.
I picked up the portable USDA-issued satellite telephone from the lower drawer. That specific peak at fourteen point two minutes corresponded directly to a banned veterinary antibiotic compound known as chloramphenicol.
The United States Food and Drug Administration banned this broad-spectrum bacteriostatic antibiotic from use in food-producing livestock in nineteen eighty-six.
The ban was enacted due to a documented association with a rare and fatal human blood disease called aplastic anemia.
This specific commercial feed pen's processed beef product was scheduled for distribution to approximately six hundred and fourteen public school cafeterias.
(Read more in the first comment below) "

06/03/2026

"I reviewed the third-fiscal-quarter financial summary for our union's pension fund, and when I pulled the physical bank deposit slips to verify a tiny administrative overage, I found a three-million-dollar redirection of three thousand members' retirement assets to a political action committee.

My name is Luz Cisneros.
I serve as the senior pension fund auditor for the regional joint pension and welfare trust fund.
This fund belongs to Local Three-Sixteen of the Western Industrial Trades Brotherhood.
I calculate the contractual contribution rates across one hundred and forty-seven different employer contracts.
Our members work in the regional petrochemical refining industry.
They build components in the aerospace manufacturing industry.
They weld in the heavy-equipment fabrication industry.
They lay foundations in the commercial construction industry.
Three thousand and forty industrial trades members rely on my math.
I protect approximately one hundred and sixty-two million United States dollars in retirement-funded assets.
I have performed this duty for fifteen years across three regional labor unions.
My office sits on the third floor of Local Three-Sixteen's main union hall building.
I report directly to the federal fiduciary trustee panel under the Employee Retirement Income Security Act.
I operate entirely independent of the regional union boss's operational reporting chain.

Keith Booker is the regional union boss.
He has controlled Local Three-Sixteen for the past twenty-two years.
He dictates the union's day-to-day operational administration.
He navigates the collective bargaining negotiations with all one hundred and forty-seven employers.
He directs the political action committee endorsement decisions.
He presides over the quarterly membership meetings.
He stands on the main union hall's central elevated stage at the central podium.
He wears a dark-gray three-piece suit.
He wears a bright-red Western Industrial Trades Brotherhood neck-tie.
He holds the wooden quarterly membership financial vote gavel in his right hand.
He serves as a federally registered fiduciary trustee on the exact panel that oversees my work.

I sat at the senior pension fund auditor's desk on the second Tuesday morning of the fourth fiscal quarter.
I reviewed the trust fund's third-fiscal-quarter financial summary.
I scanned the general administrative-cost ledger.
The line item labeled ""national headquarters administrative transfer"" caught my attention.

The ledger recorded a third-fiscal-quarter transfer of approximately two hundred and forty-eight thousand seven hundred United States dollars.
I calculated the required standard cost-sharing rate.
The standard rate is exactly six-tenths of one percent of our quarterly assets-under-management.
The mathematically required transfer was approximately two hundred and forty-four thousand seven hundred United States dollars.
The reported transfer was exactly four thousand dollars higher than the required percentage.

I pulled the second-fiscal-quarter financial summary.
The transfer was four thousand dollars higher than required.
I pulled the first-fiscal-quarter financial summary.
The transfer was four thousand dollars higher than required.
I loaded the financial summaries for the preceding twelve fiscal quarters.
Every single quarter carried an approximately four-thousand-dollar overage.
The discrepancy totaled roughly forty-eight thousand United States dollars over three years.
I logged into the trust fund's accounts-payable disbursement system using my read-only fiduciary credential.
The system showed a single quarterly automated wire transfer of two hundred and forty-eight thousand seven hundred dollars.
The system listed the recipient account routing number for the national headquarters.
The system did not list the recipient deposit account number.
The deposit account field was completely blank.
I walked downstairs to the south parking lot at eleven oh five that Tuesday morning.
I drove seven miles to the regional commercial bank at the intersection of the southwestern arterial roadway.
I requested the physical deposit slips for all twelve automated wire transfers under my federal request authority.
The senior branch manager pulled the slips from the first-floor archived wire-transfer record vault.
He handed the twelve physical documents to me.
I drove back to the main union hall building.
I walked into my third-floor office at twelve forty-seven.
I locked my office door from the inside.
I placed the twelve physical deposit slips face down on my desk.

A spreadsheet can say whatever the person typing wants it to say.
A bank routing number tells you exactly where the money lives.
A bank deposit account number tells you exactly whose hands hold it.

I opened the accounts-payable disbursement system on my left monitor.
I checked the national headquarters' federally registered general administrative-cost remittance account number.
The legitimate account ended in the four-digit suffix four-two-eight-one.
I turned over the twelve physical deposit slips on my desk.
Every single slip printed by the bank carried a recipient deposit account number ending in nine-six-three-seven.
The money had never gone to the national headquarters.

(Read more in the first comment below)"

06/03/2026

"I spent six months drafting an environmental bill to protect our state's water supply, but when I checked the document's hidden XML code, I found my boss had secretly copy-pasted a massive loophole directly from the agricultural lobby's network drive.

I read legislation the way a software engineer analyzes source code.
A Microsoft Word document is never just a piece of paper on a screen.
It is a zip file packed with XML data.
It records exactly who touched it.
It records exactly when they touched it.
It records exactly where the keystrokes originated.
The ghost is always in the machine.

On a Tuesday morning, I sat at my dual-monitor workstation in the senior staff workroom on the third floor.
I was dissecting a four-hundred-page transportation bill.
It had been forwarded from the House for our senator's review.
I scanned page three hundred and twelve.
Down in subsection seventeen of the highway maintenance funding allocation, I spotted a two-word alteration.
The original House language said the agency ""shall"" conduct a safety review prior to releasing construction bonds.
The new Senate working draft said the agency ""may"" conduct a safety review.
A mandatory safety review was now an optional one.
I flagged the track changes immediately.
I typed a note stating this was a substantive policy change hidden under the guise of formatting clean-up.
I sent the marked-up draft back to the highway counsel at four ten in the afternoon.
By five o'clock, the highway counsel reverted the language.
Fifteen minutes later, the committee staff director walked right past my cubicle.
She did not stop to speak to me.
She did not need to.
The sneaky shall-to-may change had been neutralized.

On Wednesday morning, I opened the committee markup file for Senate Bill four-eighty-two.
This was my own water rights bill.
I had spent the previous six months drafting it.
I had combed through the state hydrology survey for the central plains aquifer system.
I had analyzed the federal Bureau of Reclamation modeling reports detailing the regional groundwater drawdown trajectory.
I had parsed state environmental quality department monitoring well data dating all the way back to nineteen seventy-eight.
I took all that dense science and translated it into enforceable legislative language.
The bill was designed to require commercial agricultural extraction operations pulling more than one thousand acre-feet per year to file annual reports.
It imposed a graduated state surface-water user fee on extraction volumes.
Crucially, it authorized the state to suspend extraction permits if the annual drawdown exceeded a specific model threshold.
That suspension authority was Section Four, subsection B.
That was the enforcement mechanism.

I scrolled to Section Four, subsection B.
A new phrase sat in the middle of the enforcement language.
""Excluding high-volume agricultural extraction operations under permit pre-existing the effective date of this act.""
Those words had not been there forty-eight hours ago.
That single phrase exempted approximately ninety-three percent of the extraction operations the bill was built to regulate.
The enforcement mechanism was entirely dead.

I stared at the monitor.
I scrolled up to the cover page.
The drafting credits still listed my name as the lead drafter.
My name was attached to a bill that now did the exact opposite of what I wrote it to do.
A coldness moved up from my chest and settled in my throat.

At nine forty-five, Paul Harrington walked into the senior staff workroom.
Paul was the Chief of Staff for Senator Vance Aldridge.
Senator Aldridge was the one who had introduced Senate Bill four-eighty-two under his own sponsorship.
Paul carried a cup of coffee.
He caught me staring at the screen.
He stopped at my desk.
""Chloe,"" Paul said.
He took a sip of his coffee.
""The Senator asked me to massage Section Four.""
He looked down at me.
""We needed stakeholder buy-in to get it out of committee. It is just the reality of governing.""
He called gutting six months of my work a massage.
""The markup is tomorrow at one,"" Paul said.
""Please print the committee copies tonight.""
Paul turned and walked out of the workroom.

I stayed at my desk.
I did not print the committee copies.
I closed the markup document.
I opened a Windows file explorer window instead.
I navigated through the shared drive to locate the committee markup file.
I right-clicked the file.
I clicked on Properties.
I checked the modified-by user account.
The modified-by user account belonged to Paul Harrington.
The modified-by timestamp read eleven thirty the previous night.

I stayed in the office.
I waited until the workroom cleared out at six forty-five.
I waited until the janitor rolled his cart past the door at seven twenty.
I waited until the entire floor was silent.
I copied the markup file from the shared drive directly to my desktop.
I copied it again to a USB stick.
I copied it a third time to my personal cloud storage account.
I left the original file on the shared drive untouched.

I right-clicked the desktop copy.
I changed the file extension from .docx to .zip.
The Microsoft Word icon vanished.
A compressed folder icon appeared in its place.
I double-clicked the zip file.
It expanded instantly into eleven folders and seven loose files.
I opened the folder labeled ""word.""
I right-clicked the document.xml file and opened it in a text editor.

Approximately eight thousand lines of XML code spilled down my monitor.
I ran a search for the inserted phrase.
The search jumped to line four thousand two hundred and eighteen.
The XML node wrapping the inserted phrase carried a revision tag.
The revision tag carried an Author ID.
The Author ID was ""AgCorp Legislative Affairs.""
It was not a Senate staff account.
It was not a state agency account.
It was a user account registered to AgCorp Lobbying LLC.
They were the largest agricultural lobbying firm in the state capitol.

I checked the timestamp on the revision tag.
It read eleven thirty PM.
I checked the copy-paste source tag.
The originating document was identified as a Word template stored on a network drive registered to AgCorp Lobbying LLC.
The XML node contained a user action tag.
The action was logged as a paste-from-clipboard operation.
The user account that executed the paste-from-clipboard operation was Paul Harrington's senate staff account.
Further down, the XML node preserved a pre-revision snapshot.
It contained my original drafting of Section Four, subsection B, preserved word-for-word.

I exported the XML node tree to a separate text file.
I exported the revision metadata table.
I exported the modified-by user account history spanning the last fourteen days.
I sent all three exports to the workroom printer.
I walked to the printer and collected the pages.
I checked every single page to ensure nothing was missed.
I locked the printouts inside my filing drawer.

I picked up my personal cell phone.
I called my sister in Portland.
I told her exactly what I was looking at.
I told her I was taking the file to a rival senator's office in the morning.
The rival was Margaret Holloway, a freshman who ran on a clean-water platform.

(Read more in the first comment below)"

06/03/2026

"I kept meticulous paper logs at a four-hundred-bed disaster relief shelter while the prime contractor smiled in my face—until I realized her digital inventory was quietly writing off sixty-one pallets of infant formula and food as ""damaged"" while families slept in their cars. I am the state-deployed logistics coordinator at a four-hundred-bed hurricane shelter.
On day twenty of operations, I stood at the Hiland Park High School receiving dock in Panama City, Florida.
It was six in the morning.
A junior logistics specialist named Maris stood beside me with a clipboard and a pen.
I walked her through the receiving process before any pallet crossed the dock line.
You stamp the bill of lading.
You write the pallet count and product class on your paper Bingo-Card line for the day.
You watch the forklift badge reader log the pallet move with the operator badge ID.
I timed a single pallet from the receiving-dock entry to the shelter floor on a stopwatch.
Four minutes and twelve seconds from gate to cot bay.
I watched the telematics log the pallet move.
I tabbed to the workstation and watched the day's intake counter increment by one.
The paper log, the electronic feed, and the forklift telematics all agreed.
My name is Rocio Holt.
I am a FEMA-certified Logistics Section Chief. I had met the prime contractor, Patrice Lennox, three years earlier at a Lee County after-action.
It was four-thirty in the morning in the break area on the fourteenth day of the response.
She brought me a hot Cuban coffee in a paper cup.
She told me I was the only logistics chief she had worked with across twelve deployments who actually kept the manual paper log.
She told me the paper line is the line that holds when the electronics go down.
She even typed up a one-page recommendation letter for my FEMA certification on her company letterhead.
I framed a copy of that letter the day my certification card came through.
The frame still hung above my desk at home in Tallahassee. On day thirty-eight of operations, a retired Bay County schoolteacher named Ms. Ramirez found me at the workstation.
She told me the Trotter family had been waiting for infant formula since two o'clock.
The digital system said we had eight pallets in inventory.
I walked the shelter myself.
I counted the pallets at the south end of the gymnasium past the children's curtained section.
There were two open pallets.
One-point-four pallets remaining on the floor.
Not eight.
I pulled formula off the open pallet.
I walked it to the cot bay and gave the bottle to Mrs. Trotter myself.
I watched her five-month-old take it.
I went back to the workstation and wrote one line in my pocket notebook. Day forty-one.
Twenty-two-eighteen at night.
I sat at the desk in my hotel room on the fifth floor of the Holiday Inn Express.
I opened the forklift yard-scan export on my laptop.
I placed the paper log photographs from my phone next to the keyboard.
I matched the day-forty-one paper line to the day-forty-one yard-scan.
The paper log showed one hundred and forty-two pallets received.
The forklift yard-scan showed one hundred and sixty pallets crossing the perimeter gate.
The difference was eighteen pallets.
I checked the digital variance report for the day.
It showed eighteen pallets written off as in-transit damage.
My paper log had zero in-transit damage entries.
The forklift telematics showed the eighteen pallets sitting on the staging apron for between twelve and ninety minutes.
The yard-scan showed them departing on a sub-trailer back through the perimeter gate. I closed the laptop.
I did not pick up the phone.
I lay down on the bed without taking off my shoes. I exported the bill of lading receiving-party data for the departing sub-trailers.
The receiving party was a single shell vendor named Coastal Triage Logistics LLC.
I opened the Florida Division of Corporations portal and searched the entity record.
The entity had been registered three days before the hurricane made landfall.
The registered agent was located at a single residential address in Lynn Haven, Florida.
That address matched the home address of Patrice Lennox's brother-in-law. (Read more in the first comment below)"

06/03/2026

"For eight months I falsified official state drought records, telling 12,400 people their water supply was fine while an agribusiness corporation drained the reservoirs down to 9% capacity. I am Constance Aldridge-Mabena.
I have spent twenty-seven years with the Virginia Office of the State Climatologist.
I maintain a 147-station monitoring network across the Commonwealth.
Rain gauges, soil-moisture probes, and dataloggers.
I have walked to 131 of those 147 stations on foot.
In March, I stood at the edge of the Elkhorn reservoir parking lot.
I calibrated Station 47, a Hydrological Services TB3 tipping bucket mounted on a galvanized post.
I poured measured volumes of water through the funnel.
100 milliliters.
200 milliliters.
500 milliliters.
I counted the tips against the expected values.
Every tip was within 0.3% of specification.
I filled out the calibration log on a clipboard.
I signed it.
I photographed it with my phone.
I know my machines are accurate.
I publish the Virginia Monthly Drought Monitor.
This document determines when water-use restrictions begin.
It dictates when reservoir priority shifts from agriculture to drinking water. Secretary of Natural and Historic Resources Whitfield Beale-Stenmark called me to a meeting in January 2025.
He arrived at my Blacksburg conference room at 10:00 in the morning.
He brought his chief of staff.
He brought a binder labeled ""Drought Methodology Review.""
He set the binder on the table between us.
He smiled.
""The Valley growers are concerned that a premature drought escalation could trigger water-priority shifts during planting season,"" he said.
""I'd like the OSC to apply conservative methodologies in the monthly assessments.""
He did not raise his voice.
He used soft language.
He framed it as a scientific choice. He left the room.
He left the binder on the table.
I opened it.
The binder contained no methodology.
It contained SVAH's quarterly water-usage projections for the 2025 growing season.
Corporate documents sitting in a cabinet secretary's briefcase. I looked at the numbers.
SVAH projected a water demand of 47,000 acre-feet.
I checked the fourteen-reservoir system's available supply.
31,000 acre-feet.
A 16,000 acre-foot shortage.
If I declared D3 Extreme Drought, SVAH lost their water to municipal drinking priority.
If I declared D1 Moderate Drought, the law did nothing.
I closed the binder.
I looked at the raw data coming from my twenty-two Shenandoah Valley stations.
Reservoir levels were at 17% of capacity.
Soil-moisture deficit was 14.7 inches below field capacity.
The Palmer Drought Severity Index read negative 5.1.
All three metrics triggered a D3 classification.
I sat at my desk.
I typed D1.
I signed my name. I printed the report.
I submitted it to the state publication system.
I looked at the miniature brass rain gauge on my windowsill.
My dissertation advisor had given it to me twenty-two years ago. In the summer of 1988, the well on our farm went dry.
I was eighteen.
My mother carried water from a neighbor's spring for three weeks.
Four five-gallon jugs per trip.
Two trips per day.
I weighed one jug on our bathroom scale.
41.7 pounds.
Forty-two round trips.
168 jugs.
Seven thousand pounds of water carried on foot.
I became a climatologist because of those jugs.
I had published 168 consecutive accurate monthly reports since my appointment.
One for each jug.
Until Whitfield Beale-Stenmark.
The Secretary called me to his Richmond office on March 3.
He gave the same instruction.
I typed D1.
We had a working dinner at the Governor's Mansion on April 11.
""Let's keep the assessment measured,"" he said between the salad and the entree.
I typed D1.
May.
June.
July.
August.
Eight consecutive months. Then I drove to the Elkhorn Municipal Reservoir on September 27.
I walked past a chain that read ""NO ACCESS — WATER LEVEL UNSAFE.""
The water had retreated four hundred feet from the shoreline.
Six feet from the remaining brown pool, a child's Frozen water bottle lay half-buried in the cracked gray clay. (Read more in the first comment below)"

06/02/2026

I was the lead biostatistician on a fourteen-million-dollar oncology trial, and when I pulled the electronic data capture audit logs against the Statistical Analysis Plan, I discovered our Chief Medical Officer was quietly rewriting a failed clinical trial into a positive one just days before the FDA submission. Three months earlier, I sat at a workstation on the ninth floor of the CRO's biostatistics suite.
I walked a junior statistician named Dev through reading a version-control diff.
Dev had two documents open side by side on his monitor.
"Read the original definition aloud," I told him.
He read paragraph 4.2.
It defined the primary endpoint as progression-free survival.
The interval ran from randomization to radiographic progression or death from any cause.
"Now read the amendment's version," I instructed.
The amended paragraph contained a new clause.
It specifically excluded events adjudicated as non-treatment-related by the independent review committee.
Dev opened SAS on his second screen.
He ran the log-rank test using both definitions.
The exclusion clause moved the p-value from 0.062 to 0.041.
It flipped the trial from non-significant to significant on the exact same data. I picked up a pencil from my desk tray.
I underlined the new clause on the printout.
I clipped the page to the version-control log.
I locked both documents inside my filing cabinet.
A biostatistician's filing cabinet serves as her laboratory bench.
Every drawer contains a version of the truth that a sponsor cannot alter later. I ran the blinded interim Kaplan-Meier curves for the Data Monitoring Committee later that week.
I kept the door closed.
I tilted my monitor so nobody walking past in the corridor could view the survival curves.
The curves diverged slightly at twelve months.
I saved the output as an encrypted PDF.
I printed one copy for the sealed DMC envelope.
I wrote March 14, 2026, on the flap in blue ink.
I locked the envelope in the second drawer. Two weeks later, the sponsor hosted a leadership dinner.
We ate at a restaurant in Research Triangle Park.
Garret Lyle sat directly across from me.
He was the sponsor's Chief Medical Officer.
He was tall, with silver hair and a voice that always remained one degree softer than everyone else's.
He picked up the pitcher and refilled my water glass himself.
He told the table he had worked as a physician for twenty-three years before joining the industry.
He said he always thought about patients first.
He said he trusted the CRO's statistical team because of our careful work.
He looked right at me when he said it.
I set my water glass down on the white tablecloth.
I did not say a word. Two days after that dinner, I logged into the electronic data capture system.
I reviewed adverse-event submissions for the weekly query cycle.
The clock on the wall of the CRO operations room showed 17:30.
The regulatory operations team members were logging off for the day.
A nearby printer finished its final cycle and fell silent.
The fluorescent lights buzzed overhead at their normal pitch.
Seventeen-thirty was the daily submission cutoff.
The queue closed until the following morning. One specific report caught my attention.
Subject 10047.
The patient had a Grade 3 neutropenic fever.
During the previous query cycle, it was classified as treatment-related.
Now it was classified as unrelated.
This sudden reclassification had not triggered the DMC review flag.
I checked the audit trail immediately.
An unrecognized user ID had entered the status change at 16:58.
The change reason field cited operational alignment per sponsor medical review. (Read more in the first comment below)

06/02/2026

I spent six years building an impeccable food-safety record for our plant, only to discover my boss had been using my spotless signature to secretly ship 184 lots of Listeria-positive meat to ten distribution centers just to protect his operations bonus. My name is Lupe Vargas. I am the HACCP verification lead at the Garden City plant. I sign the monthly Sanitation Standard Operating Procedures verification report. Seven red 3-ring binders sit on the credenza behind my desk. They are labeled by month in my own black marker. A signed monthly verification report sits in the first divider of each. Behind that report are ten years of swab counts and SSOP entries. Three years ago, our plant earned its first SQF Level 3 certification with no major findings. Dale Crane stopped by my office. He brought a case of plant-branded hot sauce. He carried a framed copy of the audit letter. "The auditors cited your verification work as the cleanest HACCP alignment in the company," he said. He called me by my first name. He set the framed letter on the credenza and walked out. I hung the frame the next morning. I believed him. Six weeks ago, Rocio Bustamante sent me an email at 5:08 in the morning. She was the second-shift line lead. "Saw a relabel ticket queue at 04:50 on Tuesday," she wrote. "Pre-cook codes for finished-product totes." I read it at my desk with my second coffee. I replied that I would check the print-server log. I filed the email in a folder labeled SHIFT FLAGS. I did not check the log. Then Tomás came to my office. He was the sanitation supervisor. He leaned on the doorframe with a coffee in a plant-branded mug. He brought a paper printout from the luminometer service log. He wanted me to overturn the 04:50 ATP reading on the line 3 conveyor takeoff. He claimed the reagent was mishandled and the swab was reading dirty when the field was clean. I pulled the line-3 schedule. I pulled the prior shift's wash-down log. I pulled the swab batch number. I checked the luminometer calibration record from the morning service. The reagent was inside its window. The calibration record was current. "The swab is valid," I said. "Hold and re-clean line 3 takeoff." Tomás took the printout and walked back to the floor. I wrote the corrective action in pencil on the verification page. I initialed it at the corner. I closed Tomás's swab-failure file at 16:40. I had thirty minutes before the end of the routine month-end reconciliation window. The line-printer print-server at the plant logged every label job. It logged the origin, lot code, timestamp, and operator. It also logged a SHA-256 hash anchored to the print queue at the moment of ex*****on. The log was append-only. The hash did not rewrite itself. I pulled the July print-server log onto my second monitor. I opened the lab LIMS Listeria-positive holds file on the third monitor. I looked at the lab posts between 03:30 and 04:45 across July. Twenty-eight finished-product lot codes posted Listeria-positive. I looked at the recodes across the same month. Twenty-eight finished-product lot codes were recoded to pre-cook codes between 04:50 and 05:00. I looked at July 9th. The lab post at 04:42 was Listeria-positive. The label printed at 04:50 carried a pre-cook code. Eight minutes between lab post and relabel. I built a side-by-side spreadsheet. Column A: lab LIMS post time. Column B: lab LIMS lot code. Column C: lab LIMS result. Column D: print-server relabel time. Column E: print-server new lot code. Column F: minutes between. July ran twenty-eight rows. I expanded the date range to the full seven months of the current and prior quarter. January through July. One hundred eighty-four rows. One hundred eighty-four finished-product lots tested Listeria-positive at the lab. One hundred eighty-four finished-product lot codes were recoded to pre-cook codes within eighty minutes of the LIMS post. I stopped typing. I saved every capture to a personal encrypted drive. I walked to the floor for a glass of water. I walked back to my office. The supplier quality council binder was open on my left monitor. Dale had sent it to me for review the prior Friday. Slide five listed me by name under HACCP verification. It displayed my name and certification number. The slide was designed to show the major retail buyers and the FSIS District Supervisor that the plant's HACCP verifications were independent of operations. I had not consented to that attribution. My signed verifications were the cover for the 04:50 relabel jobs. (Read more in the first comment below)

Readit Saga

06/03/2026

06/03/2026

06/03/2026

06/03/2026

06/03/2026

06/02/2026

06/02/2026

Address

Telephone

Website

Alerts

Contact The Business

Shortcuts

Share

Category