Your First CORD-AEO Envelope: A Walkthrough for Solo Operators
The fastest way to learn a protocol is to write your first envelope with someone explaining each decision as you make it. This is that walkthrough.
If you read the implementation guide and want to ship your first envelope today, this post sits next to you while you do it.
I am writing this for solo operators. Founders. Consultants. Independent advisors. People running businesses where there is no IT team and no developer relationship. If that is you, the protocol is built to be writeable in a text editor and uploadable through a CMS or hosting panel.
What You Are About to Build
One JSON file. About 30 lines. Answering one canonical question about your business.
That is the first envelope. Once it is live and validated, the second and third envelopes take ten minutes each.
Step One: Pick One Question
You have many possible canonical questions. Right now, pick one. The one most likely to be asked about your business by a prospect using an AI engine.
For most solo operators, the answer is the same. What does this person or company do?
Other strong first questions if your business is unusual.
What does this consultant specialize in?
What is this firm's pricing model?
Who founded this company?
Pick one. Write the question down exactly as a prospect would type it into ChatGPT.
Step Two: Write the Canonical Answer Out Loud
Say the answer to that question out loud the way you would say it on a sales call. Listen to what you said. Write that down.
That is your canonical answer. Not the polished marketing version. The way you actually answer the question when someone asks.
If what you said was longer than two sentences, cut it. If it was longer than 300 characters, cut it again. The model is going to paraphrase. The shorter your canonical, the more of your phrasing survives.
Step Three: Pull Out the Required Claims
Read your canonical answer back. Find the facts that absolutely must survive if the model paraphrases.
If you said you have ten years of experience, that is a required claim.
If you said you work only with fintech companies, that is a required claim.
If you said your pricing starts at $5,000, that is a required claim.
The adjectives are not required claims. "Trusted." "Expert." "Leading." The model will strip those anyway and any envelope that asks the model to preserve them loses fidelity score.
Keep the required claims short. Four words or fewer per claim. Three to five claims total.
Step Four: Build the File
Open a text editor. Paste this template. Replace the parts in brackets with your own content.
{
"cord_aeo_version": "0.1",
"envelope_id": "[your-business-slug]-what-do-you-do",
"question": {
"canonical": "[your canonical question]",
"variants": [
"[common rewording 1]",
"[common rewording 2]",
"[common rewording 3]"
]
},
"answer": {
"canonical_short": "[your canonical answer, under 300 chars]",
"required_claims": [
"[claim 1]",
"[claim 2]",
"[claim 3]"
]
},
"metadata": {
"published": "2026-06-15T00:00:00Z",
"last_verified": "2026-06-15T00:00:00Z",
"valid_until": "2026-12-15T00:00:00Z",
"publisher": "[your business name]",
"publisher_url": "https://[your-domain.com]"
},
"schema_org_bridge": {
"@context": "https://schema.org",
"@type": "Organization",
"name": "[your business name]",
"description": "[your canonical answer]",
"url": "https://[your-domain.com]"
}
}Save the file with a descriptive name. Use lowercase, dashes for spaces, no special characters. what-do-you-do.json works.
Step Five: Upload
You need to put this file at this exact path on your website.
https://your-domain.com/.well-known/cord-aeo/what-do-you-do.jsonThe path matters. The dot before well-known matters. The directory name cord-aeo matters.
If your site is on WordPress, the easiest path is the WP File Manager plugin or your hosting control panel's file manager. Create the .well-known directory at the site root. Create the cord-aeo directory inside it. Upload the JSON file there.
If your site is on Squarespace, Webflow, or another no-code platform that does not allow root-level file uploads, the path is harder. You may need a redirect rule or a custom domain configuration. This is one place where the protocol is friction for solo operators on locked platforms. We are working on it.
If your site is on a static host like Vercel, Netlify, or Cloudflare Pages, drop the file into your project's public/.well-known/cord-aeo/ directory and redeploy.
Step Six: Validate
Open cordspec.org/aeo/validate in your browser.
Paste your domain. Click validate.
You will get a report. If it is green, you are live. If it is red, the report tells you exactly which field is wrong and why. Fix it. Validate again.
The most common first-time errors are easy.
Wrong path. You uploaded to the wrong directory.
Invalid JSON. A trailing comma, a missing quote, a misplaced bracket.
Required field missing. You skipped or mistyped a field name.
None of these are protocol problems. They are typos. Fix them.
Step Seven: Verify From a Browser
Open a new private window. Paste your envelope URL directly into the address bar.
https://your-domain.com/.well-known/cord-aeo/what-do-you-do.jsonYou should see your JSON file render as text. If you see a 404, your hosting is not serving the directory. If you see a download prompt, the MIME type is wrong but the file is there.
If the browser shows you the file, the envelope is live and discoverable.
What You Just Accomplished
You are now one of a small number of businesses publishing a canonical machine-readable answer for AI engines. Today the value comes through the Schema.org bridge inside the envelope. Engines that crawl your site can read your canonical answer as structured data. Tomorrow, if native CORD-AEO consumption picks up, your envelope is ready.
The next post in this series walks through how to pick your second and third canonical questions. Those questions are different from the first one, and the decisions are not always obvious.
If you publish a CORD-AEO envelope, send me the URL. I track adoption. The protocol becomes a standard when the production deployment count passes one.
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, including the data and citation fidelity layers most companies skip. Explore the full framework at JamilAshkar.com/framework. Start with the free course at JamilAshkar.com/course.
