Explaining an AI theme to a client is a vocabulary job, not a prediction job. On this desk, a theme page is an editorial basket of public tickers with delayed quotes and linked research — see a theme basket is not an ETF. The two states to keep apart are research framing (what the theme tracks and what filings it points to) and account action (what, if anything, belongs in a client portfolio under your firm’s process). When the path works, you can say which RomeWay theme URL you opened, which sibling filing explainer you used, and which sentences you refused to say. The look-alike to refuse is reading a theme card as a ranked buy list or as a substitute for a written recommendation with a price objective.
This page owns client-facing language for AI themes. Sibling jobs: theme vs ETF honesty in theme basket is not an ETF, stock-page boundaries in what stock pages show, delayed-number hygiene in cited market numbers, demand-layer filings in where AI demand shows up, concentration hygiene in customer concentration vs AI revenue, and the live board at Desk terminal. Theme hubs: AI semiconductors, hyperscaler capex, earnings week. Learn: theme basket, delayed quote, Investor.gov.
- During the meeting: open the theme page and one filing sibling before you narrate “AI exposure.”
- When the client asks “should we buy”: switch clocks — that is account process, not theme vocabulary.
- After you stop the wrong inference: what remains is a research map, not a completed recommendation.
Who this page is for
Stay here if you are a trader-facing advisor, RIA associate, or small desk that must explain public AI themes without inventing a target price. You need sentences you can reuse that name documents and refuse slogans. You already accept that RomeWay quotes are delayed and that empty fundamentals stay empty.
Takeaway: This URL is for humans who will speak to a client and still open a filing path.
Who should skip
Skip if you want a model portfolio, a rebalance ticket, or a compliance opinion letter — this page is not your firm’s IPS. Skip if the question is only “is the basket an ETF” — use that page. Skip if you need Meta/Oracle cloud vs capex mechanics — use C1. Skip if you need the earnings-week document order — use the premarket checklist.
Takeaway: Leave when the job is product mechanics, compliance sign-off, or a trade ticket.
Out of scope
No buy/sell/hold language, no price targets, no “will outperform,” no suitability determination, no Form ADV drafting, no broker-dealer marketing rules checklist. Empty PE cells stay empty. Delayed lasts stay delayed.
Takeaway: Language hygiene only — one intent per URL.
Clock: when the client asks about AI
Healthy sequence in a client conversation:
- Name the theme surface you are using (URL + what membership rule means).
- Name one filing object the theme is meant to illuminate (capex, RPO, concentration, Item 2.02 — pick the real sibling).
- State what the theme does not do (not an ETF, not an account list, not a target).
- Only then, if your firm process requires it, move to a separate account-review clock.
Trouble starts when step 4 happens before step 1 — when “AI theme” becomes a verbal buy list while the theme page never opens.
Takeaway: Theme clock first; account clock second; never reverse them in the same sentence.
A reusable desk script (ports before slogans)
Hand a junior this three-sentence pattern:
- Surface: “This is RomeWay’s AI semiconductors theme page — an editorial basket with delayed Desk quotes, not a fund.”
- Caption: “If we care about demand in filings, we open a sibling such as where AI demand shows up or customer concentration — not a social summary.”
- Refuse: “I will not attach a price target or a buy ranking to this theme card. Account decisions follow our firm process on holdings, not this research map.”
Observable result when the path works: the client can repeat which URL was research and which decision, if any, is still pending under your process.
Takeaway: Surface → caption → refuse is the designed dump path.
Look-alike matrix
| Object | What it is | Client misread |
|---|---|---|
| Theme page | Editorial membership + delayed quotes + research links | Treated as ETF or model portfolio |
| Stock research page | Single-name delayed quote + filing-backed fields when present | Treated as a live terminal ticket |
| Filing explainer | Named caption / document hygiene | Treated as a rating |
| Client holdings list | Account inventory under your custody / IPS | Assumed identical to the theme basket |
Defeat the look-alike: theme membership is a research rule; holdings are an account fact. Do not merge them because both list tickers. For basket vs ETF detail, stay on theme basket is not an ETF.
Takeaway: Same ticker symbols can sit in four different objects — name which object you are in.
What you may say vs what you must not
| Allowed (research desk) | Not allowed on this URL’s script |
|---|---|
| Name the theme URL and membership rule | Say the theme is a recommendation |
| Point to EDGAR / Item 2.02 / 10-Q siblings | Invent a target price or “will rise” |
| Label quotes as delayed Desk data | Claim a licensed live feed |
| Say a fundamental cell is empty | Fill empty cells from memory |
| Route account questions to firm process | Answer suitability from the theme card |
Takeaway: If the sentence needs a target to feel complete, the sentence is already on the wrong clock.
Common mistakes
- Reading the theme as a buy list. Look-alike: theme ↔ recommendation.
- Promising performance because “AI demand is in filings.” Filings show captions; they do not mint a target — see demand layers.
- Equating client holdings to theme membership. Account clock vs research clock.
- Using a delayed last as proof the theme “worked.” Quote surface ≠ thesis (cited numbers).
- Compressing concentration % into “the AI customer.” Use concentration hygiene.
- Skipping the refuse sentence because the client is impatient. That is when the look-alike wins.
Takeaway: Each mistake drops a port name or swaps clocks.
FAQ
Can I say a name is “in the AI theme”?
Yes, if you mean membership on the editorial page you opened. No, if you mean “therefore buy for the account.”
What if the client demands a target?
Refuse on this research clock. Move to your firm’s recommendation process — or say you will not invent one from a public theme card.
Is explaining a theme the same as a research report?
No. This page is a language map for public surfaces. Firm research reports follow your own policies.
Do delayed quotes make the explanation invalid?
No. They constrain what you can claim about “now.” Label them delayed.
Where do Meta and Oracle cloud vs capex questions go?
To Meta/ORCL cloud vs capex in filings — not into a target sentence.
What to do next
- Still learning ports: stay; rehearse the three-sentence script.
- Basket vs ETF confusion: theme basket is not an ETF.
- Filing mechanics: AI demand in filings, Meta/ORCL cloud vs capex.
- Earnings week: premarket checklist.
- Board context: Desk terminal.
Takeaway: Route by question type — client language stays here; mechanics and account process leave.