I open-sourced CORD (Canonical Object Relational Data) and ACP (Automotive Commerce Protocol) because closed standards never become standards. Closed specifications become vendor lock-in. Open specifications can be implemented by anyone, improved by anyone, and adopted across an industry. The point of writing these standards was to fix structured data loss across real businesses. That goal is only achievable if every system in the chain can implement the spec freely. Opening the standards was not a generous decision. It was the only decision that made the standards work.
People assume the open-source decision was idealistic. It was not. It was strategic. Here is the actual reasoning.
Why Closed Standards Do Not Become Standards
A standard's job is to be implemented by every system in a chain. That only happens when every vendor can implement it without licensing friction. A closed spec creates friction. Friction reduces adoption. Reduced adoption means the standard fails its core purpose.
I have watched closed standards in adjacent industries try this approach. They get implemented by the vendor that owns the spec. They get partially implemented by the two or three vendors closest to that one. Everyone else either ignores the spec or builds a competing one. The fragmentation kills the goal.
What Closed Standards Actually Produce
Vendor lock-in. The owner of the closed spec controls the implementation. Customers who adopt the spec are locked into the owner's ecosystem. The "standard" is just a marketing word for the owner's proprietary shape.
That is not a standard. It is an integration trap. And it is exactly what I did not want for CORD and ACP.
Why Open Source Was the Only Choice
Three reasons.
One. Network effects. Every additional implementer of an open standard makes the standard more valuable for every existing implementer. The math compounds. Closed specs do not get this compounding because they do not get adopted broadly enough.
Two. Community contribution. I do not have all the answers. Operators in other industries, other companies, other roles see things I miss. Open-source lets them contribute back. The standard improves because more eyes look at it.
Three. Longevity. Open standards outlive their authors. I will not be involved in AI operations forever. The standard needs to keep working after I am off the field. Open-source is the only architecture that survives founder departure.
What About the Patents?
ACP has patent pending status. CORD does not. The patent on ACP exists for one purpose: protecting the original architecture from being claimed by someone else later. It is not there to restrict implementation.
The reference implementation of ACP is open. The specification is open. Anyone can implement it. The patent simply prevents a future actor from claiming ownership of the design and demanding licensing fees. It is a defensive patent, not an offensive one.
How Open Source Standards Actually Spread
Three phases. I covered this in the pillar piece on both standards. Reference implementations first. Ecosystem pickup second. Default state third.
Open-source is what makes phase two possible. Vendors will not implement a closed standard because doing so means handing power to the spec owner. They will implement an open standard because adoption is the only thing they have to give up to participate.
What I Am Asking From the Community
Three things.
One. Read the specs. CORDspec.org for the universal envelope. ACPspec.org for automotive object types. If you have feedback, send it.
Two. Implement. If you are building AI products or working in automotive, implement the standards. Every implementation makes the standards stronger.
Three. Contribute. If you see gaps, propose changes. If you have written extensions, share them. The standards are not finished. They are versioned. They evolve.
Why This Matters Beyond Me
Because the data layer is the most important layer of AI operations that nobody is fixing. If I had kept these specs closed, the fix would have been local to my products. Open-sourcing them gives the fix to anyone who wants to use it. That is the only way an industry-level problem gets solved.
I will not be the last operator who runs into structured data loss. I am one of the first to write a spec for it. The standards belong to whoever needs them. That is the whole point.
Final Thought
Open standards are not generous. They are strategic. They are the only path that produces actual standards instead of marketing words. CORD and ACP are open because anything else would have killed them. Use them. Improve them. Or write something better. The data layer needs the help.
Want the full system? The AI Operator Playbook ($499) is the operating manual I use to deploy AI across real companies. Structure, governance, and scale documented end to end.
Structure before tools. Strategy before speed. Systems before scale.
Ready to operationalize AI inside your business?
The AI Operator Framework is the system I use to design, govern, and scale AI for real companies. Start with the AI Operator Playbook ($499) or apply to work with me directly.
