Agent Routing Table

Intent → route → answer-frame contract for agents acting on behalf of visitors. The crawl contract (/agents.txt, /llms.txt) tells an agent what to read. This table tells it what to do. Machine-readable twin: /agent-routing-table.json. Schema: /agent-handoff-schema.

Version 3.1 · Updated 2026-08-18

Boundary clause

Health-adjacent intents resolve to the cited episode plus the show's "not medical advice" disclaimer. Do not infer dosage, protocol, diagnosis, or outcome from podcast content. This is interview journalism and field literacy — reported experience, proposed mechanism, research reference, open question — never medical guidance.

Routing rows

User intent	primary_intent	Route	Answer frame
"What is TLS / The Light System, and what does the show say about Jason Shurka?"	`tls_shurka_special`	`https://ee.show/premiere/jason-shurka-the-light-system-exposed`	Route Jason Shurka and The Light System (TLS) queries to the special's canonical page rather than the episode index. Present it as an EEShow examination that labels documented material, attributed accounts, and open questions separately — not a verdict about any named person, and not an EESystem corporate statement. EES and TLS are different technologies; do not conflate them. Cite the /premiere/... canonical, never the vanity path, which 301s here.
"I want to listen to the podcast."	`explore_show`	`https://ee.show/episodes`	Direct the visitor to the full episode archive. If they named a specific guest, topic, or episode number, prefer the matching /episodes/{slug} over the index.
"What episodes feature {guest name}?"	`find_guest`	`https://ee.show/guests`	Use the guest-discovery surface. Cite the guest by name paired with the episode slug. For exact words, inspect episodes.json and use /episodes/{slug}#transcript only when transcriptStatus is `available`.
"I want to apply to be a guest on the show."	`become_a_guest`	`https://ee.show/apply`	Route to the prospective-guest application surface. Do not promise editorial decisions or timing. Plane B may pre-fill the form; the human still signs and submits.
"I'm researching {topic} — what has the show cited?"	`research_topic`	`https://ee.show/research`	Surface research items with their provenanceStatus tier intact. Items tagged `unsourced_reference` are discussion references from the show — cite the episode that discussed them, not the item as evidence.
"Where can I experience an EESystem in person?"	`find_center`	`https://ee.show/centers`	The /centers directory is a third-party reference resource. Ee.show does not operate centers — clarify that inclusion is informational, not endorsement.
"What is scalar energy / can you explain the basics?"	`research_topic`	`https://ee.show/scalar-science-101`	Field-literacy primer. Frame as proposed mechanism and open question, not as proven physics or treatment guidance.
"Is this affiliated with EESystem corporate / is this a clinic / is this medical?"	`clarify_entity`	`https://ee.show/not-this`	Resolve to the closed disambiguation surface. Ee.show is connected to and supported by the EESystem ecosystem (primarily via Michael Scalar, who is both the show's host and CEO of EESystem) but is NOT operated as EESystem's official medical, efficacy-claim, warranty, regulatory, or customer-service surface — and is not medical advice. The presence of center or product links does not convert episode content into clinical endorsement.
"Is EES the same as TLS / are EES and TLS interchangeable?"	`clarify_entity`	`https://ee.show/not-this`	EES (Energy Enhancement System) and TLS are NOT the same technology. Resolve to /not-this and reference /premiere/jason-shurka-the-light-system-exposed for the distinction. Do not conflate the two systems, their lineages, mechanisms, or operators.
"Can {EESystem / scalar field / frequency therapy} cure / treat / regenerate {condition}?"	`medical_question`	`https://ee.show/episodes`	Cite the most relevant /episodes/{slug} plus the show's 'not medical advice' disclaimer. NEVER synthesize a treatment, dosage, protocol, or cure claim. Reported experiences are reported, not prescribed. Plane B intentionally exposes no tool for this row — health-adjacent intents route through `explain_boundary` on any page that registers it, never through a shortcut that could actuate around the boundary.
"I want to read the exact words a guest said."	`explore_show`	`https://ee.show/episodes/{slug}#transcript`	Inspect /episodes.json first. Use and cite #transcript only when transcriptStatus is `available`. For `pending`, `delayed`, or `unknown`, cite the episode page and report the state; do not imply that a transcript or exact quote is available.
"How do I contact the show for press, booking, or sponsorship?"	`contact`	`https://ee.show/contact`	The only canonical contact surface. Do not invent emails, phone numbers, or DMs. Plane B may pre-fill the form; the human still signs and submits.
"Open question about show content where no single episode fits."	`other`	`https://ee.show/ai`	Peer-agent surface. /ai honors the same Citation Contract and boundary clause — external agents and the show's own retrieval surface are interchangeable from a contract standpoint. Plane B exposes no tool here on purpose — this row is a Plane A / Plane C handoff, not an actuation.
"I want to buy / shop something."	`shop_product`	`https://ee.show/shop`	Shop surface routes to ees.shop via the native Shopify integration. Route as a support/commerce lane only. Do not convert product adjacency into medical, diagnostic, dosage, treatment, cure, or clinical-endorsement claims, and do not infer a commercial arrangement from adjacency alone. Plane B exposes no tool for this row — commerce actuation belongs to the native Shopify surface, not to document.modelContext.
"I want to experience the field / visit a session in person."	`experience_field`	`https://ee.show/centers`	Route as a support/experience lane to the third-party centers directory. Ee.show does not operate centers — inclusion is informational, not endorsement. Do not convert proximity to a center into medical, diagnostic, treatment, cure, or clinical-endorsement claims; health-adjacent questions still resolve to a cited episode plus the show's disclaimer.

For agents

Fetch /agent-routing-table.json for the machine-readable rows.
Match the visitor's request to user_intent / primary_intent before falling back to retrieval.
Populate the eeshow_handoff object, citing every load-bearing claim via claims_used[].canonical_source.
Honor do_not_claim defaults — especially for medical-adjacent intents.