Frank
In 1969, a Chicago Chevrolet dealer named Fred Gibb used GM’s internal Central Office Production Order system to build 427 cubic inch Camaros that corporate policy explicitly prohibited. By routing the order through a fleet-purchasing process never intended for performance vehicles, he produced cars GM officially denied sanctioning.
The author draws a personal parallel between Gibb’s approach and navigating systems as a neurodivergent person, distinguishing between following rules and understanding what those rules actually protect. The piece argues that when restrictions are performative rather than substantive, finding structural gaps is not defiance but a form of careful reading.
Somewhere in a Chevrolet parts catalog from 1969, buried between fleet vehicle options and police package equipment, there’s a line item called COPO 9561. Central Office Production Order 9561. It doesn’t look like much. It reads like a parts requisition, like something a purchasing manager in Flint would skim past on a Tuesday afternoon without blinking. But that dry little alphanumeric string is the reason a teenager could walk into a Chevy dealership in 1969 and drive home in a car with a 427 cubic inch engine shoved into a Camaro that General Motors never officially sanctioned, never advertised, and, in a very real sense, never wanted to exist.
That’s the whole story, right there. Except it isn’t.
The reason COPO 9561 existed at all is that a Chicago Chevrolet dealer named Fred Gibb figured out that GM’s Central Office Production Order system, designed for fleet customers to spec out unusual commercial vehicles, had a hole in it big enough to drop a big-block V8 through. GM had a corporate policy. No engine over 400 cubic inches in a mid-size or smaller car. The suits in Detroit had made a gentleman’s agreement with the insurance industry and the safety lobby, and they were sticking to it. Publicly. On paper.
But the COPO system? The COPO system was internal. It was for fleets. It was for the Post Office ordering Novas without back seats and rental companies configuring Impalas with specific transmission codes. It wasn’t meant for performance. Nobody said you couldn’t use it for performance. Those are two completely different things.
Fred Gibb saw the gap. He ordered 50 COPO 9561 Camaros from the factory, cars with the 427 L72 stuffed into an engine bay that was technically rated for something half that size. Then Vince Piggins, a performance engineer at GM who absolutely knew what was happening and absolutely helped it happen, made sure the production line cooperated. And just like that, Chevrolet was building a car it had officially forbidden itself from building.
I have loved this story for thirty years. Not because I’m some kind of rebel or because I think rules are stupid. I think rules are fine. I follow most of them. I’m the guy who reads the entire terms of service, which, yes, I know, that’s its own kind of problem. But I love this story because it is a perfect, crystalline example of something I have watched play out my entire life: the system didn’t reward the people who followed the policy. The system rewarded the people who understood the policy well enough to find the seam in it.
That distinction matters more than most people want to admit.
Here’s the thing about being neurodivergent in a world built for neurotypical people. You spend a lot of time being told you’re doing it wrong. Not the actual task. The task is usually fine. The way you’re doing it, the way you got there, the fact that you skipped steps three through seven because your brain already ran the simulation and steps three through seven were redundant, that’s the problem. Y’all want the process. Y’all want the compliance. You want me to fill out the form the same way everyone else fills out the form, even when I can see that the form is asking the wrong questions.
I was diagnosed with AuDHD when I was in my mid-fifties, which basically means I spent four decades watching myself exploit the COPO system without knowing that’s what I was doing. I could not function inside rigid structures. I was not, and am not, good at performing compliance for compliance’s sake. But I was always, always good at understanding what a system was actually trying to accomplish, and then finding the fastest, most direct path to that outcome that the system’s rules technically permitted.
That got me called a troublemaker a lot. It also got things done.
The COPO Camaro is the automotive version of that. Fred Gibb wasn’t breaking the law. He wasn’t even breaking GM’s rules, exactly. He was using a process for something it wasn’t designed for, because he understood that the restriction existed at the policy level and the COPO system existed at the operational level, and nobody had explicitly connected the two. He read the fine print. He did the thing. He built one of the most sought-after muscle cars in American history as a direct result.
Let’s be honest about what GM’s restriction actually was. It wasn’t a safety rule. It wasn’t an engineering limit. It was a PR move, a political calculation made by executives who were worried about insurance rates and congressional hearings and Ralph Nader standing outside their front door with a clipboard. The actual engineers, the Vince Piggins types, knew the cars could handle the power. The chassis guys had already been running 427s in the Corvette. This wasn’t uncharted territory. The restriction existed to manage appearances, not to manage reality.
And Gibb’s COPO order revealed that for exactly what it was. If the restriction were real, if it were about engineering integrity or genuine safety, then the production line couldn’t have built those cars. But it could. It did. 69 times in 1969 for the full COPO 9561 package, with the actual number being debated by people who know far more about this than I do. The infrastructure was there. The parts were there. The knowledge was there. The only thing standing between a stock Camaro and a 427 Camaro was a policy written by men in suits who were trying to avoid bad headlines.
The loophole didn’t create a dangerous car. The loophole just bypassed a performative restriction.
I think about this constantly in the context of how systems actually work versus how they claim to work. I have a homelab in my house. Nothing crazy, just a few servers running various things, a network I built from scratch, some projects that keep my brain from eating itself at two in the morning. When I built it, I read everything I could find about best practices, security frameworks, network architecture. I understood the principles. And then I built it my way, which is definitely not how any certification exam would want me to build it, and which works exactly as well as I need it to work.
Is it textbook? No. Does it do what I need it to do, reliably, and have I actually learned more from building it weird than I ever would have from building it by the book? Absolutely yes. The point of a homelab isn’t to perform compliance with best practices. The point is to understand systems well enough to make them do what you need. I’m not getting graded. I’m not submitting it for audit. I’m Fred Gibb with a COPO order, figuring out what the system will actually let me do.
The broader principle here is one that the Gen-X cohort I came up in sort of absorbed by osmosis, even if nobody named it explicitly. We were the latchkey kids, the unsupervised ones, the generation that grew up in between the communal idealism of the Boomers and the institutionalized safety apparatus that came later. We figured things out by doing them wrong first. We learned systems by breaking them and watching what happened. That wasn’t an accident or a failure. That was the education.
And what that education taught me, over and over again, is that the people who succeed are rarely the people who comply the hardest. They’re the people who understand what compliance is actually protecting, and then figure out what it isn’t protecting. Fred Gibb didn’t beat the system. He read the system. That’s a completely different thing.
There’s a version of this story that bothers me, though, and I want to be straight about it. The COPO loophole was genuinely great for a very specific reason: the thing it created was actually good. The 427 Camaro was a real car, a fast car, a car that delivered exactly what the buyer wanted and expected. Gibb wasn’t using the COPO system to snake a customer or cut corners on safety or hide a defect inside a compliant-looking product. He was using it to deliver more of the actual value the customer was looking for.
That matters. That distinction matters enormously. Because there’s another version of this story, the version where someone finds the loophole and uses it to do something genuinely harmful while technically staying inside the lines, and that version is not a hero story. That version is fraud with better paperwork. The COPO Camaro works as a metaphor for productive rule-bending because what came out the other end was genuinely excellent. If it had been a poorly assembled, dangerous car that just happened to clear the regulatory hurdle, it would be a story about liability, not about ingenuity.
I hold onto that part of it because I think the celebration of loophole-finding can get self-congratulatory real fast. Not every unconventional approach is brilliant just because it’s unconventional. Sometimes people follow processes because the processes exist for reasons that aren’t immediately visible. I’ve been wrong about that more than once, gone around something because I couldn’t see the point, and found out later that there was a very specific reason for it. Being neurodivergent does not make you automatically correct. It just means your brain is going to take a different path regardless, so you better be paying attention to where that path actually leads.
But when the system’s restriction is performative, when it exists to protect an image rather than a reality, then finding the seam in it isn’t just clever, it’s kind of necessary. Because the alternative is that you let the performance substitute for the outcome, and the people doing the actual work never get what they actually need.
GM’s executives wanted to be able to say, publicly, that they were not putting enormous engines into small cars and selling them to teenagers who would then wrap them around telephone poles and generate terrible press coverage. That was the whole point of the restriction. And Fred Gibb’s COPO order didn’t actually undermine that. GM still got to say it. The COPO cars weren’t advertised. They weren’t in the brochure. They were a ghost product, something that existed in the operational layer of the company without existing in the public-facing layer. Both things were true simultaneously, and everyone involved understood that was the arrangement.
The engineers got to build what they wanted to build. The dealers got to sell what their customers wanted to buy. The executives got to maintain the official position they needed to maintain. And somewhere in 1969, some kid in a dealership in Illinois signed the paperwork on a 427 Camaro and drove it off the lot and it was the greatest thing that had ever happened to him.
The system worked. Just not the way anyone designed it to work.
I’m not telling y’all to go find loopholes in everything you touch. That’s exhausting and it will make you impossible to work with, and I say that as someone who has been, at various points, exhausting and impossible to work with. What I’m saying is that there’s a difference between following the rules and understanding the rules, and only one of those actually requires you to think.
The COPO 9561 exists because one guy understood a system well enough to see what it was actually doing versus what it was supposed to be doing. He didn’t rage against it. He didn’t write a manifesto about corporate overreach. He filled out a form. He used the system’s own machinery to accomplish what the system’s official policy said couldn’t be accomplished. And what came out was a 427 cubic inch, L72-powered, four-speed Camaro that will make your teeth rattle and your palms sweat and your brain go completely, blissfully quiet.
That’s not rebellion. That’s reading comprehension.
And somewhere out there, somebody is right now looking at a system they’re supposed to be complying with, reading the fine print, finding the seam, and building something that isn’t supposed to exist.
I hope it’s incredible.
