“Sure pal, you can cut in front of me when you should’ve been in the lane already.”

I wave him in like I’m not irritated, even though I definitely am. Not at the driver per se, but at the ridiculous design of this on-ramp. It constantly causes traffic, even though a few well placed barriers and painted arrows could easily fix the problem.

It just slowed my whole commute down at the exact same time it always does… again.

This stretch adds five to ten minutes of travel time to every commuter that passes through it, and I’ve been watching it do that for years.

Ten years living here taught me to expect incompetence in bursts, not this kind of consistency. Traffic is supposed to fail noisily. This fails with discipline.

While I consciously feel mildly annoyed on the outside, subconsciously I’m more puzzled than surprised. This city should be a monument to efficiency. It sits southwest of Dallas, about thirty minutes from Waco, and was built around an ancient dirt mound discovered around 2030. Supposedly constructed by Native Americans centuries ago, it became a tourist attraction almost overnight.

Development followed immediately. The government poured hundreds of millions into a museum and cultural research center. The city grew fast. Too fast to feel accidental, and too expensive to feature this kind of incompetence.

---

Showers are usually where my thoughts behave themselves, assuming life doesn’t interfere first. The city’s water pressure regulations did their best, but I’d long since learned enough plumbing to ignore them. The water hit hard enough to be useful.

Two steady streams ran down the glass door. Separate at the top, then merging lower down into a single, thicker line. I watched them longer than necessary. They didn’t hesitate. They didn’t fight each other. Gravity handled the negotiation.

The onramp came back immediately. Same shape. Same stupidity. Two lanes forced into one without markings, barriers, or any attempt at order. A wide mouth narrowing into chaos and then surprise when it failed. I’d driven it every workday for years. Everyone had. No one seemed offended by it anymore.

What bothered me wasn’t that it was inefficient. It was that inefficiency had been chosen. It would have taken less effort to do it correctly.

I shut the water off and found myself already thinking in terms of angles and merge distances. That was usually how it started.

I moved a few Warhammer figures off my desk without really looking at them and told the AI to pull up the city map. I sketched lane guidance, added barriers, adjusted entry timing. Nothing elegant. Nothing clever. Just enough to stop the daily friction.

I packaged it into a short visualization and uploaded it to the city’s public bulletin board, mostly because that was where unfinished ideas went to die.

By the time I finished my coffee, the irritation had quieted. I grabbed my bag and left for work, confident the model was correct, and mildly annoyed that it existed at all.

---

It’s not that my job is boring. It’s that it stopped demanding anything from me years ago. I chose logistics analysis because I was good at it, and now I’m good enough that most problems resolve themselves before I consciously engage with them. At this point, my work occupies roughly the same mental bandwidth as eating or brushing my teeth. Necessary. Automatic. Rarely interesting.

That was probably why the on-ramp refused to let go of me. The solution had been stupidly obvious. Two lanes narrowing into one with no guidance, no painted arrows, no barriers to force an orderly merge. Just a wide invitation to improvise followed by collective surprise when improvisation failed. I’d driven it every weekday for ten years. Everyone had. Five to ten minutes lost each time. Thousands of hours evaporated annually because someone, somewhere, had decided this was acceptable.

I told myself I didn’t care whether anyone took my solution seriously. I even avoided checking the city’s bulletin board all day, which felt like proof. If nothing else, maybe a few neighbors would see it and start complaining loudly enough to force action. That kind of thing still worked sometimes.

When I got home, curiosity won.

The post was gone. Not recategorized. Not rejected. Just removed completely. I refreshed the page twice, more out of habit than hope. I had followed the submission guidelines carefully. There were a lot of them. Enough that the disappearance felt procedural rather than accidental.

I checked my email and found a short message waiting.

Technically valid, it said. Not aligned with planning objectives.

I stared at that phrase longer than was reasonable. How something could be technically valid and still unacceptable before the public ever saw it wasn’t immediately clear. Valid solutions usually survived scrutiny. They didn’t vanish quietly.

I pulled up my proposal again. Then the city’s publicly available planning objectives. One of them was explicitly stated as streamlining traffic for the highest benefit of the city. My model did exactly that. It reduced accidents. It improved flow. It lowered congestion-related emissions. If alignment existed anywhere, it was here.

I tried to explain it away. Politics, maybe. The area around the on-ramp was packed with high-end offices and expensive residences. Someone important might benefit from the congestion. Advertising exposure. Real estate pressure. Maybe they wanted drivers staring at the same candidate’s billboard for an extra thirty seconds while he smiled down from his recycled slogan about believing in the city. I doubted that translated into votes, but I’d seen stranger accounting decisions justified with less effort.

Still, none of it fit cleanly. The inefficiency was too precise. Too persistent.

Before I could settle on an explanation, another email arrived. Oddly fast, especially for off-hours.

I was flattered despite myself. Not enough to say yes, but enough to notice the timing. My traffic solution disappeared. A new problem appeared. Different scale. Different category. Same skillset.

I closed the message without responding.

The next morning, I was back on the on-ramp, watching the same careless merges play out exactly as before, and wondering why a problem that simple had been handled so deliberately.

---

A week later, the on-ramp still wouldn’t let go of me. “Not aligned,” my ass.

I’d been working in logistics for over twenty years. I’d seen bad plans, lazy plans, and politically compromised plans. This didn’t feel like any of those. It felt deliberate in a way that was hard to pin down, which only made it worse.

When something itches and I can’t ignore it, I do the same thing every time. I pull data. I organize it. I look for the place where my irritation turns into something measurable.

I started locally, then widened the scope. Traffic data. On-ramps and off-ramps. Accident frequency. Time-of-day congestion. Then I pulled comparable cities. Same population range. Similar growth curves. Similar reliance on personal vehicles. I even included cities with robust alternatives: trains, subways, bike infrastructure. I expected noise. I expected variation.

I didn’t get it.

The patterns lined up far too well. Congestion spikes. Accident clustering. Seasonal effects. Even the timing of slowdowns behaved similarly across places that had no obvious reason to resemble each other. These weren’t the worst roads in each city. They were the most consistently compromised.

That should have pointed to planning failure. It didn’t. Planning failures vary. This didn’t.

I added demographics next, telling myself it was just another way to rule things out. Education levels. Income. Household structure. Commuter behavior. The matches got tighter, not looser.

Areas with on-ramps like mine tended to serve the same kinds of people. Educated. Above-average income. Married with multiple kids or single with several pets. Conservative voting patterns. Larger vehicles. White-collar jobs that required physical presence. Long, predictable commutes.

I kept thinking they were similar to my situation, and every time I had to stop myself from using the more accurate word: exactly.

The longer I stared at it, the harder it became to believe this was something no one had noticed. If incompetence were the cause, someone would have fixed it by accident somewhere.

I take a break from my growing concern to check my email and find a new one from the city.

Another project. Another category. Efficient circulation. Different problem. Same tone.

By then they’d sent five of these. I’d declined every one. They kept coming anyway. It was hard not to notice that they arrived as my analysis deepened, not after I published anything.

I didn’t respond.

What bothered me wasn’t that the city rejected solutions. Cities do that all the time. What bothered me was the consistency.

If this were incompetence, it would be messier. If it were corruption, it would leave fingerprints.

Whatever this was, it behaved too cleanly for either.

---

The on-ramp had replaced my hobbies.

In the evenings, I used to paint Warhammer figures, play games, or experiment in the kitchen until I ran out of things that could reasonably be grilled. Lately, I spent that time reading city planning documents and analyzing highway infrastructure. It wasn’t healthier, but it was quieter.

I kept looking for supporting information and documentation, and surprisingly, my biggest problem is that I keep finding it. In fact, the information is shockingly complete and available.

At one point, out of boredom more than curiosity, I clicked on a case study titled The Impact of Footpath Traffic on Centralized Community Centers in Early Civilizations. I didn’t expect much. At best, I figured it might offer some insight into pre-industrial movement patterns.

It was mostly dry until I recognized a familiar landmark.

One of the examples referenced the mound at the center of my city. There were illustrations. Lidar scans taken before modern construction buried everything. Additional pathways radiated outward from the mound, some extending miles beyond what would later become downtown.

I stared at the diagrams longer than I meant to. I’d never seen these maps before. They weren’t on the official mound website. They weren’t referenced anywhere else I could find.

I pulled the images anyway and overlaid them onto the modern city map.

They didn’t line up with current roads. They ignored them entirely. The paths flowed organically, branching and recombining like tributaries feeding into a river. Small structures connected naturally to larger ones near the center. There were no forced merges. No abrupt narrowing. No obvious points of friction.

It was elegant.

I found myself irritated for a familiar reason. If city planners had even glanced at this, they could have done better. Whatever assumptions we made about early builders, they clearly understood movement.

I shut everything down for the night with the intention of coming back to it.

The next day, the case study wouldn’t load. No error. No redirect. Just nothing. The link existed, but it led nowhere. I asked the AI to locate the source or anything similar. It came back empty.

Completely empty.

I leaned back and stared at the screen longer than necessary before checking my email. There was a new message from the city.

It was the first time they hadn’t offered me a project.

---

I’d never been invited to a city planning meeting before, nor had I ever wanted to attend one. Still, it seemed like a chance to explain myself in person. Maybe I could convince them that the on-ramp solution made sense, even without referencing the older pathways.

I arrived on time, expecting a crowd of residents filtering into the city hall auditorium. Instead, I appeared to be the only one headed inside.

The room was large, clean, and brightly lit. Three city administrators stood at the front near a table arranged with laptops and neatly stacked papers. A single chair faced them. It was clearly meant for me. The setup looked formal, but unremarkable. I’d seen similar scenes archived on the city’s website.

They greeted me politely and introduced themselves. I nodded and shook hands, already rehearsing how to frame my proposal in terms they would find actionable.

“Thank you for coming, Mr. Smith,” one of them said. “We value residents who engage thoughtfully with city systems. Your proposal regarding the 10th Street on-ramp drew our attention.”

I felt a small, involuntary satisfaction. At least it had been read.

I handed them printed copies of my full report. They accepted them without comment and placed them on the table, unopened.

“Your analysis is accurate,” the administrator continued. “Your proposed changes would reduce congestion and improve throughput along that corridor. We arrived at similar conclusions during initial planning.”

The relief lasted half a second.

“Then why wasn’t it implemented?” I asked.

He smiled in a way that suggested the question had been anticipated.

“Because efficiency is not a singular objective,” he said. “Transportation systems participate in broader stability models. Movement speed affects distribution, timing, and downstream load across multiple domains.”

“Domains like what?” I asked.

“Economic activity. Resource access. Social pacing.”

The words were delivered evenly, like parameters being listed.

“The on-ramp is functioning within its intended range,” he continued. “From a systems perspective, it performs reliably.”

I frowned. “You’re saying the delay is intentional.”

“We’re saying the outcome is acceptable.”

That distinction landed harder than I expected.

“Then why invite me here?”

“Because your skillset is useful,” another administrator said. “You identify friction points others fixate on. We’d prefer to manage those points proactively.”

“Manage them how?”

“By ensuring adjustments appear responsive without destabilizing existing flows.”

I sat back, trying to map that sentence onto something human.

“You’d like me to find more problems,” I said slowly, “so you can decide which ones not to fix.”

The administrator nodded. “So we can reduce unnecessary disruption.”

The meeting ended shortly after. No signatures. No next steps. Just a clear sense that my role had been defined.

As I left, I realized I felt less deceived than I expected.

It was the most straightforward conversation I’d had in years.

---

The next day I went back to work like nothing had happened. I even picked my hobbies back up. It turns out grilling lamb neck is easier than it looks if you don’t overthink it.

The on-ramp research had swallowed my free time for weeks, but after the meeting the mental noise quieted. I stopped replaying conversations. I slept better. Whatever they were doing, it wasn’t my problem to solve anymore.

About a week later, an email arrived from the city.

A volunteer role and access to an internal portal with upgraded credentials. Information that wasn’t publicly available. Information that, according to them, “very few citizens” ever saw.

I told myself I could say no. I didn’t.

Access was hard to refuse. Maybe if I understood the system better, I could find a way to adjust my commute without destabilizing everything else. Maybe I could help my neighbors.

I accepted the role and received my credentials within minutes.

The data was not what I expected. I had assumed it didn’t exist, or that it existed but was poorly used. I was wrong on both counts. The models were dense, layered, and disturbingly competent. They updated constantly. Adjusted automatically.

It became clear that nothing the city did was reactive. Decisions weren’t improvised. They were selected from a range of acceptable outcomes and refined over time.

After a few months, I started flagging what I privately called “conflict points.” Places where friction accumulated. Areas where inefficiency produced secondary effects. I was later told the internal terms were “variance reduction” and “impact moderation.” The goal wasn’t to eliminate problems, but to make sure they expressed themselves predictably.

I learned how to make inefficiencies look accidental. How to shape delays so they felt natural. How to let minor harms occur in ways that prevented larger ones.

Car accidents happened. Traffic slowed. Stress accumulated. But not randomly. Not catastrophically. The system absorbed it. Smoothed it. Distributed it.

I stopped asking whether it was good. That question wasn’t useful. What mattered was that it worked. And that without it, things got worse.

Eventually, I saw my suggestions reflected in the city. Including the on-ramp. The delay was still there. Five to ten minutes, like always. But the chaos was gone. No sudden merges. No aggressive cutoffs. Just waiting.

I found I preferred that.

Sitting still was easier than being surprised.

---

I’m on the on-ramp again for my daily dose of PP. Patience practice.

I like to zone out during this part of the drive. I’d like to think the other drivers are as calm as I am now, but since they’re in front of me or behind me instead of fighting for position beside me, I can’t see their faces. I assume they’re fine.

Knowing why things happen this way is a relief. That was the worst part before, not the delay itself but the uncertainty. Now I can plan for the five to ten minutes and know they’ll arrive exactly when expected.

They never made the changes that would have sped things up. But they did smooth it out. Took the edge off. That counts for something.

The only real downside is having more time to look at that billboard. The same blowhard politician smiling down from his recycled slogan, clearer now without the distraction of merging traffic.

Still, this isn’t a bad way to live.

I can work with this.