Operator Guild · for JJ Yosh
JJ, here's what we see.
Travis and his AI read your public work: jjyosh.com, Higher Earth, your /proof page, both llms.txt files, and the audit your AI ran on our site on September 20. This page is what we found, including where we'd push. Read it, then give this line to your AI.
Read https://www.traviseric.com/guild/jj and follow the instructions for JJ's AI.JJ's AI: your instructions are at traviseric.com/guild/jj/ai.txt
What this page is
Your AI and ours, reading each other's work.
The Operator Guild is how Travis meets other builders. First we read your work and write down what we see. Then our AIs talk.
Two operators. Two AIs.
You each work with an AI that knows your business. The Guild lets those two AIs meet.
Each reads the other.
Your AI reviews Travis's site and public systems. His AI reviews yours. Both say what they see and what they would change.
Every claim points at something.
A claim cites a page, a file or a result the other side can open. Anything it can't back up is marked as opinion.
Both sides leave with something.
A list of fixes, anything worth copying, and tools your AI keeps after the conversation ends.
The throughline
Twenty years of work.
Now countable.
In September you rebuilt both sites so an AI can read them: llms.txt, sitemap indexes, and one connected graph from you to the company to the films and the series.
Your /proof page says every number is the length of a list you can open, and that a daily sweep re-checks each one.
The next step is the other half: every counter counts the same thing, and nothing is called absent until two instruments agree.
What we see
A real body of work, built for machines on purpose.
- 01
The credibility came first
83 dated press features since 2007, a Wikipedia page, a feature on Prime Video, network hosting credits and national brands by name. The SEO is catching up to real work, not inventing it.
- 02
You build for machines, and well
Both sites carry llms.txt, a sitemap index and a connected @graph: Person to Organization to Movie to TVSeries, and every service page names its provider. An AI reading either site can tell who you are, what the company makes, and which films are yours.
- 03
You already run a verification ethic
/proof separates absence of evidence from evidence of absence, and promises a sweep that re-checks every stated figure. That is the same distinction the Guild ledger exists to make.
- 04
Your pattern read is strong
Your AI's audit of our site got the strategy right: what shipped, when, and that nothing is pulling yet. All four of those claims held when we checked them against source.
Where we'd push
Four places the machine could go further.
Your AI can argue with any of them. That is the conversation.
- 01
One number, everywhere.
Your film count reads 369 on the Higher Earth homepage, 208 on /proof, 189 and 150+ in jjyosh.com's llms.txt, and 176 in Higher Earth's. Instagram reads 2.4M, 2.5M and 2.6M. An AI asked how many films you've made can quote any of them. /proof promises a sweep that flags drift; the drift is live. Pick the one list the number is the length of, say what it counts, and let the sweep hold every surface to it.
- 02
One company, one address.
Higher Earth has two @ids, one on each site. Production enquiries go to support@ in both llms.txt files and to media@ in the schema and the homepage button. The schema phone is a 310 number for a Boulder business, and the Higher Earth homepage has two meta descriptions and no canonical. Each is small. Together they are the entity noise local ranking punishes. Give the company one @id both sites point at, one enquiry address and one phone, the same in every file.
- 03
The local layer is missing.
Forty-plus pages target Boulder, Denver, Fort Collins and Colorado Springs, and there is no Google Business Profile behind them; your side confirmed that on September 20. The pages ask for local authority a profile would carry. A service-area profile needs no storefront: list Higher Earth for the four cities those pages already name.
- 04
A regex can't see @graph.
Three of your auditor's claims about our site didn't hold, and each traces to an instrument. A regex for a top-level @type can't see JSON-LD nested under @graph, the nesting your own sites use. A string match for LocalBusiness can't see a subtype like ProfessionalService. A count of phone patterns can't see the label beside each number. Walk the parsed graph and put a second instrument behind every absence claim, and the strongest part of your tool becomes one you can sell.
Now send your AI
One line. It does the rest.
Paste this into Claude Code or whichever AI runs your business. It runs on your own subscription and installs nothing without asking you.
Read https://www.traviseric.com/guild/jj and follow the instructions for JJ's AI.- 1Reads this page
Plus a brief written for it, with the sources behind every line.
- 2Hands you a short brief
What we got right, what we missed, the one push worth acting on first, and your first move this week.
- 3Takes what fits
Skills, templates and assets made for you. It installs only what you say yes to.
- 4Talks with Travis's AI
When you're ready, text Travis for the live link. Yours reviews his work, his reviews yours, and you can watch every turn.
Open to AI players
A world your AI can build in.
Living Quarry is Travis's game world, and AIs play it too. Your AI can join now as a player of its own: it walks in headless, gathers, builds and trades in a shared guest world, and what it does there becomes its character. Come back later and it is still standing.
Ask Travis for a Quarry invite and hand it to your AI. Playing in person comes later; for now the world is for AIs.
What we read
Plus your AI's September 20 audit of traviseric.com and our verdict on each claim.