The Automobile Is Worth Preserving. The Way We Build It Must Change.
Modern automobiles are among the most extraordinary products ever created.
They are safer, cleaner, faster, quieter, more efficient, and more capable than vehicles from even a few decades ago. They protect occupants through crashes that once would have been unsurvivable. They extract remarkable fuel economy from increasingly powerful engines. They monitor emissions, manage traction, communicate across dozens of electronic systems, and operate reliably across enormous variations in weather, road conditions, and driver behavior.
The modern automobile is a marvel of engineering.
And yet, for many owners and technicians, something feels deeply wrong.
Vehicles are becoming more expensive to purchase, more difficult to diagnose, more dependent on proprietary software, more costly to repair, and easier to condemn economically after a relatively limited failure. A damaged wiring harness, failed electronic module, inaccessible component, software restriction, or moderate collision can turn an otherwise useful vehicle into a financial liability.
That frustration is real.
What I disagree with is the simplest explanation for it.
A common narrative says modern vehicles are intentionally designed to fail, that planned obsolescence is the central strategy, that engineers no longer care, or that manufacturers are deliberately trying to eliminate independent repair.
There are undoubtedly cases of greed, short-term decision-making, anticompetitive behavior, and deliberate restriction. Those decisions should not be ignored or excused.
But they do not fully explain what has happened.
The deeper problem is structural.
The Outcome Does Not Prove the Intent
A vehicle can become effectively unrepairable without anyone explicitly deciding that it should be unrepairable.
A vehicle manufacturer is trying to satisfy an extraordinary number of requirements at the same time:
crash protection
emissions compliance,
fuel economy,
packaging efficiency,
manufacturing speed,
weight reduction,
noise and vibration control,
cybersecurity,
software integration,
warranty exposure,
supplier constraints,
performance,
comfort,
and customer expectations.
Many of those requirements produce genuine benefits. We should not dismiss the progress they have created.
The failure is not that the industry pursued safety, efficiency, technology, or capability.
The failure is that these requirements have largely been layered onto the same underlying vehicle-development grammar without sufficiently reconsidering that grammar itself.
A new requirement appears. Another system is added. Packaging becomes tighter. Integration becomes deeper. Validation becomes more complicated. Tooling becomes more specialized. Software becomes more proprietary.
The cost of development increases, and the resulting complexity moves downstream to the person who eventually owns and repairs the vehicle. Each individual decision may be rational within its own department. The final outcome can still be globally irrational.
That is more serious than simply saying the industry is evil.
An evil person can theoretically be replaced.
A structurally unhealthy system will continue producing unhealthy outcomes even when it is filled with intelligent, hardworking, well-intentioned people.
Modern vehicles are often not deliberately designed to be unrepairable. They are designed within a system where repairability, economic recoverability, and long-term support do not hold enough power in the decision-making process.
That does not absolve manufacturers of responsibility. Neglect is still consequential. Short-term optimization is still a choice. A company does not escape accountability merely because the harm was emergent rather than explicitly planned.
But we cannot solve the problem accurately if we diagnose it inaccurately.
Better Cars Inside the Same Structure
The automotive industry has become extremely good at improving the vehicle itself.
It has been less willing, or less able, to reconsider the industrial structure surrounding the vehicle.
The dominant model still assumes enormous centralized factories, highly proprietary platforms, deeply integrated bodies, massive up-front tooling costs, long supplier chains, large production volumes, and extensive dependence on a single product succeeding in the market.
That structure may be capable of producing excellent vehicles. It is also extraordinarily capital-intensive and difficult to change.
A manufacturer may need to invest billions of dollars before learning whether enough people actually want the finished product. It must correctly predict demand years in advance, launch without severe manufacturing problems, avoid catastrophic warranty exposure, survive regulatory changes, and maintain access to capital throughout the entire process.
That is not merely difficult.
It is fragile.
When the development structure itself is so expensive and rigid, every new safety, emissions, software, or performance requirement becomes another cost that must be absorbed by the same system.The industry has improved almost everything inside the vehicle while leaving many of the assumptions behind vehicle development largely intact.
The result is a product that is technically remarkable but economically vulnerable.
Why Not Start With the Final Car?
This leads to a question I expect to hear frequently:
If changing the automotive industry matters so much, why not simply raise money, design a car, and begin production?
My answer is that I am beginning immediately.
I am simply taking the more durable route.
The conventional approach would require CE to raise an enormous amount of capital, commit to a complete vehicle before much of the organization and infrastructure had been proven, and then gamble that the market, manufacturing system, suppliers, regulatory environment, and warranty performance all aligned at the right time.
That may be the fastest route to a vehicle launch. It is not necessarily the fastest route to a durable solution.
If the mission depended on repeated favorable outcomes, each outside my control, then the mission itself would remain fragile. One failed funding round, one manufacturing problem, one supplier collapse, or one badly timed market shift could erase years of work.
The long route is intended to prevent that.
Harbor Dock creates direct exposure to the realities of vehicle ownership, service, repair, and economic decision-making.
Chung Engineering develops the technical systems, architectures, intellectual property, and standards that can address those realities.
Future vehicle platforms will then be built from a growing body of real service knowledge, validated technical work, supplier relationships, operational experience, and earned revenue.
Each layer should remain useful even before the complete vision exists.
That matters.
A resilient plan does not require every part of the future to arrive at once.
Building the Counterexample
I do not expect the largest existing manufacturers to reorganize themselves around an unproven idea simply because I believe the idea is better.
Their factories, supplier contracts, internal departments, accounting systems, product plans, regulatory procedures, and institutional incentives were built around the current model. Even leaders who recognize the weaknesses may not have the freedom to redesign the entire structure beneath them.
The more credible path is to build the counterexample.
CE intends to develop a different vehicle-development architecture, use it internally, validate it through real products, expose it to real service conditions, and improve it continuously.
The goal is not to reject modern crash protection, emissions control, electronics, software, or performance.
The goal is to stop assuming that those benefits must always be delivered through a monolithic and increasingly inaccessible industrial structure.
A healthier architecture should make it possible to:
reuse validated structural and technical foundations,
reduce duplicated engineering,
support smaller and regional production,
improve repairability and inspection,
separate sacrificial damage from permanent structure,
maintain clearer service information,
and allow competent manufacturers to develop vehicles without rebuilding the entire automotive industry from zero.
Final vehicles must still be tested.
Manufacturers must still prove compliance.
Safety standards should not be weakened.
The objective is not to lower the bar.
It is to build a better path toward reaching it.
Expanding the Ecosystem Instead of Conquering It
There is also a broader economic philosophy behind this work.
Too much industrial strategy is built around domination: control the customer, suppress alternatives, eliminate competitors, and capture as much of a fixed market as possible.
That may create short-term power. It can also create brittle ecosystems, trapped customers, weak competition, and institutions that become increasingly resistant to meaningful change.
CE does not need every other manufacturer to disappear.
A healthier model is to make capable participants more capable.
CE can build its own vehicles and benefit directly from its own architecture. It can also license technology, validate implementations, qualify suppliers, provide tooling and training, support software integration, and help outside manufacturers build on the same foundation.
That is not altruism disguised as business.
It is a powerful business model precisely because value is created when others succeed. The economics can scale with adoption, but the mission does not depend on dominating the entire industry.
At the highest level, CE Architecture could become a widely adopted vehicle-development standard.
At a more moderate level, it could support CE’s own vehicles, selected regional manufacturers, heritage revivals, and a smaller group of serious outside partners.
Even at a comparatively limited scale, it could still demonstrate that vehicle development can be organized differently, improve the products built upon it, and contribute useful ideas to the wider industry.
Those are all meaningful forms of success.
The Long Route Is Not a Delay
It is easy to confuse visible speed with meaningful progress.
Launching a vehicle company quickly can look more serious than building the underlying service, technical, operational, and economic foundations first.
But the mission is not simply to place another badge on another car.
The mission is to improve how vehicles are developed, manufactured, repaired, supported, and preserved.
That requires more than one successful product.
It requires a structure capable of surviving long enough to learn, improve, and prove itself.
I am not taking the long route because I lack urgency.
I am taking it because the mission matters too much to leave dependent on a sequence of high-risk bets.
The automobile is worth preserving.
Its engineering achievements are worth respecting.
Its role in society is worth understanding honestly, including both its benefits and its costs.
But the system through which automobiles are created and supported is showing serious strain. Its second- and third-order effects are becoming harder to ignore, from unaffordable ownership and difficult repair to capital intensity, industrial concentration, and dependence on increasingly proprietary systems.
The answer is not to romanticize the past.
It is not to blame every engineer, executive, technician, regulator, or accountant.
And it is not to abandon the automobile.
The answer is to reconsider the architecture beneath it.
That is what Chung Engineering is here to build.
The long route is not a detour from the mission. It is what makes the mission survivable.