I was the senior streetlight telemetry engineer, and when I ran my own MQTT broker rollup against the federal grant compliance report, I discovered Glenn Mosley had inflated LED-converted fixtures by fifteen hundred and called dark streets converted.

I was the senior streetlight telemetry engineer, and when I ran my own MQTT broker rollup against the federal grant compliance report, I discovered Glenn Mosley had inflated LED-converted fixtures by fifteen hundred and called dark streets converted.

My name is Angela Chen. I am a Senior Streetlight Telemetry Engineer, state-licensed PE with NEMA controller certification. I have spent eleven years building a fixture-type and fault-event archive for the city’s 13,402-controller network that has never had a discrepancy attributable to telemetry—and Glenn Mosley has spent the past six months publishing a compliance report that says fifteen hundred sodium-vapor fixtures are converted LEDs.

I’ll tell you what the job is before I tell you what the broker showed.

Telemetry engineering is not traffic counts or opinion surveys. It is subscription messages from hardware that cannot negotiate with policy memos. My division maintains the broker endpoint, the commissioning database keys, and the field verification protocols when a controller disagrees with a ticket. When elected officials talk about “smart cities,” they imagine dashboards. I maintain the pipes underneath—topics, payloads, retained messages when the network partitions, reconciliation jobs when a contractor uploads the wrong pole ID.

That division of labor paid my salary and bought the rack humming behind my bench.

The complaint came in at 4:12 PM on a Tuesday: flickering streetlight, Cherry Lane at Willow. The 311 ticket carried a photograph from a resident—orange sodium bloom against dusk, the pole tagged with our asset barcode. I drove out with the diagnostic laptop belted into the passenger seat and the spare driver modules in a foam tray behind my seat.

At the pole I opened the lid, authenticated to the city’s VPN, and queried the MQTT broker for controller SL-44192’s last twenty-four hours of pings. MQTT is the city’s message broker—a piece of software every controller talks to on schedule. Each streetlight controller publishes a short JSON payload every sixty seconds: fixture type stamped at manufacture install, wattage class, relay state, cumulative kilowatt-hours tally, and a fault code when something fails. The broker stores nothing sentimental; it routes packets. The pings stacked in my query window like a heartbeat with timestamps down the left margin.

The fault code read DRIVER_DEGRADE. I deployed the bucket on the service truck, raised to fixture height, opened the LED head housing with the torque driver from my belt, traced the harness through the gasket to the driver brick clipped behind the reflector, and swapped the brick from stock on the truck shelf. I seated the connector until the latch clicked. I closed the housing, cleared the fault from the field service tablet tethered to my wrist strap, and waited on the platform while the controller transmitted three clean status returns sixty seconds apart.

The broker log printed STATUS_OK three times. I climbed down, wrote the one-page finding on paper before I rolled the cable: Driver-stage degradation; swapped and verified. I signed it with my PE stamp number and my employee ID. I scanned the PDF into the asset management queue myself. I did not delegate fieldwork I could execute because the resident who filed still stood at the corner waiting for the orange flicker to stop.

Three weeks later I stood in the training room with twenty-three field techs and one projected slide that showed the broker schema tree—topics, payload keys, timestamp offset rules. I pointed at the fixture-type field.

“The controller’s fixture-type field is locked at commissioning,” I said. “HPS commissions as HPS; LED commissions as LED. The field cannot be reclassified by report-side software. Whatever the grant spreadsheet says on Schedule B, the controller still tells you what it is every minute.”

A junior tech in the second row raised his hand. “How often is that field wrong?”

I answered without hedging. “Across five years and 11,840 commissioned LED conversions on this broker, never—when we verify against the commissioning log line by line. Across the entire 13,402-controller network, that field is the most reliable variable we own.”

Someone asked what happens if reporting software disagrees. I told them software reports what operators enter; controllers report what they are. I advanced to the next slide showing a sample ping split across two columns—hardware fields versus spreadsheet fields. The room stayed quiet the way rooms stay quiet when people realize their paperwork is not the same object as the pole.

That Friday after the FY2024 DOE Better Buildings progress audit closed clean, Glenn Mosley walked into my lab with a copper-finished LED desk lamp in both hands—a vendor gift from a Smart Cities conference. He set it on the bench beside my oscilloscope and brushed metal dust off the base with his thumb.

He said: “Engineer, your telemetry record is why we cleared that audit with zero findings.”

He used my first name once in that conversation—Angela—when he thanked me for the uptime metric staying above the federal 99.0% threshold for grant compliance. He said my MQTT pull was the anchor that held the network narrative together when federal reviewers asked questions.

He said: “You are the reason this city has a four-year zero-finding grant cycle.”

I believed him. I was not wrong to believe him. The belief rested on eleven years of controllers that behaved like machines and on audits that had never caught a discrepancy between his program-management tables and my samples—until they did.

The arsenal seed was already running while he talked. Every night at 22:33—the city’s published end-of-day rollup window—the broker consolidated cumulative kilowatt-hours and fault-state summaries from every controller into a single indexed bundle. My workstation job pulled that bundle, hashed the output, and appended it to a write-once archive only I maintained on my machine. I mentioned it once to a junior engineer who asked why I stayed late when automation could email results.

“Belt and suspenders,” I said. “The broker rolls the day’s pings at 22:33. I pull. I hash. I archive. Anyone could; nobody does. Belt and suspenders never hurt anyone.”

The desk lamp sat where he left it. Its cord brushed the rack fan grille when I walked past.

The surface crack arrived as email three weeks before the City Council Smart Infrastructure briefing. Donna Reyes, Riverside outreach, wrote:

Angela—we got six more dark-light complaints this month from Maple and Twelfth. The 311 system says they were marked resolved but the residents say the lights are still out. Just flagging.

I replied: Will check the rollup.

I filed the email in the outreach folder. Two parallel audit windows had my calendar pinned—internal capital reconciliation and the federal reporting dry-run—so I never pulled the geo-binned fault map for Riverside before the next reporting cycle closed. Eight days later the annual DOE Better Buildings grant compliance report went out with Schedule B attestation that carried my title block and PE license number pulled from Public Works personnel records.

At 22:33 that night the broker finished its rollup on schedule. The archive job hashed and wrote without drama. I walked past my workstation on the way to shut down the bench lights. The LED desk lamp Mosley gave me glowed warm against the wall.

It meant the network was alive and the day was closed.

It meant nothing else yet.

In October 2025 I sat in this same lab after dark with Mosley’s draft Schedule B on the left monitor and the internal capital-projects conversion spreadsheet on the right. The draft claimed 11,840 LED conversions and 99.4% aggregate uptime against the federal threshold. Mosley’s office ran program management schedules; mine ran what the controllers actually reported. His analyst had highlighted conversion batches by fiscal quarter; mine showed commissioning IDs tied to contractor invoices.

Rain hammered the narrow window facing the equipment yard. The rack fans pulled cool basement air across my wrists while I compared vendor completion certificates to his Schedule B narrative—spot checks only, five controllers per batch, because that was what the division memo authorized for routine filings.

I scrolled his LED total without opening my nightly rollup index—routine cycles used sample-based verification per division protocol. I countersigned the draft because his internal counts matched facilities’ booked conversions for that grant year and because I had never caught him moving a program table away from field reality.

When his analyst emailed asking whether I wanted additional MQTT extracts attached to the filing package, I wrote back: Not required for routine cycle—samples sufficient per DPW policy 14-B. I hit Send and immediately ran my personal 22:33 archive anyway out of habit. The hash wrote to disk while I rinsed my coffee mug in the break room.

The signature PDF printed on departmental letterhead. I walked it to the secure cabinet, slid it into the orange grant folder, and walked past the broker rack on my way out. Green LEDs blinked in sequence on the patch panel. The MQTT terminal window on my secondary monitor showed the previous night’s 22:33 job completed—green checkmark, hash stored.

If someone had asked me that night whether every LED line in Schedule B matched controller stamps, I would have said I followed protocol. Protocol was the mistake—not kindness, not ambition. Protocol.

In March 2024 I testified under oath before a state utility panel that was reviewing how municipalities measure energy savings from networked streetlight conversions. I wore a gray suit I keep for rooms with flags and microphones. The panel chair asked whether grant reporting should rely on capital-project schedules or field telemetry.

I said the program-management count is an operator’s attestation. I said the controller fixture-type field is the network reporting its own identity on hardware we commissioned. I said if the engineer is not pulling the broker rollup on a defined cadence, the engineer is verifying paperwork, not controllers.

A commissioner asked whether sampling ever misses systematic drift. I said sampling catches drift when drift is large enough to hit the sample—unless someone bridges the gap with narrative.

An attorney for a rural cooperative asked me to define MQTT in language his board could repeat. I said think of it as a post office every device writes to—each streetlight drops a postcard every minute with its identity printed at the top and its fault box checked if something broke. The board wrote that metaphor into their minutes without understanding the protocol layers underneath.

They entered my testimony into the public record. I walked out through a corridor lined with state-flag photographs, water glass still half-full on the witness table behind me. I filed the transcript in our compliance library and kept the nightly 22:33 job running exactly as before—because staffing never expanded to full reconciliation on routine cycles.

Three weeks after testimony, Mosley forwarded me a congratulatory email chain from the DOE regional liaison praising our city’s “transparent telemetry culture.” I starred the email and returned to sample validations—because praise is not verification.

In November 2022 a neighboring city’s DOE Better Buildings grant took a clawback after inflated LED conversion counts surfaced during a federal desk review. Their Public Works director asked our department for a technical consult; Mosley sent me.

I spent two days in their telemetry lab comparing broker stamps to their Schedule B narrative. The gap lived in program-management tables that counted “planned” conversions as completed. I told the DOE field auditor the structural fix is to never treat the capital spreadsheet as inventory—controller-by-controller, cycle-by-cycle, fixture-type field every time, with archived broker extracts signed by a licensed engineer.

I signed their consultation report with my PE stamp. I drove home and expanded my personal archive job to include checksum verification on every pull. I still did not run thirteen thousand lines against Schedule B every quarter—because nobody funded that many hours.

The Reyes email stopped being a courtesy flag the night I opened it beside the broker.

I pulled Donna’s thread into a second monitor and loaded the geo-binned fault map for Riverside and East Mill at quarter-mile resolution. Fifty-one controllers in the Maple-Twelfth-Northbrook quadrant showed FAULT_OPEN on the broker while 311 tickets in the same tiles read closed-resolved. The tickets carried Mosley’s division codes and closure timestamps inside the SLA window.

The under-count of failure events was not abstract geography. It was her neighbors standing under dark poles while the database said the work order succeeded.

I wrote controller IDs on a sticky note in permanent ink. I cross-checked five IDs against the broker ping stream—each still publishing FAULT_OPEN every sixty seconds. My tea sat on the desk until midnight. The building emptied around me except for the central-dispatch console three floors down.

The next evening at 22:33 I watched the rollup index populate line by line. Eleven thousand eight hundred forty controllers reported fixture-type LED. One thousand five hundred sixty-two reported HPS—still pinging, still commissioned as sodium vapor, still drawing power maps on our GIS layer in the color we use for legacy inventory.

I exported the fixture-type histogram to CSV and sorted descending by count. LED dominated the left column the way it always had on inventory charts—except the total row did not match Schedule B’s headline.

The grant Schedule B PDF on my screen claimed 13,402 LED conversions.

I opened the commissioning log in read-only from the enterprise archive. LED-stamped controllers: 11,840. HPS-stamped controllers: 1,562. The delta matched the inflation exactly—not commissioning lag, not staging brokers—hardware identity.

I cross-checked random HPS controller IDs against street-view photographs from asset management—same poles, older cobrahead silhouettes, sodium spectrum still visible on winter nights in the photo archive. Nobody had swapped heads without commissioning records; the records said HPS.

I pulled the geo map with fault overlays. Riverside and East Mill carried eighty-four controllers in active fault with no resolution ping in the stream. Schedule B’s fault summary listed zero open faults in those geographies.

I exported the fault stream for ninety nights and filtered for FAULT_OPEN persistence. The shortest duration in the eighty-four set was forty-one consecutive nightly observations; the longest ran one hundred twelve. SLA timers on paper did not align with ping persistence—paper closed tickets while hardware kept screaming.

I stacked printouts until the lab smelled like hot toner. The smell meant evidence in triplicate—broker truth, commissioning truth, grant fiction.

For eleven years 22:33 meant the day closed the way a bookmark means you stopped reading.

That night 22:33 meant the city had been telling me the truth every night while Schedule B told the federal grant a story about LED counts and resolved outages.

I closed the MQTT terminal session. I exported ninety days of 22:33 rollups to my encrypted drive. I photographed the commissioning log pages that listed HPS stamps beside latitude-longitude pairs. I opened the DOE Office of Inspector General complaint intake in a private browser window. I read the filing instructions twice. I did not call Mosley.

I ejected the encrypted drive and slid it into the locked drawer. I copied the same rollup folder to a second drive and labeled both with painter’s tape and the date in permanent marker. I stacked the drives in the steel box under my bench and turned the key until the latch clicked.

I locked the lab door from inside. I did not call the Public Works director—Mosley’s supervisor—or legal. I sat down and began the complaint draft at 12:14 AM.

The City Council briefing packet arrived by internal courier two days later. On the Smart Streetlight Network Performance Summary page, under the chart Mosley planned to project to elected officials, a footer line read: Senior Telemetry Engineer Attestation: A. Chen, PE.

I had not signed his performance graphics. I had not attested his inflated LED total or his suppressed fault table. The packet designed the council—and any federal observer in the room—to believe I had closed Schedule B with my license.

Six business days remained until the briefing.

At 5:38 AM that morning, before the administrative wing filled with meetings, I transmitted the DOE OIG complaint: ninety days of 22:33 rollups, commissioning log extracts, geo-binned fault map layers, Schedule B as filed, Donna Reyes’s email thread, and a notarized declaration under penalty of perjury. The upload bar crawled because the rollup attachments were large—night after night of plain CSV truth lined up beside PDF narratives.

The portal returned a case number. I screenshot the confirmation screen for my records and printed one copy on letter paper that went into the binder beside the hash tables. I wrote that case number in my new paper field log in blue ink—the first line on the first page.

Outside the basement windows the sky turned gray over the equipment yard. A salt truck rumbled past early sweep routes. The vibration rattled the loose pane Mosley never prioritized because it was not grant-eligible glass.

I drank office coffee that tasted like metal and waited until seven. The broker rack LEDs blinked through their startup self-test one more time before the daytime shift logged into VPN.

At 7:00 AM Mosley emailed a revised council agenda. He added me as co-presenter for the twenty-five-minute Smart Streetlight Network Performance Summary block.

“The council specifically asked for the senior telemetry engineer’s voice,” he wrote. “Thought you’d want to walk them through the rollup record yourself. You are the most credible voice on this.”

I read his message with the OIG acknowledgment already in my inbox.

I was still listed beside him with a handout block that would print my PE license under metrics I had never validated line by line.

Here is the pattern I tolerated and the window it occupied.

Six months from October forward—grant-cycle preparation through February filing—when I countersigned program-management drafts on sample validation instead of controller-by-controller reconciliation during overload. Three weeks from Donna Reyes’s first flag until I treated Maple-Twelfth as “will check” without checking while dual audits ate my calendar. Eleven years of treating 22:33 as archive habit instead of nightly attestation against federal paperwork because budgets do not pay overtime to read thirteen thousand lines every cycle.

Between October and February I attended two internal meetings where Mosley cited “network-wide LED penetration” from Schedule B language and nobody in the room—including me—asked him to read controller IDs aloud. I sat beside facilities managers who trust spreadsheets because spreadsheets fund replacement batches on time. I knew better. I still stayed silent because conflict with program management during a grant window buys nothing but emails.

I know what I saw and when. That is not the same as naming it while it arrived.

The afternoon before the briefing, Mosley worked in his office at Public Works with framed grant-program plaques on the wall and a brass Smart Cities conference paperweight beside his keyboard. Glass on his bookcase reflected the corridor whenever someone walked past. He rehearsed slide transitions aloud—uptime curve, conversion headline, photo of LED cobraheads on Main Street—timing clicks so each bullet landed before council attention wandered.

His printer spat draft handouts into a tray. He stacked them, tapped the edge on the desk until the pages aligned, and slid them into labeled folders for council pickup. On the phone with the City Manager’s chief of staff he walked through press lines—grant retention, infrastructure modernization, resident safety—nothing that required him to mention controller stamps or fault queues.

He spoke in the calm voice he used when federal reviewers asked soft questions he could answer with acronyms.

He believed elected members would ask two questions about performance summaries and move on when they saw a PE stamp on the deck—because that was what had happened four times before.

He told his executive assistant to add my full PE license number to the council handout beneath the attestation banner—numbers as punctuation under his narrative.

He never asked whether I consented. He never asked whether I had reviewed every cell that fed Schedule B. He believed my nightly rollup was belt-and-suspenders redundancy that proved his story without forcing him to open broker exports himself.

I did not get a private hallway. I got a published agenda and a binder.

The Smart Infrastructure Subcommittee chamber at City Hall opened at 10:00 AM with a horseshoe table, seven members, Public Works leadership, city counsel, three reporters with notebooks, and the observers named on the packet cover. Ceiling panels hid the HVAC roar; the projector threw Mosley’s first slide onto a screen hung between two flags.

City staff had placed water pitchers at the corners. A court reporter’s stenotype machine clicked softly when Holloway identified himself for the record. I set the rollup binder on the dais edge where counsel could see it without touching it—procedure I learned from contract disputes where evidence walks in on paper first.

Kevin Holcomb sat with his DOE Better Buildings lanyard visible—program manager, federal observer. Patricia Ng from the Inspector General’s office took a seat with a slim folio and no coffee cup, pen ready.

DOE OIG Special Agent Marcus Holloway introduced himself at the table before Mosley called the room to order. Holloway stated he had reviewed an active grant-integrity complaint filed under federal statute and would remain seated through the streetlight performance block. He placed a business card beside the microphone tray.

Mosley looked up from his laptop. “We were not notified of a concurrent federal inquiry. That is irregular procedure for a City Council briefing.”

Holloway did not raise his voice. “DOE OIG inquiries do not require advance notice to the grantee.”

Mosley turned his head toward me. Quiet: “What did you do?”

I did not match his volume. “I filed a DOE Office of Inspector General complaint six business days ago. I am the senior telemetry engineer. It is my job.”

He straightened behind the podium. “The fixture-type counts in Schedule B reflect forward-looking accounting consistent with municipal reporting flexibility. Conversion programs are continuous.”

I laid the fact sentence once. Facts are what I carry into rooms like this.

“Schedule B of the city’s DOE Better Buildings grant compliance report reclassifies 1,562 sodium-vapor streetlight fixtures as LED conversions and reports zero open faults in two neighborhoods where 84 controllers have been transmitting FAULT_OPEN for between forty-one and one hundred and twelve consecutive nights at 22:33.”

He said: “Operational normalization within the SLA window is consistent with municipal reporting practice.”

I opened the 22:33 rollup binder on the table between us—printed fixture-type tables, ninety nights of broker extracts indexed by date, the fault map with Riverside and East Mill shaded in hatch marks.

“The fixture-type field is hardware-stamped. The controllers transmit it every minute. Eighty-four fixtures in two neighborhoods have been transmitting FAULT_OPEN while Schedule B reports them resolved. You inflated fifteen hundred sixty-two sodium-vapor fixtures into LED conversions and hid faults to clear the federal uptime threshold.”

Before Holloway touched the binder, his hands rested flat on his folio—printed agenda, pen capped, thumbnail lined up with the margin. He watched Mosley’s mouth finish the SLA sentence while the projector still showed a green uptime graphic.

When I finished speaking, Holloway lifted the binder from the table center with both hands, read three controller IDs aloud into the official recording—digits clipped for the microphone—and set the binder open in front of him at page one. For two minutes he read line items without lifting his eyes toward Mosley’s face—only paper, only stamps, only my summary sheet with the hash values copied from the archive.

Holcomb had balanced his federal compliance report copy upright on his thumb during Mosley’s opening slides, spine toward the ceiling like a tent. When Holloway began reading controller IDs into the microphone, Holcomb lowered the book slowly, closed it with one hand, set it face-down beside his water glass so the DOE seal pressed against oak, picked up his phone, and held it dark-screened without unlocking. His thumb hovered above glass that stayed black until the clerk called the next procedural item on the council agenda.

Ng had leaned forward when Mosley started his uptime chart—pen pointed at the legend as if teaching. After the fault map slide showed beside Holcomb’s turned report, she slid her chair back four inches until the legs scraped softly, looked down at the geo printout on the witness table, looked across at the binder in Holloway’s hands, and fixed her eyes on the middle distance beyond Mosley’s shoulder—never back to his side of the dais for the rest of the block.

Mosley aligned his briefing packet to the table edge until the corners matched. He said: “I built this Smart Infrastructure division from the ground up. Forward-looking accounting has been our pragmatic practice for ten years.”

He gathered his laptop. He left the chamber without turning his head toward my seat. Holloway wrote 10:48 AM in his field notes beside Mosley’s printed name.

By end of week the OIG sustained the intake as an active grant-fraud inquiry. DOE suspended FY2026 disbursement pending review. Mosley’s federal-state advisory-panel nomination disappeared from the agenda packet posted online. City HR opened a disciplinary review on his tenure classification. The grant clawback language in the federal correspondence referenced false statements to an agency and misallocation categories I recognized from the 2022 neighboring-city file—same statute headings, different city letterhead.

None of that rewired eighty-four poles.

The reporters outside chamber doors asked me for comment on the record. I pointed them to the public filing once OIG released the receipt number. I did not stand for a camera quote about Mosley’s career. The story was never his biography. It was the delta between Schedule B and the broker.

Inside Public Works, technicians asked quieter questions—whether their overtime tickets would get scrutinized because telemetry flagged faults leadership had marked resolved. I told them the controllers already kept honest logs; leadership does not get to negotiate with physics.

That speech took thirty seconds. It cost me nothing. It changed nothing about the eight-month deferral council adopted when repayment crowded out immediate bucket truck deployments in Riverside and East Mill.

The afternoon light in my lab ran low and warm across the bench. Dust motes hung in the beam because I had not swept—there had been no hour for sweeping. The MQTT rack fan carried its steady note that masked the building’s heating cycle. Flux residue hung in the air from a harness repair I had finished that morning when a junior tech brought back a failed splice from East Mill. Mosley’s copper desk lamp still sat where he placed it in 2024—I had not moved it. The lamp worked when I clicked the switch. I left it off. Light came from the window and from the rack LEDs.

The 22:33 rollup binder rested on my desk, not on the rack shelf where older binders lived. Its spine wore a white label I wrote in block letters—the kind of label investigators expect when chain-of-custody matters.

Donna Reyes texted a one-line thank-you she did not owe me: “Maple says they see you in the data even if they don’t see you on the pole yet.” I did not reply with promises about truck rolls. I typed: Working on it. Honest. Bare.

The honest answer was repayment dollars had to land before bucket trucks could prioritize those eighty-four tickets without stealing from another capital line. Nobody elected wants to say that in a neighborhood meeting. Telemetry engineers end up saying it without microphones—by showing persistent FAULT_OPEN lines next to deferred work codes.

That night, when the broker fired the end-of-day consolidation on schedule and my archive job pulled the indexed bundle, I did not walk past the workstation on my way to the door. I stayed seated until the job logged complete. I sent the rollup to the printer at the end of the bench. I sent the fixture-type-by-controller table for all 13,402 stamps to the printer second. I sent the geo-binned fault map with Riverside and East Mill highlighted to the printer third.

Paper slid into the catch tray with heat still in the fuser. I signed each stack on the title block with my PE license number and the date. I squared the corners and slid them into a new hanging folder labeled “22:33—daily fixture-inventory and fault-state review, signed, filed.” I clipped the folder into the cabinet beside the rack instead of letting the day’s bundle live only on disk.

The minute on screen still read 22:33—the same end-of-day stamp it had used for eleven years. The consolidation still landed in the same second. What changed was not the clock. What changed was the motion that followed the paper landing in my hands: label, signature, file, repeat—the custody chain my 2024 testimony said should have run every night instead of living as private habit after everyone went home.

The same timestamp. Different responsibility after the printer stopped.

OIG sustained the complaint and ordered the city to repay $4.7 million in misallocated grant funds. Council adopted a remediation plan that deferred replacing eighty-four failed HPS fixtures in Riverside and East Mill for eight months while cash moved to repayment. Those eighty-four lights stayed dark or dim through seasons residents had already waited out while 311 tickets read resolved.

I will watch those controller IDs in the rollup every night until status_OK returns.

Repayment was the correct fiscal outcome.

The eight-month delay in those neighborhoods cannot be undone.

Mosley thought the Schedule B count was the inventory. He forgot the controllers were the inventory. He forgot that 22:33 every night is the minute thirteen thousand four hundred two pieces of hardware say what they are—and that fifteen hundred sixty-two HPS controllers classified as LED in his report had been saying it every night for half a year.

I opened a fresh field log from the bottom drawer—same manufacturer as the 2025 book, dark blue cover.

I wrote the date on the first page.

I wrote: Daily 22:33—fixture-inventory and fault-state review, all 13,402 controllers, signed, filed.

I set the pen in the gutter.

The blank lines waited.

Tomorrow I would drive Riverside again not to swap a driver on one pole, but to watch eighty-four fault lines until the trucks could come without stealing money from somebody else’s street. That watch begins at the broker, not at the speech podium.