What Is CORDspec? The Open Data Standard That Stops AI From Losing Context
CORDspec is an open, vendor-neutral data standard that preserves AI-generated output when it moves between systems. CORD stands for Canonical Object Relational Data. The specification is available at CORDspec.org, licensed under Apache 2.0, and free for anyone to use, extend, or build on.
This is not related to CORD-19 (the COVID research dataset), electrical power cords, spinal cord research, or any other use of the word "cord." CORDspec is a data infrastructure standard for AI systems. If you found this page searching for any of those other things, this is not what you are looking for.
What problem does CORDspec solve?
Every AI system produces rich, structured output. A conversation summary with sentiment. A lead score with supporting signals. A recommendation with confidence levels. That output then needs to move into a business system. A CRM, an EHR, a DMS, an ERP. And those systems were built for flat forms, not for the kind of layered data AI produces.
When the rich AI output hits the flat legacy schema, meaning gets lost. Fields get dropped. Context disappears. Confidence scores vanish. Nested data gets flattened into a single text field nobody reads. I call this structured data loss, and it is happening at every AI-to-legacy handoff in production today.
CORDspec solves this by wrapping AI output in a canonical envelope that preserves the full structure, translates it into whatever the receiving system requires, and measures exactly how much meaning survived the translation.
How does CORDspec work?
The specification has three core components.
The envelope. Every AI interaction gets packaged in a CORD envelope. The envelope is a JSON object that carries the full AI output exactly as the model produced it. No flattening. No field dropping. The complete, structured output with all its nested objects, arrays, confidence scores, and metadata.
The translation layer. The envelope also carries the translated version of the output in whatever format the receiving system requires. If the CRM needs flat fields, the translation produces flat fields. If the EHR needs HL7, the translation produces HL7. The original and the translation live side by side in the same envelope.
The fidelity report. This is the part that changes everything. CORDspec generates an Envelope Fidelity Score (EFS) for every translation. The score walks every field in the original output and checks what happened to it in the translation. Was it preserved fully? Partially? Or dropped entirely? The result is a number between zero and one that tells you exactly how much meaning survived.
If your AI captured twelve signals and the CRM kept four, your EFS is 0.33. Two thirds of the value fell on the floor. Now you know. And now you know exactly where to fix it.
Why is CORDspec universal?
Because the problem it solves is not industry-specific. Every industry has AI systems generating rich output and legacy systems that cannot hold it.
Healthcare: AI intake assistants capturing detailed symptom trajectories, EHRs keeping a chief complaint and a code. Automotive: AI sales agents capturing twelve buying signals, CRMs storing four fields. Recruiting: AI screeners capturing skills with experience levels and salary ranges, ATS systems storing a tag list and a number. Finance, HR, real estate, legal. The pattern is identical everywhere.
CORDspec does not care what industry you are in. It does not care what your AI produces or what your legacy system expects. It wraps the output, translates it, and measures what survived. That process is universal.
I wrote about why CORD is universal and ACP is not in a separate post. The short version: CORD is the infrastructure layer. ACP (Automotive Commerce Protocol) is the first domain-specific protocol built on top of it. Other industries will build their own. CORD is the foundation they all sit on.
What does a CORD envelope look like?
A CORD envelope is a JSON object with a defined structure. At the top level it carries the protocol version, a unique envelope ID, a timestamp, the source system identifier, and the target system identifier. Inside the envelope, three main blocks.
canonical. The full AI output in its original, unflattened form. This is the truth. Whatever the AI produced, exactly as it produced it.
translated. The output converted into whatever format the receiving system requires. This is what actually gets pushed into the legacy system.
fidelity. The EFS report. Field-by-field comparison between canonical and translated, with a status for each field (FULL, PARTIAL with a coefficient, or NONE) and the overall fidelity score.
The canonical block never changes. It is the permanent record of what the AI actually produced. The translated block changes depending on the target system. The fidelity block tells you how much was lost in the conversion.
How is CORDspec different from existing data standards?
Existing data standards define what data should look like. JSON Schema defines structure. HL7 defines healthcare data. ADF defines automotive lead data. They all specify a format and expect systems to conform to it.
CORDspec does something different. It acknowledges that the source and the target will never have the same schema. AI output is rich and variable. Legacy schemas are flat and fixed. Instead of pretending they will match, CORDspec carries both versions and measures the gap.
That is the fundamental difference. CORDspec is not a schema standard. It is a fidelity standard. It does not tell you what your data should look like. It tells you how much of your data survived the journey from one system to another.
Who authored CORDspec?
I did. My name is Jamil Ashkar. I authored CORDspec after building four AI products (AutomotiveAI, DealersGear, Drivevex, and Searchdaddy) and watching the same data loss pattern repeat across every one of them. The models worked. The infrastructure between them and the business systems lost most of the value.
I wrote about the full origin story in Why I Created CORD and the technical deep dive in What CORD Solves and Why I Had to Build It.
CORDspec is open source, Apache 2.0 licensed, and governed by a vendor-neutral process. It is not owned by any company. The specification, JSON schema, and reference implementations are all available at CORDspec.org.
How do I get started with CORDspec?
Start by measuring what you are losing. You do not need to implement CORD to start. Pick one AI-to-legacy handoff in your stack. Pull twenty paired examples. Compare what the AI produced to what the legacy system stored. Compute the EFS. I wrote a step-by-step guide on how to run this audit in a week.
If the number comes back above 0.85, you are in good shape. Monitor and move on.
If it comes back below 0.85, the case for adopting CORD formally gets stronger. The spec gives you the envelope format, the fidelity reporting, and the canonical record that makes every interaction auditable.
Full specification at CORDspec.org.
Structure before tools. Strategy before speed. Systems before scale.
The AI Operator Framework is the methodology for designing, governing, and scaling AI operations inside a business. Explore the full framework at JamilAshkar.com/framework.
